Microsoft Outage History

Microsoft is up right now

Microsoft had 35 outages in the last 2 years totaling 3383h 18m of downtime — averaging 1.4 incidents per month.

There were 35 Microsoft outages since January 27, 2026 totaling 3383h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cloud.microsoft/ · Aggregated across Microsoft products

Major April 24, 2026 via Microsoft Azure

Multiservice impact for Azure Workloads in East US

Detected by Pingoru
Apr 24, 2026, 11:39 AM UTC
Resolved
Apr 25, 2026, 01:16 AM UTC
Duration
13h 37m
Affected: App Service — East USApplication Gateway — East USAzure Cache for Redis — East USAzure Data Factory — East USAzure Databricks — East USAzure Kubernetes Service (AKS) — East USAzure Service Fabric — East USAzure Synapse Analytics — East USAzure Virtual Desktop — East USVirtual Machine Scale Sets — East USVirtual Machines — East USAzure VMware Solution — East USBatch — East USAzure Red Hat OpenShift — East USAzure Database for PostgreSQL — East USAzure Database for PostgreSQL flexible servers — East USAzure Data Explorer — East USAzure Maps — East US
Timeline · 1 update
  1. monitoring Apr 24, 2026, 11:39 AM UTC

    Impact Statement: Starting at 11:39 UTC on 24 April 2026, a platform issue resulted in provisioning, scaling, and connectivity issues for customers with Azure workloads hosted in the East US region. This issue initially affected one availability zone in East US. As traffic was automatically rerouted and shared services were involved, some customers in other availability zones may have also experienced an impact. Current Status: We detected this issue through our automated monitoring, which identified an unusual increase in failures within the services supporting virtual machine and virtual machine scale set operations in the East US region. We have taken steps to stabilize the affected services and address the underlying issue, while continuing the investigation to determine contributing factors. The next update will be shared within 60 minutes, or as events warrant.

Read the full incident report →

Minor April 8, 2026 via Microsoft Consumer Products

Some users are unable to search, chat or call users in Microsoft Teams Free

Detected by Pingoru
Apr 08, 2026, 06:45 AM UTC
Resolved
May 21, 2026, 12:09 PM UTC
Duration
43d 5h
Affected: Microsoft Teams Free
Timeline · 3 updates
  1. monitoring Apr 28, 2026, 02:12 PM UTC

    User impact: Users are unable to search, chat or call users in Microsoft Teams Free. More info: Some new users who signed up during the impact window were incorrectly treated as already onboarded, causing onboarding and privacy consent screens to be skipped, their profiles to appear as “Unknown users” to others, and preventing them from being searchable or reliably reachable in chat. Current status: We've identified a recently deployed backend change is causing new Teams Free users to bypass required onboarding steps, leaving user profiles in an incomplete state. As a result, affected users can not be discovered, connect with others, or successfully complete chat request flows. We're analyzing all our available resources to identify a mitigation plan. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC Next update by: Wednesday, April 29, 2026, at 3:30 PM UTC

  2. monitoring Apr 29, 2026, 01:44 PM UTC

    User impact: Users are unable to search, chat or call users in Microsoft Teams Free. More info: Some new users who signed up during the impact window were incorrectly treated as already onboarded, causing onboarding and privacy consent screens to be skipped, their profiles to appear as “Unknown users” to others, and preventing them from being searchable or reliably reachable in chat. Current status: We're continuing to review various available mitigation strategies to determine the most effective method to relieve impact. As a workaround, affected users can sign into the mobile application and complete onboarding steps to make the desktop application function as expected. Start time: Wednesday, April 8, 2026, at 6:45 AM UTC Next update by: Wednesday, May 6, 2026, at 3:30 PM UTC

  3. monitoring May 06, 2026, 02:37 PM UTC

    User impact: Users are unable to search, chat or call users in Microsoft Teams Free. Current status: We're validating a fix to address the underlying issue. Due to the complexity of the deployment, the validation is taking longer than initially anticipated. Once the fix is finalized, we’ll confirm the update in our internal test environment to ensure it doesn’t introduce any regression, before progressing with a gradual rollout to the affected environment. We'll share an estimated completion timeline when one becomes available. Start time: Wednesday, April 8, 2026, at 6:45 AM UTC Next update by: Wednesday, May 13, 2026, at 3:30 PM UTC

Read the full incident report →

Minor April 8, 2026 via Microsoft Consumer Products

Some users are unable to search, chat, or call users in Microsoft Teams Free

