Microsoft Cloud service back after outage: What caused the glitch that also hit Starbucks app

Microsoft said that it has started to resolve an outage affecting its Azure cloud service. The issue, according to the company, resulted from an unexpected usage surge. The outage is also said to have disabled mobile ordering at Starbucks for hours on Tuesday (July 30). Reports of outages on Azure and Microsoft 365 began to spike shortly after 7 a.m.Tuesday New York time (4.30 pm IST) and comprised hundreds of complaints at the incident’s peak, according to user reports compiled by Downdetector. The issue affected multiple Microsoft 365 services and features, Microsoft said in a post on social network X, formerly Twitter. Microsoft 365 includes common productivity apps like Outlook, Word and Excel.
The Starbucks' app disruption is also reportedly connected to the issues affecting Microsoft Azure. Mobile ordering for Starbucks has largely been restored, according to a statement issued about 1 p.m. New York time. The company is working to address limited interruptions that continue, a spokesperson said.
Microsoft said it will continue monitoring the situation until the outage has been resolved and will provide more updates throughout the afternoon.

Starting approximately at 11:45 UTC on 30 July 2024, a subset of customers may have experienced issues connecting to Microsoft services globally. Current Status: An unexpected usage spike resulted in Azure Front Door (AFD) and Azure Content Delivery Network (CDN) components performing below acceptable thresholds, leading to intermittent errors, timeout, and latency spikes. We have implemented network configuration changes and have performed failovers to provide alternate network paths for relief. Our monitoring telemetry shows improvement in service availability from approximately 14:10 UTC onwards.We continue to investigate and mitigate reports of specific services and regions that are still experiencing intermittent errors. While our previous network configuration changes successfully mitigated the impacts of the usage spike, these changes caused side effects for a small number of services. Our updated mitigation approach has successfully reduced these impacts across regions in Asia Pacific and Europe. Our phased approach is now applying this same mitigation targeting regions in the Americas, and we expect that services should be fully mitigated by 20:30 UTC.We will provide an update on our continued mitigation efforts by 20:00 UTC, or sooner if we have progress to share.