How to Export Office 365 Mailbox to PST in 2026

Why not just use Microsoft 365 Backup (native)?

Microsoft launched its own first-party backup service in July 2024. If you’re comparing tools right now, this is the objection every buyer raises. Here’s the honest answer.

Microsoft 365 Backup is a restore service, not an export service. It snapshots Exchange, SharePoint, and OneDrive on Microsoft’s own infrastructure. Recovery points arrive every 10 minutes for two weeks, then weekly for up to one year. Restore is fast; 1 to 3 TB per hour, but the restore goes back into the same tenant.

What Microsoft 365 Backup does not do?

• Produce a PST file. There is no PST output. Restore is to the live mailbox, always.
• Give you a portable copy. Data stays inside Microsoft’s tenant infrastructure.
• Cover public folders as a first-class source.
• Satisfy the 3-2-1 rule. Both copies live on Microsoft. A tenant compromise or a Microsoft outage takes both down together.
• Come cheap on high-volume data. Pricing is roughly $0.15 per GB per month. A 500 GB user is $75/month, or $900/year for one mailbox.

Use Microsoft 365 Backup for fast in-tenant recovery. Use a PST export tool for offboarding, legal handoff, tenant-to-tenant portability, and offline archival – different jobs.

Who actually needs to do this?

PST export from Office 365 comes up in real situations.

• Offboarding: employee leaves, mailbox is 50–500 GB, you can’t keep paying the license.
• Tenant-to-tenant M&A: quick extract before a proper migration project starts.
• Storage reclamation: back up, purge, release the license.
• Public folder cleanup: legacy shared calendars, contacts, and mail folders before decommissioning.
• Online archive rescue: users with 100 GB+ auto-expanding archives that break Outlook’s export dialog.

What Microsoft-native methods can and can’t do?

A quick, honest look at every native option before we get to the tool. If you only need Method 1, use Method 1 and skip the rest.

Method	Works for	Fails at
Purview Content Search	Primary + archive, single mailbox at a time	Public folders (limited), 7-day SAS blob expiry, PST includes hidden Recoverable Items, can’t be cleanly re-imported to another tenant
Compliance Search PowerShell	Same as above, scriptable	Same PST format problem, eDiscovery Manager role required, E3+ licensing
Outlook desktop → Export to PST	Public folders, single user, small mailboxes	20 GB ANSI / 50 GB Unicode ceiling, needs Outlook installed, no server-side automation, Cached Mode corruption breaks large exports
New-MailboxExportRequest	On-prem Exchange only	Cmdlet does not exist in Exchange Online
Microsoft 365 Backup (native)	In-tenant restore, fast RTO	No PST output, no portable copy, no public folder as first-class source
Purview eDiscovery Premium	Legal exports with case management	Investigation-format PST, E5 license or 90-day trial, slow

Method 1: Microsoft Purview Content Search

Microsoft’s recommended path for Exchange Online. Requires the eDiscovery Manager role or Compliance Search assignment on a member of Organization Management.

1. Sign in to compliance.microsoft.com with an account in the eDiscovery Manager role group.
2. Open Content search → New search.
3. Name the search, select the target mailbox under Exchange mailboxes, and leave conditions empty to grab everything.
4. Run the search. Purview returns an item-count estimate; this is based on the search index, not a full count.
5. Export results → tick Include archive if the user has one → Generate.
6. Wait. Purview extracts to Azure blob storage and returns a SAS URL.
7. On a Windows machine using Edge, open the export job and click Download results. The Microsoft Office 365 eDiscovery Export Tool downloads and runs. Paste the SAS URL, choose a local path, and download.

What breaks on Method 1?

• SAS URL expires in 7 days. Miss the window, and you rerun the entire search.
• The PST includes Recoverable Items, hidden system folders, and workflow data. Attachments protected by sensitivity labels stay encrypted.
• Handing the PST back to the user? Strip hidden folders first, or they’ll see things they weren’t meant to see.
• Real report on r/Office365: a 370 GB online archive export ran for days and had to be split per year to complete.

Method 2: PowerShell + Compliance Search

Same engine as Method 1, scriptable. Best when you have 5–10 mailboxes to run through a repeatable process.

Connect-IPPSSession -UserPrincipalName admin@tenant.onmicrosoft.com New-ComplianceSearch -Name “Offboard-JSmith” ` -ExchangeLocation jsmith@contoso.com Start-ComplianceSearch -Identity “Offboard-JSmith” Get-ComplianceSearch -Identity “Offboard-JSmith” New-ComplianceSearchAction -SearchName “Offboard-JSmith” ` -Export -ArchiveFormat PerUserPst

