Stop Paging the On-Call Admin for False Exchange Online Alarms: Managing the 100 GB Rollout

Microsoft’s announcement that Exchange Online mailboxes for Business Basic, Standard, and Premium are jumping from 50 GB to 100 GB is objectively good news for end users. More space for archives, fewer "mailbox full" tickets, and happier clients.

But for the IT Operations engineer or the MSP technician holding the pager, this rolling update (June through September 2026) is a classic recipe for alert disaster.

Here is the reality: You have a tenant with 500 users. Microsoft randomly applies the new 100 GB license plan to User A today, but User B is still stuck at 50 GB. If your monitoring tools are still configured with static thresholds—say, alerting when a mailbox hits 45 GB—your on-call team is about to have a very bad few months.

The Hidden Ops Nightmare: The Context Gap

The problem isn't the storage increase; it's the lack of context in your current alerting stack.

Most traditional RMMs and standalone monitoring tools operate on simple arithmetic: if (CurrentUsage > Threshold) then Alert(). They treat every mailbox exactly the same. They don't inherently know that User B has a hard cap of 50 GB while User A now has room to breathe.

This creates two distinct failures in your Alert Management & On-Call operations:

The False Positive (Noise): Your monitoring script sees User A at 60 GB used. Under the old rules, this is impossible. If you didn't update your threshold globally (which you can't do yet because the rollout is staggered), you might get confusing data, or worse, you set the threshold to 90 GB to be "safe." Now, User B hits 46 GB—nearly full—and no alert fires because the threshold is too high. The user stops receiving email, and you hear about it from an angry client, not your dashboard.
The Pager Fatigue: When Microsoft flips the switch for a batch of users, your monitoring environment changes state overnight. If your tool isn't dynamic, you might see a sudden spike in "usage anomalies." The on-call engineer gets woken up at 2:00 AM. They log in, check the admin center, see the license update happened, and realize it's not an outage—it's just a change they have no visibility into.

This is tool sprawl in action. Your monitoring tool screams, your RMM doesn't see the license change, and your helpdesk gets flooded with "is my email broken?" tickets. The signal is lost in the noise.

How AlertMonitor Solves This

At AlertMonitor, we operate on a core belief: Alert fatigue isn't a volume problem — it's a signal quality problem.

When the M365 rollout hits your environment, AlertMonitor doesn't just see a number going up. We ingest the context of the asset.

1. Dynamic Thresholding Based on License State

Instead of a static "Alert at 45 GB" rule for everyone, AlertMonitor looks at the service plan associated with the user. We detect if the user is on the legacy 50 GB cap or the new 100 GB cap. The alert threshold adjusts automatically per user.

The Old Way: Admin sets alert at 45 GB. User A (100 GB limit) alerts at 46 GB (waste of time). User B (50 GB limit) alerts at 46 GB (critical).
The AlertMonitor Way: We calculate "Percentage Used" against the provisioned limit for that specific user. We only page the on-call engineer if User B hits 90% of their specific limit. User A at 46 GB is treated as healthy.

2. Intelligent Deduplication and On-Call Routing

During this rollout, you might see status changes for hundreds of mailboxes. A lesser tool would spawn a hundred individual tickets or pages.

AlertMonitor uses smart deduplication. We recognize that "Mailbox Quota Increased" is a systemic change event, not a device failure. We can suppress the noise for the on-call team but log the event in the audit trail. If a mailbox genuinely fills up post-rollout, we escalate that specific signal to the Exchange Administrator immediately, bypassing the generalist queue.

3. The Unified Dashboard

You don't need to toggle between the Microsoft 365 Admin Center to check license status and your RMM to check disk usage. AlertMonitor brings the mailbox health, the license tier, and the user support ticket history into one view. When the alert fires, the technician sees why it's firing, the user's current quota, and recent changes—all in one pane.

Practical Steps: Audit Your Quota Readiness

You don't have to wait for AlertMonitor to get visibility into this. You can run a quick audit today to see which of your users are at risk during this transition period.

Run the following PowerShell script to identify users who are currently consuming more than 80% of their quota. This script dynamically checks the ProhibitSendQuota, so it will automatically adjust for users who have received the 100 GB update versus those who haven't.

PowerShell

# Connect to Exchange Online first
# Connect-ExchangeOnline

$Mailboxes = Get-Mailbox -ResultSize Unlimited
$AtRiskUsers = @()

foreach ($Mailbox in $Mailboxes) {
    $Stats = Get-MailboxStatistics -Identity $Mailbox.Identity
    
    # Convert Quota to GB for easier calculation
    # Using ProhibitSendQuota as the hard limit
    $QuotaBytes = ($Mailbox.ProhibitSendQuota -replace "[^\d]")
    
    if ($QuotaBytes -gt 0) {
        $QuotaGB = [math]::Round($QuotaBytes / 1GB, 2)
        $UsedGB = [math]::Round($Stats.TotalItemSize.Value.ToBytes() / 1GB, 2)
        
        if ($QuotaGB -gt 0) {
            $PercentUsed = ($UsedGB / $QuotaGB) * 100
            
            # Flag users over 80% usage regardless of their specific quota tier
            if ($PercentUsed -gt 80) {
                $AtRiskUsers += [PSCustomObject]@{
                    User              = $Mailbox.UserPrincipalName
                    DisplayName       = $Mailbox.DisplayName
                    UsedGB            = $UsedGB
                    QuotaGB           = $QuotaGB
                    PercentUsed       = [math]::Round($PercentUsed, 2)
                    IssueDate         = Get-Date
                }
            }
        }
    }
}

# Output the report
if ($AtRiskUsers.Count -gt 0) {
    $AtRiskUsers | Sort-Object PercentUsed -Descending | Format-Table -AutoSize
} else {
    Write-Host "No users currently exceeding 80% of their mailbox quota." -ForegroundColor Green
}

The AlertMonitor Workflow

Once you've identified your at-risk users, you need a system that watches them intelligently:

Ingest: Connect AlertMonitor to your Microsoft 365 environment.
Contextualize: AlertMonitor reads the ProhibitSendQuota dynamically, just like the script above.
Route: Configure an escalation policy. If a user hits 90%, send a low-severity email to the helpdesk to clean up the mailbox. If they hit 98%, page the on-call Exchange admin via SMS/Slack.
Resolve: When the admin clears space, AlertMonitor auto-resolves the alert, creating a closed-loop record for your SLA reporting.

Don't let a storage upgrade turn into a management headache. Use the transition to 100 GB as a catalyst to fix your alerting strategy once and for all.

Related Resources

AlertMonitor Alert Management & On-Call Operations AlertMonitor Platform Overview Book a Demo Alert Management & On-Call Operations Resources