Microsoft 365 apps Outage History

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.

The outage impacted Microsoft 365 Apps with users reporting that My Apps and admin functions were not loading and performing poorly. Symptoms included sign-in/SSO issues, slow page loads, and failures accessing admin dashboards across regions. Microsoft 365 components such as My Apps, admin pages, Dynamics 365 Apps, and SharePoint login were affected, with reports coming from North America, Europe, and Asia, indicating a broad global impact. The incident began at Oct 29, 2025 4:01 PM UTC and lasted about 2 hours and 38 minutes, concluding around Oct 29, 2025 6:39 PM UTC.

No official Microsoft 365 status updates were published during the event. StatusGator recorded an Early Warning Signal at Oct 29, 2025 4:01 PM UTC based on user reports, indicating the issue was detectable before any formal acknowledgment. A high volume of user reports from around the world during the window of 16:00–18:30 UTC suggests widespread impact across North America, Europe, and Asia.

Microsoft 365 apps experienced a partial outage, with some users unable to access the service. The outage began on 9:17 AM UTC and was resolved by 4:27 PM UTC, lasting roughly 7 hours and 10 minutes. The disruption was limited to users served through the affected infrastructure.

Microsoft 365's status page showed two updates during the incident. The first stated that the team was reviewing service monitoring telemetry to isolate the source and establish a fix. The second indicated that the issue had been resolved and services were restored.

The outage prevented sign-in to Microsoft 365 accounts, blocking access to web and desktop Office applications including Outlook, OneDrive, and SharePoint for users across the United States. Reports described login failures, slow web portal access, and Outlook clients disconnecting. The incident began at 6:37 PM UTC and was resolved by 6:48 PM UTC.

StatusGator detected the issue at Oct 9, 2025 6:37 PM UTC based on early user reports, with observations starting around 6:30 PM UTC. The provider did not publish official status updates during the incident. The outage appeared to be regional to the United States, affecting sign-in to Microsoft 365 accounts across web and client apps.

An outage in Microsoft 365 apps degraded features that rely on Microsoft Purview Information Protection labels. Some users were unable to open email messages with Information Protection labels, access labeled files in SharePoint Online and OneDrive for Business, or open documents in Word, Excel, and other Microsoft 365 apps.

The outage began on Feb 13, 2025 2:27 AM UTC and was resolved by Feb 13, 2025 5:57 AM UTC, lasting about 3 hours and 30 minutes. The Microsoft 365 status page posted two updates during the incident to communicate the degradation and recovery.

An outage briefly affected Microsoft 365 apps by preventing some users from creating or running Office scripts in Excel. The issue impacted Office scripts functionality in both the web and desktop versions of Excel. The outage began at 3:17 PM UTC and lasted about 45 minutes, with service restored by 4:02 PM UTC.

An issue related to Multi-Factor Authentication (MFA) gating briefly affected access to some Microsoft 365 Apps. Users could experience sign-in difficulties or be unable to launch certain apps. The outage began on 10:42 AM UTC and was resolved by 12:07 PM UTC as Microsoft 365 redirected affected traffic and continued telemetry analysis to identify the root cause.

The Microsoft 365 status page reported the progression from the initial alert to a recovery, with the incident classified as a partial outage during its duration. The service provided two status updates during the event, outlining mitigations and the eventual restoration of normal access.