Then head to the Purview portal, open the export action, copy the SAS URL, and run the eDiscovery Export Tool. Same 7-day expiry, same investigation-format PST.

Re-import problem: these PSTs frequently fail to re-import into another tenant using New-MailboxImportRequest or the M365 Network Upload service. Microsoft’s own MVPs confirm this is by design — Content Search PSTs are built for review, not transfer.

Method 3: Outlook desktop export

The only Microsoft-native path for public folders. Runs against your local Outlook profile.

Interactive

1. Outlook → File → Open & Export → Import/Export → Export to a file → Outlook Data File (.pst).
2. Select the public folder or user mailbox, include subfolders, save.

Scripted via Outlook COM

$Outlook = New-Object -ComObject Outlook.Application $pfTopFolder = $Outlook.Session.Folders | Where-Object { $_.Name -like “Public Folders -*” } # traverse to target public folder … $namespace = $Outlook.GetNameSpace(“MAPI”) $namespace.AddStore(“C:\Export\pf.pst”) $pstStore = $namespace.Session.Folders.GetLast() [void]$publicFolder.CopyTo($pstStore) $namespace.RemoveStore($pstStore) $Outlook.Application.Quit()

What breaks on Method 3

• Outlook must be installed and profiled. RDP or non-interactive sessions break the COM object.
• 50 GB Unicode PST ceiling. Larger folders must be split by date range.
• Public folder permissions are not preserved on export.
• Corrupted public folders throw DataExportTransientException, and the batch fails. You have to identify the folder by entry ID, remove it from NON_IPM_SUBTREE, and re-run.
• Common runtime errors: MAPI_E_NOT_FOUND, MAPI_E_FAILONEPROVIDER, and PST file lock errors when Outlook holds the store open.

Where all three native methods hurt

• Time: Purview searches on 100 GB+ mailboxes routinely take 12–48 hours before download even begins.
• Format: investigation PSTs need cleanup before user handoff.
• Coverage: public folders, primary, archive, and shared each need a different method.
• Scale: bulk offboarding; 25 employees at 320 GB total; is a multi-week project with native tools. IT teams pull weekends.

Method 4: Cigati Office 365 Backup Tool

Built for the gaps above. Named sources, no eDiscovery role required, no Azure blob timers, six export formats in one tool.

Sources supported in one interface

• Primary mailbox
• Online archive (in-place archive, including auto-expanding archives)
• Shared mailbox
• Public folder (public folder mailboxes and nested subfolder hierarchies)

Export formats

PST, MBOX, EML, MSG, CSV, PDF chosen per job. Migration mode targets another Microsoft 365 tenant, Google Workspace, or an IMAP server directly, no PST intermediate step. You can also export Office 365 Shared Mailbox to PST.

Steps to export any Office 365 source to PST

1. Install Cigati Office 365 Backup Tool (Windows or macOS) and click Backup.
2. Choose Modern Authentication, sign in with the tenant account. For bulk export, sign in as an admin with impersonation rights; the tool auto-fetches every mailbox on the tenant.
3. Select the source: Primary, Online Archive, Shared Mailbox, or Public Folder.
4. Pick users and folders from the tree structure.
5. Choose PST as the saving format. Apply date range, sender, subject, or attachment filters as needed.
6. Set the destination path.
7. Click Convert. The tool preserves folder hierarchy, metadata, timestamps, and attachments end-to-end.

Bulk offboarding via impersonation

Enable application impersonation on a service account. Point the tool at the tenant. Every mailbox backs up in one run, no re-auth per user. Runs concurrently across multiple mailboxes depending on hardware.

Post-backup storage reclamation

Once backups verify, the tool can delete backed-up items from the source mailbox. That reclaims tenant storage and lets you drop the license after confirmation — the ROI argument in front of finance.

Retention hold, litigation hold, and inactive mailboxes

Holds change export behavior in ways that trip up IT teams. Three cases to know.

Mailbox on litigation hold or in-place hold

A held mailbox retains all items in the Recoverable Items folder, even deleted ones. Purview Content Search exports everything in the hold — including deleted items — so PSTs from held mailboxes are often 2–3× larger than the user sees in Outlook.

Cigati Office 365 Backup Tool exports the visible mailbox by default and can include Recoverable Items on toggle. Turn it off for user handoff PSTs, on for legal hold response.

Inactive mailboxes (offboarded but held)

Microsoft’s recommendation for an ex-employee subject to hold: remove the license, keep the mailbox as inactive. This is free from a license standpoint but tenant-locked — no portable copy. If legal counsel wants a portable copy, you need to export before making it inactive, or use eDiscovery on the inactive mailbox directly.

Retention policies (retention labels)

