Microsoft had 35 outages in the last 2 years totaling 947h 28m of downtime — averaging 1.4 incidents per month.
There were 35 Microsoft outages since January 27, 2026 totaling 947h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
Azure Status Event Alert (Resolved) Start Time: 2026-05-29 09:39:00 UTC End Time: 2026-05-29 17:05:00 UTC Impacted Services: Azure OpenAI Service (Global)
What happened?Between 21:45 UTC and 23:23 UTC on 15 June 2026, Azure customers leveraging services which depend upon Microsoft Artifact Registry (MAR) may have experienced 401 authentication errors when attempting to pull images from MAR . This incident is now mitigated. Further details will be provided directly to impacted customers through the Azure Portal.
Impact Statement: Starting at 21:45 UTC on 15 June 2026, a subset of Azure customers leveraging services which depend upon MCR (Microsoft Container Registry) for storing images may experience 401 authentication errors for requests attempting to pull Microsoft images from mcr.microsoft.com.Current Status: We detected this issue via internal service monitoring upon identifying a spike of 401 errors. We’ve identified a potential underlying factor to be a recent update which introduced a code regression, and we've completed roll out of a hotfix to address the code regression and mitigate impact for affected customers. We are closely monitoring internal telemetry to validate full mitigation and prevent further occurrences. The next update will be provided within 60 minutes, or as events warrant.
We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We’ve identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly.
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold. Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings. This communication serves as a preliminary notification about a potential issue affecting your service.
User impact: Users may be unable to access the Microsoft Copilot desktop or web app. Current status: We’re reviewing our telemetry to determine the specific impact and isolate the root cause. Next update by: Monday, June 01, 2026, at 5:00 PM UTC
User impact: Users may be unable to access the Copilot desktop or web app. Current status: We're working on getting logs from impacted users to focus our investigative efforts to isolate the source of impact. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 5:00 PM UTC
User impact: Users may be unable to access the Copilot desktop or web app. Current status: We've received logs from impacted users and are reviewing them to identify the root cause. We're also continuing to monitor our telemetry to determine mitigating actions we can implement in the interim as our investigation progresses. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 6:00 PM UTC
User impact: Users may be unable to access the Copilot desktop or web app. Current status: We identified a routing issue which is sending Copilot traffic to a portion of infrastructure that is unhealthy, resulting in the access and timeout errors. We're rerouting requests to healthy infrastructure and our telemetry is starting to show service health recovery. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 6:00 PM UTC
User impact: Users may have been unable to access the Copilot desktop or web app. Final status: We've rerouted requests to healthy infrastructure and have confirmed through our telemetry that service health has recovered. Start time: Monday, June 01, 2026, at 1:55 PM UTC End time: Monday, June 01, 2026, at 5:52 PM UTC
User impact: Users may be unable to use Microsoft Copilot. Current status: We're reviewing service telemetry to isolate the source of the issue. Next update by: Friday, May 29, 2026, at 5:30 PM UTC
User impact: Users may be unable to use Microsoft Copilot. Current status: We've identified high utilization on the underlying infrastructure that the Copilot LLM APIs use and are applying mitigations. Additionally, at the Copilot service level, we're reviewing options to change routing paths, throttling rules and retry logic to allow the underlying infrastructure to recover. Next update by: Friday, May 29, 2026, at 6:30 PM UTC
User impact: Users were unable to use Microsoft Copilot. Final status: The underlying infrastructure that the Copilot LLM APIs use has recovered after the mitigation actions were applied. We monitored the environment for an extended period of time and have validated that service has been restored. Start time: Friday, May 29, 2026, at 2:30 PM UTC End time: Friday, May 29, 2026, at 5:35 PM UTC This is the final update for this event.
Azure Status Event Alert (Resolved) Start Time: 2026-05-29 09:39:00 UTC End Time: 2026-05-29 12:46:52 UTC Impacted Services: Azure OpenAI Service (Global)
Impact Statement: Starting at 09:39 UTC on 29 May 2026, you have been identified as a subset of customers using Azure OpenAI service in multiple regions who may experience degraded request success where some requests returned errors or failed to complete. Current Status: We identified this issue through internal automated service monitoring after detecting a drop in call success rates. Our investigation indicates that the issue is linked to elevated server-side errors within a backend service layer in the affected region. We are actively investigating and working to determine the full scope and mitigation steps. The next update will be provided within 60 minutes, or sooner if there are significant developments.
Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region. Engineers are actively investigating the issue and working to restore network stability. Some requests may succeed upon retry as connectivity intermittently recovers. We are sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.
Impact Statement- Starting at 04:27 UTC on 29 May 2026, customers may experience increased latency, intermittent connectivity, or timeouts when accessing resources hosted in the West US 2 region, due to a power event. We are in process of recovering power and working to restore infrastructure in the region. We started seeing partial recovery and will be sending targeted communications to impacted customers through the Azure Service Health dashboard. The next update will be provided within 60 minutes.
Impact: From 08:40 UTC, 27 May 2026, some customers using Azure Synapse Analytics (private link) may experience delays or failures accessing Synapse Studio or workspaces across multiple regions. As of now mitigation is in progress, and we are seeing initial signs of recovery.
Impact: From 08:40 UTC, 27 May 2026, some customers using Azure Synapse Analytics (private link, East US) may experience delays or failures accessing Synapse Studio or workspaces. We detected elevated connection failures via automated monitoring and are actively investigating.
User impact: Users may see failures when accessing Microsoft Copilot More info: Users may be presented with a 401-error response code. Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to users. We'll provide an update within 30 minutes.
User impact: Users may have seen failures when accessing Microsoft Copilot. More info: Users may be presented with a 401-error response code. Final status: We've completed a deployment to roll back to the most recent stable version of the service. Through our service side telemetry, we've confirmed that the service has been restored to a healthy level. Start time: Thursday, May 14, 2026, at 1:16 PM UTC End time: Thursday, May 14, 2026, at 5:00 PM UTC This is the final update for this event.
User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
User impact: We're checking for potential impact to your users. Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication has expired. This is the final update for this event.
User impact: Users may be unable to select "Allow editing" when using Copilot through Word or Excel. More info: Affected users may be unable to click on the drop-down menu to select "Allow editing" and may only be able to utilize "Chat mode" for Copilot queries through Word or Excel. Current status: We've received reports from a subset of users who have stated they are unable to select "Allow editing" when using Copilot through Word or Excel. We've isolated that a recent update intended to add additional agent functionality for Copilot premium users incorrectly marked "Allow editing" and other agent mode functionalities to be unavailable to non-premium users. We're deploying a code fix to address this and we anticipate the code fix to be fully deployed by our next scheduled update. Start time: Friday, May 01, 2026, at 4:17 PM UTC Next update by: Tuesday, May 05, 2026, at 6:00 PM UTC
User impact: Users may be unable to select "Allow editing" when using Copilot through Word or Excel. More info: Affected users may be unable to click on the drop-down menu to select "Allow editing" and may only be able to utilize "Chat mode" for Copilot queries through Word or Excel. Current status: Our fix deployment is currently at 90 percent saturation but is taking longer than expected to complete. We're working to expedite the remainder of our deployment, and we anticipate the code fix to be fully deployed by our next scheduled update. Start time: Friday, May 01, 2026, at 4:17 PM UTC Next update by: Wednesday, May 06, 2026, at 12:00 AM UTC
User impact: Users may be unable to select "Allow editing" when using Copilot through Word or Excel. More info: Affected users may have been unable to click on the drop-down menu to select "Allow editing" and may have only been able to utilize "Chat mode" for Copilot queries through Word or Excel. Final status: We confirmed that an eligibility check error introduced in a recent update caused limited access for users. We developed and deployed a fix to correct the offending update, and after a period of monitoring the service health telemetry, confirmed that the errors associated with impact have been resolved and the issue was remediated by our actions. Start time: Friday, May 1, 2026, at 4:17 PM UTC End time: Monday, May 4, 2026, at 11:32 PM UTC This is the final update for the event.
User impact: Affected users may have been unable to use Copilot services and features. More info: Prompts to Copilot may have returned an error message stating "Oops, Something happened. Can you try again?" Final status: We observed and mitigated an infrastructure issue that caused issues accessing Microsoft Copilot. We redirected traffic to healthy infrastructure and have confirmed that the issue is resolved. Start time: Wednesday, April 29, 2026, at 1:51 PM UTC End time: Wednesday, April 29, 2026, at 3:28 PM UTC This is the final update for the event.
User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
User impact: We're checking for potential impact to your users. Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication has expired. This is the final update for the event.