Microsoft 365 apps Outage History

The outage began on Dec 4, 2025 6:47 AM UTC and was resolved by Dec 4, 2025 5:07 PM UTC, lasting about 10 hours and 20 minutes. Microsoft 365 desktop app downloads from the Microsoft 365 homepage were blocked due to a recent service update that contained a code issue impacting the license check process.

During the incident, Microsoft 365 issued two status updates describing the issue and eventual resolution. The impact was limited to the download flow for desktop apps, with other Microsoft 365 services remaining unaffected by the outage. After the fix, downloads returned to normal.

Microsoft 365 desktop app installation on Windows devices experienced a degraded condition beginning on Nov 14, 2025 4:57 PM UTC after Microsoft identified a misconfiguration in newly released authentication components that prevented installation of the Microsoft 365 desktop apps on Windows devices. Users attempting to install faced errors or failed installations, affecting both individuals and organizations. The issue persisted as a degraded service for roughly 4 days, 5 hours, and 20 minutes, until Nov 18, 2025 10:17 PM UTC when it was resolved. The root cause was a misconfiguration in the authentication flow; remediation involved reconfiguring and redeploying the affected components.

Microsoft documented the remediation steps in the status updates, stating the plan to reconfigure and redeploy the authentication components to restore installation functionality. The incident progressed from warning to up, with the service restored by Nov 18, 2025 10:17 PM UTC. The issue primarily impacted Windows devices attempting to install the Microsoft 365 desktop apps during the degraded period.

Microsoft 365 apps experienced a partial outage that prevented some users from accessing the service. The incident began on Oct 13, 2025 9:17 AM UTC with the status page moving from operational to degraded, and it persisted until service was restored on Oct 13, 2025 4:27 PM UTC, lasting about 7 hours and 10 minutes.

Status updates indicated ongoing monitoring and an investigation to isolate the source of the issue. The provider issued two official status updates: one announcing the degraded access and later confirming restoration.

A subset of Microsoft 365 users experienced degraded access or functionality for items that rely on Microsoft Purview Information Protection labels. Impact included difficulties opening labeled email messages and accessing labeled files in SharePoint Online and OneDrive for Business, as well as working with labeled content in Word, Excel, and other Microsoft 365 apps.

During the incident, the service posted two updates to the status page. The outage lasted approximately 3 hours and 30 minutes, from 2:27 AM UTC to 5:57 AM UTC, and affected a subset of users across Email, SharePoint Online, OneDrive, and Office apps that rely on Information Protection labeling features.

An outage affected Office Scripts in Excel, impacting some users' ability to create or run scripts in Excel web and desktop. The incident began at Feb 5, 2025 3:17 PM UTC and was resolved by Feb 5, 2025 4:02 PM UTC, lasting about 45 minutes. Microsoft 365's status page indicated that the issue had been reproduced internally and that engineering teams were reviewing logs and telemetry to identify the root cause and develop a remediation plan; updates advised that remediation was in progress and the service was returning to normal. The provider issued 2 status updates during the incident.

An outage affected some Microsoft 365 Apps starting at Jan 13, 2025 10:42 AM UTC, when Multi-Factor Authentication gating prevented access for a subset of users. Microsoft redirected affected traffic and initial monitoring indicated improving availability. The incident persisted for approximately 1 hour and 25 minutes and was resolved by Jan 13, 2025 12:07 PM UTC when services returned to normal.

Microsoft issued two status updates during the incident, informing users that traffic was redirected and that ongoing telemetry was guiding efforts to identify the root cause of the unhealthy infrastructure. The disruption was limited to certain apps, with broader service remaining accessible.