How to Offboard Exchange Online Archives with Auto-Expanding Enabled
Question details
The user needs to know if it is possible to offboard an Exchange Online archive mailbox with auto-expanding enabled back to an on-premises Exchange Server and what properties need to be checked.

- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- Migrating or offboarding an Exchange Online mailbox and its auto-expanding archive back to an on-premises Exchange environment.
- Observed behavior
- The user requires clarification on the offboarding process, limitations regarding auto-expanding archives, and the specific PowerShell commands to verify archive readiness.
Before initiating the offboarding process, verify your on-premises Exchange Server version and ensure your hybrid environment configuration is up to date, as offboarding capabilities depend heavily on these factors.
Verify Archive Properties and Migration Scope
Use PowerShell to inspect both on-premises and Exchange Online archive properties to determine if the mailbox can be safely offboarded.
Offboarding an archive mailbox with auto-expanding enabled can be complex because on-premises Exchange Servers do not support the auto-expanding archive feature in the same way Exchange Online does. You must first determine if you are moving the archive, restoring data, or migrating the entire mailbox.
Determine whether your goal is to move only the archive mailbox, restore specific archive data, or perform a full migration of the primary and archive mailboxes together.
Open the Exchange Management Shell on your on-premises server and run the 'Get-Mailbox' cmdlet to inspect the current local archive properties and storage quotas.
Connect to Exchange Online PowerShell and run the 'Get-MailUser' cmdlet to check the archive status, specifically looking at the size and whether auto-expanding is actively utilizing additional storage space.
Because archive offboarding relies strictly on your hybrid configuration and Exchange versions, follow the official Microsoft migration documentation or contact Exchange Support if the auto-expanded archive exceeds on-premises storage limits.

Document Your Exchange Migration Plans with WPS Office
While WPS Office does not directly manage Exchange servers, it is the perfect lightweight alternative to Microsoft Office for creating detailed migration runbooks, tracking PowerShell scripts, and logging mailbox batch statuses.
- 1. Download and Install: Get WPS Office from the official website and install it on your workstation.
- 2. Create Migration Runbooks: Use WPS Writer to document your PowerShell scripts (like Get-Mailbox and Get-MailUser) and step-by-step offboarding procedures.
- 3. Track Mailbox Batches: Use WPS Spreadsheet to maintain a detailed list of users, archive sizes, and migration completion statuses.

Frequently Asked Questions
Can I offboard an auto-expanding archive that is over 100 GB?
Generally, no. On-premises Exchange environments do not support the auto-expanding archive architecture used in Exchange Online. If the archive has expanded beyond standard on-premises limits (typically 100 GB), you cannot natively offboard it and may need to export the data to a PST file instead.
What PowerShell commands should I use to check my archive size?
You should use 'Get-MailboxStatistics' in combination with 'Get-MailUser' in Exchange Online PowerShell to accurately read the total size of the archive and check if the auto-expanding feature has provisioned auxiliary mailboxes.
Does offboarding an archive mailbox affect the primary mailbox?
It depends on your migration batch configuration. In a hybrid environment, you can sometimes move an archive independently of the primary mailbox, but doing so with auto-expanding archives is highly restricted and often requires moving both simultaneously or neither.




