Can PowerShell Export Microsoft 365 Mailboxes to PST?
No. Exchange Online PowerShell has no cmdlet that exports a mailbox to PST. Microsoft states that New-MailboxExportRequest works only in on-premises Exchange.
The older workaround closed too. Microsoft retired the Export parameter of New-ComplianceSearchAction on 26 May 2025. The eDiscovery Export Tool ended on 31 August 2025.
| Where the mailbox lives | Method |
|---|---|
| Exchange Online | Purview eDiscovery export in the portal |
| Exchange Online with scripting needs | Microsoft Graph eDiscovery APIs |
| Exchange Server on premises | New-MailboxExportRequest in PowerShell |
| Many users with date filters | Backup software |
How does the Purview Portal Export a Mailbox to PST?
Method #1: Purview eDiscovery Export (Microsoft 365 E3 or E5)
Who it suits. Admins with eDiscovery permissions. Extra application. A browser.
- Sign in to the Microsoft Purview portal with an account that has eDiscovery permissions.
- Select eDiscovery, then Cases, and open a case.
- Create a search with the mailbox as the source. Add no conditions to export every item.
- Open the search and select Export.
- Enter an export name. Choose Export items with items report and Create PSTs for messages.
- Set the PST size and select Export.
- Open the export under Process manager and select Download packages.
Microsoft lists PST sizes of 1, 2, 5 or 10 GB, with 5 GB as the default. When you organize by location, every mailbox gets its own PST. The primary and archive mailboxes merge into one file.
Search export packages expire 14 days after creation. Exports that take longer than 7 days are canceled, so split large exports by date range. The eDiscovery user needs a Microsoft 365 E3 or E5 license.
Can You Script the PST Export Without PowerShell?
Old PowerShell scripts that used the Export parameter no longer export. Microsoft recommends the Graph eDiscovery APIs for scripting.
Microsoft states that tenants with an E5 license and eDiscovery (Premium) can script all eDiscovery operations, including export, through these APIs. PowerShell still creates cases, holds and searches. Only the export step moved to the portal and to Graph.
What does PowerShell do on Exchange Server?
Method #2: New-MailboxExportRequest (Exchange Server)
Who it suits. Admins who manage Exchange Server. Extra application. Exchange Management Shell.
The cmdlet needs the Mailbox Import Export role. No role group holds it by default, so add it first. The Exchange Trusted Subsystem group needs permission to read from and save to the network share that stores the PST files.
New-MailboxExportRequest -Mailbox AylaKol -FilePath "\\SERVER01\PSTFileShare\Ayla_Recovered.pst"
New-MailboxExportRequest -Mailbox Kweku -FilePath "\\SERVER01\PSTFileShare\Kweku_Archive.pst" -IsArchive
Get-MailboxExportRequestThe -FilePath value must be a network share path. The -IsArchive switch exports the archive mailbox. Get-MailboxExportRequest lists your requests.
Our guides on downloading an Exchange mailbox to PST and exporting all mailboxes in a database go deeper.
What if PowerShell is Not an Option?
Classic Outlook exports one mailbox by hand. Select File, then Open & Export, then Import/Export, then Export to a file, and choose Outlook Data File (.pst).
This route applies only to the mailbox open in Outlook. Our Office 365 mailbox backup guide compares every method.
How do You Get PST Files for Many Users?
Method #3: Office 365 Backup Tool (Paid After Demo)
Who it suits. Admins who need PST copies for many users. Extra application. Office 365 Backup Tool.
The Office 365 Backup Tool saves mail, contacts and calendars to PST. It backs up many mailboxes through an admin account and a CSV file, filters by date and saves only new items in delta backups.
Shared and archive mailboxes are in scope. Single user backup needs no admin credentials. For deleted users, read how to export a soft deleted mailbox to PST.
Frequently Asked Questions
Can PowerShell Export an Exchange Online Mailbox to PST?
No. Microsoft states that New-MailboxExportRequest works only in on-premises Exchange.
What Replaced the eDiscovery Export Tool?
Microsoft retired the tool on 31 August 2025. The Purview eDiscovery portal now exports PST files as download packages.
Does New-ComplianceSearchAction Still Export in PowerShell?
No. Microsoft retired its Export parameter in 2025.
Which License does the Purview Export Need?
The eDiscovery user needs a Microsoft 365 Enterprise E3 or E5 license.
How Long do Purview Export Packages Last?
Search export packages expire 14 days after creation and Microsoft deletes them.
Can You Script the PST Export Without PowerShell?
Yes, with the Microsoft Graph eDiscovery APIs. Microsoft states that E5 tenants with eDiscovery (Premium) can script all eDiscovery operations.
Which Role does the PowerShell Export Cmdlet Need on Exchange Server?
New-MailboxExportRequest needs the Mailbox Import Export role. No role group holds it by default, so add it first.
Author's Verdict
Use the Purview portal for a PST from Exchange Online when you have E3 or E5 licenses.
Use PowerShell for PST export on Exchange Server only, and use a backup tool when many mailboxes need PST copies.
Key Takeaways
- PowerShell has no mailbox to PST cmdlet for Exchange Online.
- Microsoft retired the Export parameter in 2025.
- Purview exports PST files and Graph APIs script them.
Related Guides