Microsoft 365 favicon

Microsoft 365 outage on 2026-10-27

microsoftonline.com
October 2026 27 Minor incident

Exchange Online had intermittent failures when accessed through REST APIs for 9 hours 3 minutes on 27 October 2026. Microsoft traced the fault to its own service change, not to anything on your end.

Started

15:56 UTC

Duration

Lasted 9h 3m

Source

IsDown

Next time

Microsoft 365 is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Exchange Online

What happened?

Microsoft's status page logged one incident on Exchange Online, starting at 15:56 UTC and lasting 9h 3m. The title describes intermittent errors or failures when accessing Exchange Online through REST APIs, which covers any app or integration calling Exchange through that interface rather than through Outlook's own client protocols. Six updates were published over the day. The first, at 16:06, said Microsoft was reviewing telemetry to find the cause. By 17:17, Microsoft reported it had identified a recent service change intended to optimise directory functionality as the likely source, and said it was disabling that change in a portion of affected environments to test the theory. Updates at 19:15 and 21:10 describe Microsoft extending that rollback to more environments while watching telemetry, with no firm resolution timeline given at either point. At 22:52 Microsoft said it had validated that disabling the change fixed the problem with no side effects, and that it was continuing the rollout to finish remediation, expecting completion by its next scheduled update. No update after that is on record, so the close of the incident is not documented with a timestamp beyond the 9h 3m duration figure. No user reports were filed during the window. The fault, as Microsoft describes it, sat in a directory-related change on its own infrastructure rather than in anything a customer configured.

Learning

Microsoft's own account places this fault inside its infrastructure, in a service change to directory functionality that affected how REST API requests to Exchange Online were processed. That is a layer you cannot see or test from your own environment, because your side of the integration only sees the REST calls failing intermittently, not the directory change behind them. An external check hitting Exchange Online's REST endpoint during this window would likely have shown the same intermittent pattern Microsoft describes, so there is no contradiction to resolve here, just a fault that originated entirely on the provider's side. In the last 90 days Microsoft has logged 58 such incidents with a median duration of 8 hours 12 minutes, so a multi-hour REST outage on Exchange Online is not unusual for this service. If your product depends on Exchange Online's REST APIs, watching your own endpoints only tells you your half is fine. It does not tell you whether Microsoft's directory layer is mid-rollback. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.