How to Export Microsoft 365 Shared Mailbox to PST (Complete 2026 Guide)
Neeru Kuchhal
July 2nd, 2026
Shared mailboxes are one of the most widely used features in Microsoft 365, letting teams manage common email addresses like support@company.com or hr@company.com without assigning individual licenses. But when it comes to backing up, archiving, or migrating that data offline, exporting a shared mailbox to PST is far more technically involved than most administrators expect.
This guide covers how shared mailboxes actually work under the hood, why manual export methods fail at scale, and how to reliably export a Microsoft 365 shared mailbox to PST, both manually and automatically using the Macsonik Tenant to Tenant Migration Tool, a Graph API-based solution built to handle this conversion without the throttling failures, mapping dependencies, and scale limitations that manual methods run into.
What Is a Shared Mailbox? (An Overview)
A shared mailbox is a mailbox object in Exchange Online that allows multiple users to read and send emails from a common address. Unlike standard user mailboxes, shared mailboxes generally do not require a license unless their storage exceeds Microsoft’s default limits or advanced compliance features are needed.
- Directory-Level Identity: A shared mailbox is created as a special type of mailbox in Microsoft Entra ID (formerly Azure AD) rather than as a standard user mailbox. This unique configuration allows Exchange Online to recognize it as a shared resource, which affects how it is licensed, authenticated, and managed.
- Storage Backend: Like any other Exchange Online mailbox, a shared mailbox stores all emails, folders, and attachments in Exchange’s secure database. It uses a standard folder structure that includes default folders such as Inbox, Sent Items, Drafts, and Deleted Items, allowing users to organize and access their mailbox efficiently.
- Access Control Model: Because a shared mailbox has no enabled security principal by default, access isn’t granted through direct login, it’s granted through delegated Mailbox Access Rights: FullAccess (via Exchange ACLs), SendAs, and SendOnBehalf (via the PublicDelegates attribute). Authentication is proxied entirely through the delegate user’s own Azure AD OAuth token.
- Auto-Mapping Mechanism: When Full Access is granted, Exchange writes an entry via msExchDelegateListLink, which the AutoDiscover service picks up to auto-inject the shared mailbox into the delegate’s Outlook MAPI profile, this is why a shared mailbox “just appears” in Outlook without manual configuration.
- Storage Limits: By default, a shared mailbox includes 50 GB of storage. If the mailbox grows beyond this limit, you must assign an Exchange Online Plan license to increase its storage capacity and unlock additional mailbox features.
Understanding this architecture matters, because it explains exactly where manual PST export methods break down.
Why Do Organizations Need Shared Mailbox to PST Conversion?
|
Backup and Disaster Recovery Maintaining offline PST copies protects valuable business communication from accidental deletion, ransomware incidents, or tenant-level failures. |
Tenant Migration & Offboarding Before migrating between Microsoft 365 tenants or moving to another email platform, administrators often export mailbox data into PST format. |
|
Compliance and Legal Requirements Many organizations archive mailboxes to satisfy legal retention policies and eDiscovery requirements. |
Storage and License Optimization Archiving older shared mailbox content locally frees up cloud storage without permanent data loss. |
Approach 1: Manual Export via Outlook (And Why It Falls Short?)
The built-in Export to PST feature in Outlook is often the first choice for administrators, but it has several limitations when handling large-scale mailbox exports.
- Firstly, ensure Full Access permission is granted to your account on the shared mailbox (Add-MailboxPermission -Identity “SharedMailbox” -User “you@domain.com” -AccessRights FullAccess).
- Wait for auto-mapping to add the mailbox to Outlook, or add it manually via File >> Account Settings >> More Settings >> Advanced.
- Once visible, use File >> Open & Export >> Import/Export >> Export to a file >> Outlook Data File (.pst).
- Lastly, select the shared mailbox folders and export.
Challenges with this Manual Approach
- MAPI Dependency: Outlook’s built-in export feature only works if the shared mailbox has been successfully added to your Outlook profile. If the mailbox isn’t automatically mapped or configured correctly, the export process cannot begin until the connection is fixed.
- EWS is being phased out: Exchange Web Services (EWS) is an older SOAP-based protocol that many legacy export tools depend on. However, Microsoft is gradually deprecating it, which means tools built on EWS are becoming less reliable over time.
- Throttling Issues: Both EWS and Microsoft Graph API apply service protection limits to prevent excessive requests. If these limits are exceeded, the system returns an HTTP 429 “Too Many Requests” response along with a Retry-After header. Without proper handling, manual or basic export methods may pause or fail during the process.
- Attachment Size Ceiling: Microsoft Graph API supports items up to 150 MB, while classic MAPI is limited to 25 MB. Because of this difference, manual export methods may fail or cut off larger attachments.
- No Selective Control: Manual export typically pulls everything or nothing, with no ability to filter by date range, folder, or item type.
- Time-Prohibitive at Scale: For organizations with dozens of shared mailboxes, doing this manually per-mailbox is not practical.
Approach 2: eDiscovery/Content Search Export (Compliance Center)
Microsoft Purview’s Content Search and eDiscovery tools can export mailbox content to PST as well.
Limitations to be Aware Of
- Limited access permissions: This method requires elevated roles such as eDiscovery Manager or Organization Management, which are not available to standard administrators.
- Additional tool requirement: You must install and use the Microsoft Purview eDiscovery Export Tool, which is a separate utility with its own setup and dependencies.
- Search-driven export process: Instead of directly exporting folders, data is retrieved using search queries (KQL), making it more suitable for legal investigations but less convenient for simple backup tasks.
- Not suitable for bulk operations: This approach is not designed for large-scale or recurring exports across multiple shared mailboxes, making it inefficient for enterprise-wide backup scenarios.
Approach 3: Graph API-Based Export (Recommended for Bulk/Reliable Conversion)
As EWS is being phased out and manual or Outlook-dependent methods are not scalable, the most reliable modern solution is a Microsoft Graph API-based export engine. This is the technology our Macsonik Tenant to Tenant Migration Tool uses to perform conversions.
Microsoft Graph-Based Export Workflow
|
Authentication The application authenticates using OAuth 2.0 through Microsoft Entra ID (Azure AD). After an administrator grants the required permissions, the software securely obtains an access token to communicate with Microsoft Graph. |
PST Generation After retrieval, mailbox data is converted into a Unicode PST file that can be opened using Microsoft Outlook. |
|
Data Retrieval Messages are downloaded directly from Exchange Online while preserving:
|
Mailbox Discovery The software retrieves the mailbox folder structure, including:
|
Prerequisites for Exporting a Shared Mailbox to PST
- A Microsoft 365 tenant with the shared mailbox already created and accessible.
- Administrator or delegated permissions to access the shared mailbox.
- For manual Outlook export, your account must have Full Access permission to the shared mailbox.
- For Graph API-based export, the application must be granted the required Microsoft Graph API permissions with admin consent.
- Microsoft Entra ID (Azure AD) app registration (required only for the Graph API-based method), including:
- Tenant ID
- Client ID
- Client Secret (or certificate-based authentication, if applicable)
- Stable internet connection to ensure uninterrupted communication with Exchange Online during the export.
- Sufficient local disk space to store the exported PST file. Large shared mailboxes may require several gigabytes of free storage.
- Appropriate mailbox licensing, if the shared mailbox exceeds the default 50 GB storage limit, by assigning an Exchange Online Plan license before export.
Step-by-Step Guide to Exporting with the Software
- First, register the app in Azure AD/Entra ID and grant admin consent for the required Graph API application permissions.
- Launch the software and authenticate using your app registration credentials (Client ID, Tenant ID, Client Secret).
- Select the target shared mailbox(es): single or bulk mode.
- Apply optional filters: date range, specific folders, item types.
- Choose PST output format (Unicode recommended) and destination path.
- Start the process, the software handles throttling, retries, and checkpointing automatically.
- Finally, review the export summary and validate the generated PST in Outlook or a PST viewer.
Comparative Analysis of Mailbox Export Approaches
|
Capability |
Manual Outlook Export |
eDiscovery Export |
Our Graph API Software |
|
Requires Outlook installed |
Yes |
No |
No |
|
Depends on auto-mapping |
Yes |
No |
No |
|
Protocol |
MAPI/legacy EWS |
Content Search/ EWS |
Microsoft Graph API |
|
Handles throttling (429) |
No |
Partial |
Yes, retry with backoff |
|
Resumable on failure |
No |
Partial |
Yes, delta query + pagination |
|
Bulk/batch conversion |
No |
Limited |
Yes |
|
Selective export (date/folder) |
Limited |
Query-based |
Yes |
|
Ease of use for non-compliance admins |
Moderate |
Low |
High |
|
Metadata preservation |
Inconsistent |
Yes |
Full (flags, categories, read state) |
Real-Life Case Study: Exporting Shared Mailboxes Before a Microsoft 365 Tenant Migration
Issue: A mid-sized IT services company with 600 employees was migrating from one Microsoft 365 tenant to another after a corporate merger. The organization managed 35 shared mailboxes, some exceeding 40 GB, used across departments like Support, HR, Finance, and Sales.
Initially, the IT team used Outlook’s Export to PST method, but the process became inefficient due to auto-mapping issues, slow performance, mailbox-by-mailbox handling, and frequent export interruptions.
Solution: To overcome these challenges, the team switched to a Microsoft Graph API-based export solution using Microsoft Entra ID app registration and admin consent. They exported all shared mailboxes in bulk, applied filters for older data, and preserved full mailbox structure and metadata.
The solution handled throttling, retries, and resumable exports automatically, generating PST files directly from Exchange Online without Outlook dependency.
Result:
- Exported 35 shared mailboxes successfully in bulk.
- Removed dependency on Outlook and auto-mapping.
- Preserved folders, emails, attachments, contacts, and calendars.
- Reduced export time significantly through automation.
- Produced ready-to-use PST files for migration and compliance needs.
Conclusion
Shared mailboxes are an essential collaboration feature within Microsoft 365, but exporting them manually can be complex and inefficient. Traditional Outlook-based methods struggle with scalability, reliability, and automation.
Microsoft Graph API provides a modern approach by securely accessing Exchange Online directly, eliminating Outlook dependencies while preserving mailbox integrity. Organizations that regularly back up, archive, or migrate shared mailboxes can significantly reduce administrative effort by using a Graph API-powered solution.
Whether your goal is compliance, disaster recovery, tenant migration, or long-term archival, a Graph API-based Shared Mailbox to PST Converter delivers a faster, more secure, and enterprise-ready solution.
Frequently Asked Questions
Ans. Yes, Graph API-based tool connect directly to the mailbox via the cloud, with no dependency on a local Outlook client or MAPI profile.
Ans. This is usually caused by Autodiscover v2 resolution delays or caching issues. It can be worked around with PowerShell (AutoMapping $false plus manual profile addition), but this doesn’t affect Graph API-based exports since they bypass Outlook entirely.
Ans. Not for the long term. EWS is on Microsoft’s deprecation path for Exchange Online, and any tool still built on it will eventually stop working. Graph API is the supported, forward-compatible path.
Ans. Shared mailboxes have 50GB of storage by default. Larger mailboxes require an assigned Exchange Online Plan license to raise the limit
Ans. Any subsequent Graph API calls will return a 401 Unauthorized or InvalidAuthenticationToken error once the current bearer token expires (tokens are typically valid for about an hour). The tool’s pre-flight validation checks consent status before starting a job, but if consent is revoked during an active run, the job will fail on the next token refresh and should be restarted after consent is reinstated.
Ans. The full folder hierarchy is captured. The tool traverses childFolders navigation properties recursively from the mailbox root, reconstructing the complete IPM subtree, including custom user-created subfolders, rather than only exporting default folders.
About The Author:
I am Neeru Kuchhal, a Technical Content Writer who focuses on turning complex ideas into clear, engaging, and impactful content. I combine creativity with strategy to write blogs, web content, and technical articles that connect with the right audience and support brand goals. I believe great content is not just written. It is thoughtfully created to inform, build trust, and drive action.
Related Post
