Table of Contents
No Support for Auto-Expanding Archives in Any Version of Exchange Server
I was surprised that Microsoft had to announce that they have had to programmatically block any attempts to move auto-expanding archive mailboxes from Exchange Online to on-premises servers (MC467234, updated 24 November 2022). The new block should be effective worldwide by the end of December 2022.
Microsoft’s documentation has always been precise on the topic, saying “after auto-expanding archiving is enabled for a cloud-based archive mailbox, you can’t off-board that archive mailbox back to the on-premises Exchange organization. Auto-expanding archiving isn’t supported for on-premises mailboxes in any version of Exchange Server.”
I cannot remember Microsoft being anything but clear on this point. Since the announcement of the feature in June 2015 (the blog post is now offline), it has always been the case that only Exchange Online supported auto-expanding archives. The technology appeared in Exchange Online in 2016 but experienced some teething difficulties that meant that full worldwide deployment didn’t happen until early 2018. At that point, Microsoft wasn’t going to retrofit such a huge technical change on Exchange 2016 and nothing was done to implement auto-expanding archives in Exchange 2019, which is the current situation.
Block to Stop Offboarding Auto-Expanding Archives to Exchange Server
The interesting question is why Microsoft feels it necessary to introduce a new block. Obviously, some customers have tried to move mailboxes with auto-expanding mailboxes back to on-premises servers to find that things don’t go so well. The new block will cause any attempted moves to “gracefully fail with no data loss,” which is quite a relief.
Essentially, once an organization enables auto-expanding archives, it increases its connection to Exchange Online. It’s possible to offboard a mailbox with an auto-expanding archive, but only the primary mailbox can move to on-premises Exchange. The archive remains in the cloud. It remains possible to move Exchange Online mailboxes with simple archives back on-premises.
Important Points About Auto-Expanding Archives
Other important facts about auto-expanding archives include:
- Exchange Online supports the choice of auto-expanding archives for the entire organization or selected mailboxes.
- After an archive mailbox becomes auto-expanding, it is always auto-expanding. The archive mailbox cannot be transformed into a simple archive mailbox again. Although the archive status for mailboxes is visible in the Exchange admin center, EAC doesn’t tell you if the archive is simple or auto-expanding (Figure 1).
- Administrators must use PowerShell to work with auto-expanding mailboxes. For example, to enable an individual mailbox, run the Enable-Mailbox cmdlet:
Enable-Mailbox -Identity Terry.Hegarty -AutoExpandingArchive
- To find the set of mailboxes enabled for auto-expanding mailboxes, use the Get-EXOMailbox cmdlet to find the set of user and shared mailboxes and apply a client-side filter against the set to find those with the AutoExpandingArchiveEnabled property set to True.
Get-EXOMailbox -RecipientTypeDetails UserMailbox, SharedMailbox -Properties AutoExpandingArchiveEnabled -ResultSize Unlimited | Where-Object {$_.AutoExpandingArchiveEnabled -eq $True } | Format-Table DisplayName, RecipientTypeDetails
- Exchange Online automatically begins the auto-expanding process when an archive mailbox reaches 90% capacity (99 GB of the 110 GB assigned quota). Exchange Online increases the normal archive quota from 100 GB to 110 GB to accommodate auto-expansion. Some older mailboxes might still have 100 GB archive quotas even when enabled for auto-expansion. This problem can be fixed by re-enabling auto-expansion for the archive.
- You can’t recover or restore an inactive mailbox if it has an auto-expanding archive. Instead, you must export the data from the archive using the results of a content search and import the data into another mailbox.
- The limit for an auto-expanding archive is 1.5 TB (here’s a script to report archive status). Originally, Microsoft publicized auto-expanding archives as “bottomless,” but operational and software issues made it necessary to impose a limit.
- Shared mailboxes support auto-expanding archives if you assign an Exchange Online Plan 2 license to the mailbox.
Not Many Organizations Use Auto-Expanding Archives
My judgement is that this change is likely to affect relatively few organizations. First, not every Exchange Online organization uses archive mailboxes. Exchange Online makes large 100 GB primary mailboxes available to enterprise accounts, so there’s less need to offload old email to archive mailboxes. Only Exchange mailbox retention policies can move items automatically. Microsoft would like customers to use Microsoft Purview retention policies instead, but Purview policies can’t move items to the archive.
Second, of the total archive population, there’s probably a low percentage that is enabled for auto-expanding archives. It’s natural to leave mailboxes with simple archives unless they need auto-expansion. Those high-traffic mailboxes tend to be more important than the norm. For instance, those used for customer communications or by public-facing executives who receive large volumes of inbound email and need to retain copies for compliance purposes.
Mailboxes with auto-expanding archives must remain in the cloud. Apart from not being able to transfer these mailboxes to on-premises Exchange, it’s not altogether clear how you could move a large expanded archive anywhere else. Exporting the archive via a content search is the obvious answer, but processing up to 1.5 TB of data will take some time.
Although content search exports can accommodate up to 2 TB, the maximum size per PST for output is 2 GB and the search can upload a maximum of 2 GB of mailbox data per hour. All the data from the archive must upload to Azure before it can download to PSTs. Only a small number of auto-expanding archives will be more than 1 TB. In addition, search filters can reduce the amount of exported data to practical amounts at the expense of leaving some data behind. That might be an acceptable solution in some cases.
I’m not sure how many mailboxes will run into the new block. However, the news that a block is necessary will help organizations who have auto-expanding archives or those considering using auto-expanding archives to plan accordingly. It’s a good reminder that if you use a cloud-only feature, the technology is only available in the cloud.
Keep up with the changing world of the Microsoft 365 ecosystem by subscribing to the Office 365 for IT Pros eBook. Monthly updates mean that our subscribers learn about new developments as they happen.
Hi Tony,
We enabled Auto Expand Archiving at an Org level in Hybrid. We observed interesting behavior:
User A is an EXO mailbox with Full Mailbox Delegate Access to User B who is an onPrem Exchange 2016 Mailbox. User B is enabled for a remote Online Archive.
User A is only able to access the Primary Mailbox of User B – the Online Archive is not accessible (from Outlook or OWA). Have also tried to add manually rather than automap, but this makes no difference.
We also tried another User C on onPrem Exchange with Full Mailbox access to User B, but they also cannot access the Online Archive as a delegate.
Is this a Hybrid architectural limitation where access to remote archives is not possible where the primary mailbox in onPrem?
We also have not seen the auto expand storage enabled yet from Microsoft after 2 weeks since enabling at an Org level. We know this as we are trying to import mailbox data directly to the Online Archive, but it wont continue after the archive shows at approx. 107GB (from Outlook folder view stats).
Thank you in advance!
Rich.
I do not have a hybrid environment so anything I say is guesswork.
I have heard that it’s important to remove full access permissions from mailbox A and grant mailbox A full access to mailbox B again to make sure that access then includes the archive mailbox. You could try that.
As to the auto expand enablement, setting the switch only tells Exchange Online that expanding archives are available. Expansion doesn’t happen until it needs to. If you have moved more than 90 GB into an online archive and no expansion happens, I would file a call with Microsoft support and have them take a look.
It was a good idea Tony, but unfortunately after removing Full Access, allowing some time and then reapplying Full Access the remote online archive is still not accessible.
I’ll update this post when I have an answer regarding the Auto Expand Storage provisioning issue.
Rats. There’s one theory in the dust.
Have you asked Microsoft through a support incident? There’s a very good escalation engineer in Exchange support (whose name I can’t post for fear that he would kick me the next time we meet) who tends to do very well on issues with archives…
Yes, we have a ticket open with Microsoft. Their support is not what it once was, but that’s a different conversation! Hopefully we can get through to your guy! In any case will keep the forum posted of any final result.
Also MS source below mentions – “After you turn on auto-expanding archiving, an archive mailbox is converted to an auto-expanding archive when the archive mailbox (including the Recoverable Items folder) reaches 90 GB. It can take up to 30 days for the additional storage space to be provisioned.”
https://learn.microsoft.com/en-us/purview/enable-autoexpanding-archiving
Yep, that’s consistent with what I see. The assumption is that the normal archive will be able to cope with the growth while the internal processes to convert it into an auto-expanding archive happen. This involves the MRM process moving content from the normal archive to a newly provisioned expandable archive followed by a final synchronization and switchover. This work can only happen when service resources allow.
Just a follow-up to my last conversation threads above.
1. Delegate access to an onPrem mailbox user’s remote archive is not supported. The Primary mailbox needs to be migrated to EXO to support this.
2. Having multiple tickets raised with MS re when and how auto expand archive is provisioned I think its best summarised here:
https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784#:~:text=Why%20do%20I%20need%20to%20wait%2030%20days%20for%20expansion%20to%20take%20place%3F