🔍 The Symptoms

🧠 Root Cause

Exchange Online archive mailboxes have an initial archive capacity commonly treated as 100 GB for import and migration planning. When auto-expanding archive is enabled, Exchange Online can increase archive storage by provisioning additional archive space over time.

However, this expansion is not instant. Auto-expanding archive does not behave like pre-allocated storage — it does not immediately create hundreds of gigabytes of writable archive capacity for a mailbox.

✅ Auto-Expanding Archive Is Designed For

• End-user archive growth through normal mailbox usage
• Retention policy-based archive movement
• Managed Folder Assistant processing
• Long-term archive expansion over time
• Gradual mailbox archive growth based on service behaviour

❌ Auto-Expanding Archive Is NOT Designed For

• Large one-time PST imports
• Bulk archive migration into a single mailbox
• Direct import into auxiliary archive mailboxes
• Pre-provisioning archive storage above supported service behaviour
• Forcing large archive expansion before data is naturally moved or accumulated

⚠️ Important Technical Limitation

📋 Microsoft Support and Technical Limitation

Microsoft does not support pre-provisioning archive mailbox size above the supported service limit for immediate bulk ingestion. Auto-expanding archive cannot be used as a workaround to import or migrate hundreds of gigabytes of data in one operation.

💡 Important Clarification About the 1.5 TB Limit

🛠️ Step-by-Step Resolution

Install-Module ExchangeOnlineManagement -Scope CurrentUser -Force

Import-Module ExchangeOnlineManagement

Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com

Get-Mailbox -Identity user@yourdomain.com |
Format-List DisplayName,UserPrincipalName,ArchiveStatus,ArchiveName,ArchiveQuota,ArchiveWarningQuota

# Enable the archive mailbox
Enable-Mailbox -Identity user@yourdomain.com -Archive

# Verify the archive is now active
Get-Mailbox -Identity user@yourdomain.com |
Format-List DisplayName,ArchiveStatus,ArchiveQuota,ArchiveWarningQuota

# Enable auto-expanding archive for a specific mailbox
Enable-Mailbox -Identity user@yourdomain.com -AutoExpandingArchive

# Verify the setting
Get-Mailbox -Identity user@yourdomain.com |
Format-List DisplayName,AutoExpandingArchiveEnabled,ArchiveStatus,ArchiveQuota,ArchiveWarningQuota

# Enable auto-expanding archive for the entire organisation
Set-OrganizationConfig -AutoExpandingArchive

# Verify the organisation configuration
Get-OrganizationConfig |
Format-List AutoExpandingArchiveEnabled

Get-MailboxStatistics -Identity user@yourdomain.com -Archive |
Format-List DisplayName,TotalItemSize,ItemCount,StorageLimitStatus

Get-Mailbox -Identity user@yourdomain.com |
Select-Object DisplayName,UserPrincipalName,ArchiveStatus,ArchiveQuota,ArchiveWarningQuota,AutoExpandingArchiveEnabled,RetentionPolicy |
Format-List

Get-MailboxStatistics -Identity user@yourdomain.com -Archive |
Select-Object DisplayName,TotalItemSize,ItemCount,StorageLimitStatus

# Check the mailbox retention policy
Get-Mailbox -Identity user@yourdomain.com |
Format-List DisplayName,RetentionPolicy

# Review the retention policy configuration
Get-RetentionPolicy -Identity RetentionPolicyName |
Format-List Name,RetentionPolicyTagLinks

# Review available retention tags
Get-RetentionPolicyTag |
Select-Object Name,Type,AgeLimitForRetention,RetentionAction

# Assign the correct retention policy if required
Set-Mailbox -Identity user@yourdomain.com -RetentionPolicy RetentionPolicyName

# Start Managed Folder Assistant processing immediately
Start-ManagedFolderAssistant -Identity user@yourdomain.com

# Validate archive statistics after processing
Get-MailboxStatistics -Identity user@yourdomain.com -Archive |
Format-List DisplayName,TotalItemSize,ItemCount,StorageLimitStatus,LastLogonTime

# Confirm archive settings
Get-Mailbox -Identity user@yourdomain.com |
Format-List DisplayName,ArchiveStatus,ArchiveQuota,ArchiveWarningQuota,AutoExpandingArchiveEnabled

📊 Supported Migration Design

🖥️ GUI Method: Microsoft Purview PST Import Planning

If using Microsoft Purview PST Import, follow these steps in the portal:

1. Go to the Microsoft Purview portal
2. Open Data lifecycle management or the relevant Import area for your tenant
3. Create a PST import job
4. Upload PST files using the Microsoft-supported network upload process
5. Map PST files to target mailboxes
6. Ensure the archive target has enough available capacity before starting the import
7. Avoid mapping more PST data than the target mailbox archive can currently accept

📌 Practical Example

🚫 Common Misconceptions

💡 Best Practices & Recommendations

• Validate archive capacity before migration. Always run Get-MailboxStatistics -Archive before importing PST or archive data
• Use phased migration for large archives. Do not attempt to move hundreds of gigabytes into a single archive mailbox in one operation
• Enable auto-expanding archive before long-term growth is required. Do not wait until the archive is already at capacity
• Use retention policies where possible. Auto-expanding archive is intended to work with normal mailbox and retention processing
• Avoid unsupported workarounds. Do not attempt to force data directly into auxiliary archive mailboxes
• Use least-privilege administration. Assign Exchange Administrator or a scoped custom role instead of Global Administrator for routine operations
• Document migration batches. Track source size, imported size, archive size, and target mailbox status after every migration phase

📝 Final Technical Summary

📚 References & Further Reading

• 🔗 Enable auto-expanding archiving in Microsoft Purview — Microsoft Learn
• 🔗 Use network upload to import PST files to Microsoft 365 — Microsoft Learn
• 🔗 Enable archive mailboxes in Microsoft Purview — Microsoft Learn
• 🔗 Learn about retention policies and retention labels — Microsoft Learn
• 🔗 Messaging records management in Exchange Online — Microsoft Learn
• 🔗 Exchange Online PowerShell — Microsoft Learn