Microsoft 365 apps outage history

Some Microsoft 365 users could not access or protect content with Azure Rights Management (ARM) across services. Microsoft 365 apps acknowledged that ARM processing components were affected, which could prevent encryption or decryption of protected files and emails across ARM-enabled features. The issue began around 9:17 AM UTC and reflected the partial outage described on the status page.

The problem appeared limited in scope and was resolved by 10:37 AM UTC, with the service returning to normal. A small number of user reports were logged around 9:00 AM UTC, consistent with the observed impact.

An Azure Rights Management (ARM) access and protection issue affected Microsoft 365 services, preventing some users from accessing or protecting content. This could block encryption or decryption of protected files and emails, and disrupted ARM-based protections in workflows such as Microsoft Purview across Microsoft 365. Impact began at 9:27 AM UTC and was resolved by 12:22 PM UTC.

Microsoft 365 status updates showed the issue persisted in a degraded protection state through the morning, with services returning to normal after the final update. User reports were limited, suggesting a relatively narrow footprint focused on ARM-protected content operations across affected services.

Impact began with user reports around Sep 17, 2026 2:45 PM UTC, as many Microsoft 365 users experienced requests not returning results. Copilot on iPhone and other Microsoft 365 apps were notably unresponsive across mobile and desktop clients, affecting productivity and typical workflows.

StatusGator detected an Early Warning Signal at Sep 17, 2026 3:06 PM UTC ahead of any official acknowledgment. There were no published Microsoft 365 status updates during the incident, even as the volume of reports grew across regions. Users in North America and India reported widespread issues with Copilot and other 365 components, suggesting a broad impact across multiple services.

Global users were unable to load the Microsoft 365 website and sign in, with errors like 'Something went wrong. Try reloading.' The outage began at 11:08 PM UTC and lasted about an hour, with connectivity returning by 12:04 AM UTC. The disruption appeared worldwide, with reports spanning North America, Europe, Latin America, and Australia, indicating broad impact on access to the Microsoft 365 website. StatusGator detected the issue at 11:08 PM UTC, ahead of any official acknowledgment from Microsoft 365.

There were no official status updates from Microsoft 365 during the incident, and the status page did not reflect an acknowledged outage in that window. As the service recovered, users could access the site again and resume normal operations.

Outlook users across Microsoft 365 experienced a widespread disruption that prevented emails from loading or syncing, with reports of not sending or receiving messages and some items stuck in outbox. The impact appeared across Outlook web and desktop clients and was reported by users in multiple regions, beginning around 4:00 PM UTC and lasting into the late afternoon. The volume and spread of reports indicated a broad impact on the email experience for many users.

Users across regions experienced sign-in problems and activation prompts when trying to access Office 365 applications. Some tenants were unable to sign in or activate new licenses, which prevented access to Office 365 apps. The issue began when the Microsoft 365 status page transitioned to a warning at 2:52 PM UTC and updates noted ongoing monitoring and troubleshooting efforts, including activation prompts that could fail when signing in.

Over the next several hours, Microsoft documented telemetry reviews and steps to isolate the root cause, followed by incremental traffic restoration as the environment recovered. By 8:22 PM UTC the status returned to up and users in multiple regions — including the United States, United Kingdom, and Canada — began regaining access. The incident lasted roughly five and a half hours and affected the sign-in and license activation flow for Office 365 apps.

Users on iOS devices were unable to sign in to OneNote due to an ongoing issue in Microsoft 365 apps starting at 4:07 PM UTC. The problem was limited to OneNote on iOS devices with OneNote builds 16.112.717.0+ and did not indicate a full outage of all Microsoft 365 services. Workarounds included accessing OneNote via the web, temporarily removing the Authenticator to allow authentication through the in-app webview, or signing in to other Microsoft 365 apps first to bypass the sign-in flow.

The issue persisted over several days with continued user reports describing sign-in failures or slow responses related to OneNote on iOS. The incident was resolved when the status returned to up at 6:02 PM UTC.,

Microsoft 365 apps experienced a global outage that disrupted email delivery and several core services. The incident began at Jan 22, 2026 7:14 PM UTC and was resolved by Jan 22, 2026 10:45 PM UTC, with users unable to send or receive email and to sign in to Office apps, access the Exchange/Outlook services, Admin Center, and calendar features. A large volume of user reports during the event indicated widespread impact across regions and services including Exchange/Outlook, Office apps, and calendar access.

StatusGator detected the issue at Jan 22, 2026 7:14 PM UTC, based on user reports, ahead of any Microsoft status page acknowledgment. In the provided feed, there were no official Microsoft status changes posted during this window.

A high volume of user reports around 20:45–21:30 UTC indicated widespread impact across multiple regions, with issues including email delays, sign-in problems, and outages across Exchange, Outlook, Office apps, and related services like Admin Center and calendar access.

The Microsoft 365 download flow from the homepage experienced a partial outage due to a code issue in a recent service update that disrupted the license check process. Users attempting to download the Microsoft 365 desktop apps likely faced failures or delays. The outage began at Dec 4, 2025 6:47 AM UTC and lasted about 10 hours and 20 minutes, until Dec 4, 2025 5:07 PM UTC.

Microsoft 365's status page published two updates during the incident, acknowledging the problem and the ongoing effort to restore downloads. User feedback was limited, with reports describing failed downloads or stalled installers, and downloadable access returned once the issue was resolved, as reflected in the status page update to up.

Microsoft 365 desktop app installation on Windows devices was disrupted, blocking new installations for many users. Microsoft 365 attributed the problem to a misconfiguration in a newly released set of authentication components and said it was reconfiguring and redeploying those components to remediate the impact. The incident began on Nov 14, 2025 4:57 PM UTC and was resolved on Nov 18, 2025 10:17 PM UTC, lasting roughly 4 days and 5 hours. The provider posted two official updates describing the misconfiguration and the remediation steps. The impact appeared limited to Windows installations, with reports from multiple US regions describing failed installs and intermittent slowdowns during the installation process. After remediation, installation flows returned to normal.