Daily Crunch: ‘Network issue’ causes cloud outage that takes down multiple Microsoft services for 4+ hours
The outage affected Office 365, SharePoint, Dynamics 365, Azure Active Directory and more
Microsoft today acknowledged that a major cloud outage that took down multiple Microsoft 365 services for more than four hours yesterday was caused by a “network issue.” The outage, which began at around 11:30 am Pacific, also impacted Office 365, SharePoint, Dynamics 365, Azure Active Directory and more.
The company says the issue has been resolved and that “most users should now have full access to all services,” though it adds that “a small number of users” may still experience issues.
This is clearly a major outage, and Microsoft says it will provide a full post-mortem report later this week. For now, it says the issue was caused by “a configuration error” that led to “a portion of traffic” being “inadvertently misrouted.”
- Microsoft today acknowledged that a major cloud outage that took down multiple Microsoft 365 services for more than four hours yesterday was caused by a “network issue.”
- The outage, which began at around 11:30 am Pacific, also impacted Office 365, SharePoint, Dynamics 365, Azure Active Directory and more.
- The company says the issue has been resolved and that “most users should now have full access to all services,” though it adds that “a small number of users” may still experience issues.
- This is clearly a major outage, and Microsoft says it will provide a full post-mortem report later this week.
- For now, it says the issue was caused by “a configuration error” that led to “a portion of traffic” being “inadvertently misrouted.”
Daily Crunch: ‘Network issue’ causes cloud outage that takes down multiple Microsoft services for 4+ hours
It was a tough day for Microsoft’s cloud computing business Azure, with multiple services down for more than four hours due to a “network issue.”
The company first acknowledged the issue at 10:54AM PT, saying that “a small subset” of customers were having trouble accessing various cloud services.
Four hours later, at 2:54PM PT, Microsoft said it had identified the root cause and implemented a fix, but that “full recovery” would take “a few more hours.”
The company didn’t provide any details about what caused the problem, but The Register reported that it was caused by “a string of DNS outages.”
The outage affected a wide range of services, including:
- Azure Active Directory
- Azure DevOps
- Azure DNS
- Azure DevOps Server
- Azure DevTest Labs
- Azure IoT Hub
- Azure Kubernetes Service
- Azure Load Balancer
- Azure Monitor
- Azure Site Recovery
- Azure SQL Data Warehouse
- Key Vault
- Power BI Embedded
- Visual Studio Online
This is far from the first time we’ve seen an interruption in Microsoft’s cloud services — a DNS problem took down Azure for a couple hours in February, for example.
Microsoft is far from alone in this regard — last week, for example, Amazon’s Simple Storage Service (S3) was down for a few hours in the Northern Virginia region, impacting a wide range of popular websites and services.