Microsoft Azure Outage Disrupts Teams and 365 Services, Recovery Underway

A major Microsoft service outage crippled key platforms for users across the United States. The disruption primarily impacted the Eastern U.S. starting around 4 p.m. UTC. Services like Teams, Azure, Microsoft 365, and the Microsoft Store were affected.

The outage caused significant disruptions for businesses and individuals relying on these cloud tools. According to Reuters, the incident was tracked by Downdetector, which recorded thousands of user complaints.

DNS Failure Identified as Root Cause

Microsoft confirmed the problem stemmed from a DNS issue affecting Azure Front Door services. This led to widespread access problems and intermittent failures. Over 25,000 outage reports were logged for Azure and Microsoft 365 combined.

The company’s Azure Support team provided updates via social media platform X. They acknowledged the issue was causing delays and sporadic request failures for customers.

Microsoft Implements Recovery Process

Microsoft announced it had initiated a recovery deployment using a ‘last known good’ configuration. The firm stated this process would take approximately 30 minutes to fully deploy. After this, customers were expected to see initial signs of service restoration.

The tech giant clarified the outage was largely confined to the East US region. It was not a global service failure, though its impact was substantial for affected users.

The company advised users they could access the Azure management portal directly. However, some portal extensions, like Marketplace, might still experience loading issues during the recovery phase. No final ETA for full restoration was provided at the time of the last update.

The widespread Microsoft Azure outage highlighted the critical dependency many organizations have on cloud infrastructure. Service restoration efforts continue as engineers work to resolve the underlying DNS failure completely.

Info at your fingertips

What caused the Microsoft outage?

The outage was caused by a DNS problem. This issue specifically affected Azure Front Door services. It led to connectivity problems across several Microsoft platforms.

Which Microsoft services were affected?

Teams, Azure, Microsoft 365, and the Microsoft Store were all impacted. The outage generated over 25,000 user complaints. The Eastern United States was the primary region affected.

When did the service disruption begin?

The problems started at approximately 4 p.m. UTC. Microsoft began investigating the issue shortly after user reports surged. The company provided ongoing updates via its Azure Support account.

Is there a restoration timeline?

Microsoft has not provided a final ETA for full restoration. The company did deploy a recovery configuration expected to take 30 minutes. Users should see gradual service improvement during this process.

Was this a global outage?

No, Microsoft confirmed the outage was largely regional. The East US was the primary area experiencing service disruptions. Other global regions remained largely unaffected.