Detected by Pingoru
Apr 08, 2026, 06:45 AM UTC
Resolved
May 21, 2026, 12:09 PM UTC
Duration
43d 5h
Affected: Microsoft Teams Free
Timeline · 2 updates
  1. monitoring May 13, 2026, 03:15 PM UTC

    User impact: Users are unable to search, chat, or call users in Microsoft Teams Free. Current status: We've completed validations of our fix within our internal testing environment and have initiated a gradual rollout of our fix to affected users. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC Next update by: Wednesday, May 13, 2026, at 5:30 PM UTC

  2. monitoring May 20, 2026, 03:20 PM UTC

    User impact: Users are unable to search, chat, or call users in Microsoft Teams Free. Current status: We're monitoring our fix deployment to ensure it has saturated throughout the entire affected environment before validating this issue is resolved. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC Next update by: Wednesday, May 20, 2026, at 5:30 PM UTC

Read the full incident report →

Minor April 8, 2026 via Microsoft Consumer Products

Some users may be unable to search, chat, or call users in Microsoft Teams Free

Detected by Pingoru
Apr 08, 2026, 06:45 AM UTC
Resolved
May 20, 2026, 12:02 PM UTC
Duration
42d 5h
Affected: Microsoft Teams Free
Timeline · 1 update
  1. resolved May 20, 2026, 04:12 PM UTC

    User impact: Users may have been unable to search, chat, or call users in Microsoft Teams Free. Final status: We've determined that a recent service update introduced the problem for the Microsoft Teams Free new user onboarding flow and caused new accounts to skip this flow entirely and appear as "unknown user." These affected "unknown" users were marked as non-searchable accounts, which resulted in impact. We've validated that our configuration change fix to correct this error has fully deployed throughout the affected environment and has successfully remediated all impact. Start time: Wednesday, April 08, 2026, at 6:45 AM UTC End time: Wednesday, May 20, 2026, at 12:02 PM UTC This is the final update for the event.

Read the full incident report →

Notice April 7, 2026 via Microsoft Foundry (Azure AI)

Azure Status Alert: Post Incident Review (PIR) – Azure OpenAI – GPT-5.2 availability degradation in 7 regions

Detected by Pingoru
Apr 07, 2026, 05:46 PM UTC
Resolved
Apr 07, 2026, 05:46 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 07, 2026, 05:46 PM UTC

    Azure Status Event Alert (Resolved) Start Time: 2026-03-09 23:20:00 UTC End Time: 2026-03-10 19:32:00 UTC Impacted Services: Azure OpenAI Service (Australia East, Central US, East US 2, Korea Central, Norway East, Sweden Central, UK South)

Read the full incident report →

Notice March 24, 2026 via Microsoft Foundry (Azure AI)

Azure Status Alert: Mitigated – Azure OpenAI Service – Availability degradation

Detected by Pingoru
Mar 24, 2026, 12:13 AM UTC
Resolved
Mar 24, 2026, 12:13 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 24, 2026, 12:13 AM UTC

    Azure Status Event Alert (Resolved) Start Time: 2026-03-09 23:20:00 UTC End Time: 2026-03-10 19:32:00 UTC Impacted Services: Azure OpenAI Service (Australia East, Central US, East US 2, Korea Central, Norway East, Sweden Central, UK South)

Read the full incident report →

Notice March 10, 2026 via Microsoft Foundry (Azure AI)

Azure Status Alert: Mitigated – Azure OpenAI Service availability degradation

Detected by Pingoru
Mar 10, 2026, 08:51 PM UTC
Resolved
Mar 10, 2026, 08:51 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 10, 2026, 08:51 PM UTC

    Azure Status Event Alert (Resolved) Start Time: 2026-03-09 23:20:00 UTC End Time: 2026-03-10 19:32:00 UTC Impacted Services: Azure OpenAI Service (Australia East, Central US, East US 2, Korea Central, Norway East, UK South)

Read the full incident report →

Major January 27, 2026 via Microsoft Foundry (Azure AI)

Azure Status Alert: Preliminary Post Incident Review (PIR) - Azure OpenAI Service - Issues in Sweden Central

Detected by Pingoru
Jan 27, 2026, 09:30 AM UTC
Resolved
Jan 27, 2026, 09:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jan 30, 2026, 08:14 PM UTC

    Azure Status Event Alert (Archived) Start Time: 2026-01-27 09:22:00 UTC End Time: 2026-01-27 16:12:00 UTC Impacted Services: Azure OpenAI Service (Sweden Central)

Read the full incident report →