Exchange Online access bug hits Outlook mobile and new Outlook for Mac for weeks

A Microsoft change adding a new virtual account broke Exchange Online access in Outlook mobile and new Outlook for Mac from 11 March 2026, and it recurred.

TechLogHub Engineering Team
April 3, 2026
3 min read
0 views

Share Article

Microsoft Still Working to Fix Exchange Online Mailbox Access Issues

From 11 March 2026, some Exchange Online users could not reliably reach their mailboxes from the Outlook mobile apps or the new Outlook for Mac. Microsoft traced it to a service change, rolled the change back and marked the incident resolved on 1 April, then had to reopen it under a new ID when tenants reported the problem was still happening. For teams that run on Microsoft 365, it is a case study in why "resolved" on a status page is not the same as resolved for your users.

What happened

Microsoft tracked the original problem as incident EX1256020 in the Microsoft 365 admin center. It said the issue started on Wednesday, 11 March 2026, and that a change "intended to introduce a new virtual account" caused the impact. Restarting affected infrastructure did not fix it. Around 21 March, Microsoft began reverting the change across affected environments as a longer-term fix, and it later marked the incident resolved on 1 April.

Affected tenants then reported that access was still failing intermittently. Microsoft re-added the issue to the admin center as EX1268771. As of 3 April, its update said engineers were restarting the "Notification Broker service" on affected parts of the Exchange Online infrastructure, working on measures to prevent recurrence, and still investigating the underlying root cause. Microsoft did not disclose affected regions or user counts, but classified the event as an incident, a label it uses for noticeable user impact.

It was one of several Exchange Online problems in a short window. BleepingComputer notes an early-March outage that blocked mailbox and calendar access over Outlook on the web, Outlook desktop and Exchange ActiveSync, a January outage affecting IMAP4, and a November 2025 incident affecting classic Outlook desktop.

Who is affected

  • Exchange Online (Microsoft 365) tenants whose users access mail through the Outlook mobile apps (iOS and Android) or the new Outlook for Mac.
  • Impact was intermittent and partial: not every user or tenant was affected.
  • Microsoft did not list Outlook on the web, classic Outlook for Windows or API clients among the clients affected by this incident.

What it means for developers and engineering teams

There is no vulnerability or code fix here for developers to apply. The lessons are operational:

  • Config changes can break specific clients. A backend change aimed at identity plumbing (a new virtual account) surfaced only on some client types. The same thing happens in your own services when a change to auth, service accounts or notification paths is tested against one client but not others. Canary rollouts segmented by client type catch this.
  • Status pages lag reality. The first incident was closed while users were still affected. If email or calendar access is part of a critical workflow (on-call paging, customer support, approvals), you need your own signal rather than relying on a vendor's status.
  • Service health is available by API. Microsoft Graph exposes Microsoft 365 service health and incidents through the service communications API (/admin/serviceAnnouncement/issues). Piping that into Slack, Teams or your incident tool means IT hears about incidents like EX1268771 without someone checking the admin center by hand.

What to do now

  1. Check the Microsoft 365 admin center under Health > Service health for EX1256020 and EX1268771 and confirm their current state for your tenant.
  2. Automate incident ingestion. Register an app with the ServiceHealth.Read.All application permission and poll:
    GET https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/issues?$filter=service eq 'Exchange Online'
    Post new or updated issues to your chat or paging tool.
  3. Give users a fallback. Tell staff that Outlook on the web is an alternative path when a mobile or Mac client misbehaves during a known incident.
  4. Add a synthetic check if mail access is business-critical: a scheduled job that signs in as a test mailbox and reads a message, alerting on failure.
  5. Track repeat incidents per service over a quarter. A pattern of outages is useful evidence when you review vendor SLAs and service credits.

Related on TechLogHub

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.