Service advisories for mailbox utilization in Exchange Online monitoring

An Exchange Online service advisory informs you about mailboxes that are on hold and at risk of reaching or exceeding their quota. These service advisories provide visibility to the number of mailboxes in your organization that might require admin intervention.

These service advisories are displayed in the Microsoft 365 admin center. To view these service advisories, you can go to Health > Service health > Exchange Online and then look for Mailbox Storage Limits under the Organization Scenarios, or you can go Health > Service health > Exchange Online and select the Active issues tab. Here's an example of a mailbox utilization service advisory under active issues.

Mailbox utilization service alert.

When you access the service advisory, you see a link under User Impact. Selecting that link opens a flyout window that lists affected mailbox GUIDs for your tenant. This list is limited to no more than 155 mailboxes.

Mailbox utilization service alert details view

If your tenant exceeds more than 155 mailboxes at or nearing their storage quota, visit your admin portal and access your mailbox usage report. Alternatively, the direct URL to the mailbox usage report is https://admin.microsoft.com/Adminportal/Home?source=applauncher#/reportsUsage/MailboxUsage.

Note

The mailbox usage report information could be 24 hours behind your mailbox utilization service advisory alert.

What do these service advisories indicate?

The service advisories for mailbox utilization inform admins about mailboxes on hold that are nearing the mailbox storage quota. The type of holds that that can be placed on mailboxes include Litigation holds, eDiscovery hold, and Microsoft 365 retention policies (that are configured to retain data). When a mailbox is on hold, users (or automated processes) can't permanently remove data from their mailbox. Instead, admins should configure Messaging Records Management (MRM) retention policies in Exchange Online (in line with their organization's compliance policies related to data retention) to move data from a user's primary mailbox to their archive mailbox.

If a mailbox on hold doesn't have an archive and reaches a critical or warning state, admins should enable archive mailboxes and enable auto-expanding archiving. Make sure the retention period for the archive policy assigned to the mailbox (which moves email from the primary mailbox to the archive mailbox) only retains data in the main mailbox for as long as needed. If nothing is done to resolve the quota issues identified by the mailbox utilization service advisory, users might not be able to send or receive email messages or meeting invites.

Mailboxes on hold without an archive

If a mailbox is on hold and is nearing or has reached its quota and doesn't have an archive, an admin can enable an archive mailbox (and potentially enable auto-expanding archiving) along with ensuring an MRM archive policy is applied to the mailbox. (An MRM archive policy is a retention policy in Exchange Online that moves items to the archive mailbox.) For more information about how holds interact with quotas and recommended quota sizes for the main mailbox and Recoverable Items folder, see Increase the Recoverable Items quota for mailboxes on hold.

Mailboxes on hold with an archive

If a mailbox is on hold, has an archive, and is nearing or has reached its Recoverable Items Quota, an admin can increase the quota for the Recoverable Items folder. For more information, see Increase the Recoverable Items quota for mailboxes on hold.

If an admin increases the Recoverable Items Quota, they should also make sure that an MRM archive policy that moves items to the archive mailbox is applied to the mailboxes. The retention period for the archive policy must be short enough so that items aren't retained too long in the primary mailbox before they're moved to the archive.

Note

MRM archive policies also move items from the Recoverable Items folder in the primary mailbox to the Recoverable Items folder in the corresponding archive mailbox. This capability helps prevent the mailbox from exceeding the quota for the Recoverable Items quota.

MRM retention policies in your organization

Archive retention policies can be configured in various ways, depending on your organization's needs. For detailed information about retention policies, see Retention tags and retention policies in Exchange Online. An admin can view existing retention policies by running the following command:

Get-RetentionPolicy | FL

Retention policies can be applied to and take different actions on mailboxes with or without archives. The following is a brief overview of common archive retention policy actions:

  • MovePrimaryToArchive and MoveDumpsterToArchive instruct the retention policy to move the contents of the main mailbox, or Recoverable Items folder respectively, to the mailbox's archive once the policy's conditions have been met. These tags are set by admins and apply regardless of a user's individual settings.
    • The retention policy applied to moving Recoverable Items content should be relatively short to ensure the user's primary mailbox doesn't reach its Recoverable Items quota.
  • A Personal Archive tag means this policy can be applied by users to their personal folders to archive content on the specified schedule.

MRM retention policies don't function as expected

Administrators possess the necessary tools to evaluate the cause of a nonfunctional retention policy and address any errors. Some common scenarios of failure include the policy not being correctly applied or failure to process a mailbox.

For information on troubleshooting retention policies, see Troubleshooting Retention Policies in Exchange Online.

How often will I see these service advisories?

If you don't resolve the quota issues, you can expect to see this type of service advisory every seven days. Subsequent service advisories might contain higher mailbox counts for other mailboxes that are nearing their quota. If you resolve quota issues, this service advisory only occurs when another mailbox with quota issues is identified.

More information