Items under a retention label may be retained beyond user deletion. Exports pull the retained copy, which may include content the user thinks they deleted. Communicate this to legal or the mailbox owner beforehand.

Throttling: what to expect from Exchange Online

Every third-party tool hitting Exchange Online is subject to Microsoft’s throttling policies. This is not a bug in the tool. Plan around it.

• EWS impersonation caps individual account concurrency. Bulk backups across 20+ mailboxes will queue, not run fully parallel.
• Graph API endpoints have separate rate limits, applied per app + per tenant.
• A large offboarding batch (25 users × 15 GB average = 375 GB) typically runs over 24–48 hours, not minutes. That’s Microsoft’s ceiling, not the tool’s.
• The Cigati tool handles throttling with exponential backoff on 429 Too Many Requests and resumes automatically. Native PowerShell scripts often crash on 429 and lose progress.

Encrypted content: RMS, MIP, and S/MIME

Not every email survives export as cleartext. Three cases and how they behave.

Protection	In Purview export	In Cigati export
Sensitivity label on message body	Body stays encrypted	Body stays encrypted
Sensitivity label on attachment	Attachment stays encrypted	Attachment stays encrypted
S/MIME signed	Signature preserved, verifiable in Outlook	Signature preserved
S/MIME encrypted	Requires recipient’s private key to open	Requires recipient’s private key to open
OME (Office 365 Message Encryption)	Recipient-side portal messages don’t export	Same — portal messages don’t export

If your export must include decrypted attachments (legal discovery), have the mailbox owner or IRM administrator decrypt them first, or use Purview’s super-user decryption entitlement before export.

Decision matrix — pick the right method for the scenario

Scenario	Use
Single user, primary mailbox, under 50 GB, have E3, no time pressure	Cigati Office 365 Backup Tool
Automation across 5–10 mailboxes	Compliance Search PowerShell
Single public folder, Outlook available on desktop	Cigati Office 365 Backup Tool
Fast in-tenant restore only (no portable copy needed)	Microsoft 365 Backup (native)
Public folder with subfolders, no Outlook on server	Cigati Office 365 Backup Tool
Online archive over 100 GB	Cigati Office 365 Backup Tool
Offboarding 20+ users	Cigati Office 365 Backup Tool
PST must be re-imported to another tenant	Cigati Office 365 Backup Tool
Cross-format export (MBOX, EML, PDF for legal handoff)	Cigati Office 365 Backup Tool
Migrating M365 → Google Workspace or IMAP	Cigati Office 365 Backup Tool

Real deployment: 25-user offboarding at a consulting firm

A mid-size consulting firm needed to offboard 25 departing employees. Combined mailbox size: 320 GB. Contents: client correspondence, signed agreements, project files.

• Purview estimate: 3 weeks per full pass, two admins running searches in parallel.
• E3 admin license overhead: ~$552/year for two exporting admins.
• Cigati Office 365 Backup Tool: single admin session with impersonation, all 25 mailboxes queued, folder structure preserved, ran over one weekend (throttling stretched the final 8 mailboxes into Monday, but ran unattended).

The PSTs opened cleanly in Outlook 2021, folder hierarchy intact, no post-processing needed to strip hidden folders. Total cost: one tool license.

What the Cigati Office 365 Backup Tool does NOT do?

Honest disclosure. Buyers who ask for these should look elsewhere or pair with another tool.

• Does not back up Teams chat messages independently. Teams chat that lands in Exchange (per Microsoft’s compliance architecture) exports with the mailbox; ephemeral chat outside that scope does not.
• Does not back up SharePoint site content or lists; mailbox-focused product. Pair with a SharePoint-specific tool for full M365 coverage.
• Does not back up OneDrive files. Mailbox-focused.
• Does not decrypt sensitivity-labeled attachments. Content stays encrypted in the exported PST.

If the exported PST corrupts (rare but possible on 50 GB+ files during network interruptions), use the Cigati Outlook PST Recovery Tool to repair the file before import.

What to do with the PST after export

• Verify: Verify the exported PST by opening it in Microsoft Outlook and confirming that the mailbox folders, emails, attachments, and other selected items are present and accessible.
• Store: PSTs corrupt easily. Follow 3-2-1 — three copies, two media types, one offsite.
• Encrypt: Outlook PST password protection uses a weak algorithm. For legal handoff, put the PST inside a VeraCrypt volume or a 7-Zip AES-256 archive.
• Tag: record source mailbox UPN, export date, and export method against the PST filename. Auditors will ask.

Related reading

• Export Office 365 Archive Mailbox to PST
• Office 365 Tenant to Tenant Migration
• Import PST to Online Archive Office 365
• Export Shared Mailbox to PST
• Migrate Office 365 to Google Workspace

Related Post