-
Written By Khushboo Maurya
-
Updated on August 31st, 2026
When export an Exchange Online mailbox to PST is a different thing. The New-MailboxExportRequest cmdlet is available for Exchange Server. But it isn’t the standard PST export method for Exchange Online. For Microsoft 365 mailboxes, administrators can use Microsoft Purview eDiscovery or Outlook-based export methods, it depends on the mailbox & export requirements.
So you’re stuck with Purview eDiscovery, Outlook manual export, or PowerShell wrapping the same Purview backend. If you’ve already tried those, you know the pain. If you haven’t, here’s the short version: they’re built for legal investigation, not IT operations.
This guide cuts to what you need – why native methods fail under real load, and how to get the job done without losing your weekend.
Microsoft’s recommended path. Requires eDiscovery Manager role. Search, export to Azure Blob, get a SAS URL, download within 7 days using a Click Once tool that only likes Edge. (Microsoft Learn)
| Limit | Reality |
| Speed | ~2 GB/hour server-side. A 100 GB archive sits for 50+ hours before you even start downloading.n |
| PST format | Investigation-grade. Includes hidden Recoverable Items. Often fails re-import to another tenant. |
| SAS expiry | 7 days. Miss it — download fails, Edge crashes, you’re on PTO — and you rerun the entire search from scratch. |
| Bulk scale | 25 mailboxes means 25 separate searches, 25 URLs, 25 reviewing sessions. |
Use when: One mailbox, under 30 GB, you already have eDiscovery rights, & no one is waiting on you.
File → Open & Export → Import/Export → PST. The only Microsoft-native way to get public folders. Client-side, so every item syncs to your local OST first.
| Why it hurts: ~50 GB Unicode PST ceiling. Public folders throw MAPI_E_NOT_FOUND on corrupted items. Unlicensed shared mailboxes often refuse to open. No automation – needs Outlook installed, an interactive session, and your patience. | Use when: One small public folder, Outlook already there, and you have an hour to spare. |
New-ComplianceSearch + New-ComplianceSearchAction -Export. Automates the search creation. But you still end up in the Purview portal, copying the SAS URL, and running the same eDiscovery Export Tool. Same investigation PST. Same re-import headaches.
Use when: 5–10 identical mailboxes and you want to skip clicking through the GUI wizard. That’s the only win.
When native methods turn a two-hour task into a two-week project, you need a tool built for the job. The Cigati Office 365 Backup Tool handles the sources and scale that Purview and Outlook leave behind.
A mid-size firm needed to offboard 25 departing employees – mixed primary mailboxes, auto-expanding archives, and shared project folders. Purview would have taken two admins three weeks of parallel searches, babysat downloads, and post-processing to strip hidden folders. Outlook was out of the question for unlicensed shared mailboxes and 150 GB archives.
Single Cigati session with impersonation. All 25 mailboxes queued. Folder structure intact. Ran over the weekend – throttling stretched the tail end into Monday, but unattended. PSTs verified clean in Outlook 2021. One tool license. One admin. Weekend intact.
| Litigation hold bloat: Held mailboxes retain deleted items in Recoverable Items. Purview exports all of it — your “50 GB mailbox” becomes a 140 GB PST. Cigati exports the visible mailbox by default; toggle Recoverable Items on only if Legal specifically needs it. | Inactive mailboxes: Once you remove the license & make a mailbox inactive, it’s tenant-locked. Export before inactivation, or you’re stuck running eDiscovery against the inactive mailbox later. |
| Encryption stays encrypted: Sensitivity labels, RMS, and S/MIME do not decrypt during export. S/MIME signatures remain verifiable. OME portal messages often don’t export at all. If Legal needs cleartext, decrypt at the source first using Purview super-user delegation or IRM admin rights. No tool bypasses this legitimately. | Throttling is universal: Microsoft’s ~2 GB/hour cap applies to every tool on the market. A 300 GB batch takes days. Plan for it. |
PSTs corrupt. It’s what they do.
The Backup Tool is focused on mailbox export. But projects expand. When yours does, Cigati has the rest covered:
One mailbox, under 20 GB, eDiscovery rights already assigned, and no deadline? Purview is fine. Slow and annoying, but it’ll get there.
Everything else – bulk offboarding, large archives, public folders, shared mailboxes, clean re-imports, or any scenario where your time has value – the native path is a trap. Microsoft’s investigation tooling was never designed for IT operations, and forcing it to do that job costs more in admin hours than any tool license.
For PST export specifically – the actual task of getting Exchange Online data into a portable, verifiable file – a purpose-built tool wins every time. The Cigati Office 365 Backup Tool handles the sources, formats, and scale that native methods struggle with. And when your project grows into tenant migration or Teams and SharePoint work, the broader Cigati suite handles those workloads without forcing you into an enterprise contract you don’t need.
Stop babysitting SAS URLs. Get the export done, verify the PST, and move on.
Ans. Yes. Cigati uses Modern Auth + application impersonation. No eDiscovery Manager role needed.
Ans. Purview takes 50+ hours server-side plus download, splitting into 10 GB chunks. Cigati streams directly and handles auto-expanding archives as a single job.
Ans. Cigati exports public folder mailboxes and nested subfolders directly. No Outlook required.
Ans. No. Export is read-only. Optional post-export delete is available after verification, but off by default.
Ans. Often no. Investigation-format PSTs frequently fail to import. Use a tool producing clean standard PSTs.
Ans. For Purview eDiscovery export: yes, on Windows with Edge. For Cigati: no.
Ans. Outlook often blocks it. Purview works with permissions. Cigati works via admin impersonation regardless of license status.
Ans. No. Sensitivity labels, RMS, and S/MIME remain intact. No legitimate tool can strip this without proper keys. Decrypt at source before export if clear text is required.
About The Author:
Khushboo Maurya is a digital content and SEO professional focused on creating useful, search-friendly content that connects with the right audience. She specializes in content optimization, website growth, and practical SEO strategies that improve visibility, engagement, and organic reach.
Related Post