Microsoft Azure Globally Down – What's Happening!
On July 30, 2024, at roughly 13:13 UTC, Microsoft Azure & Microsoft 365 reported a worldwide outage affecting a subset of its services. The dilemma resulted in timeouts and difficulties connecting to diverse Azure services worldwide.
Extra than one engineering teams at Microsoft had been promptly engaged to diagnose and unravel the dilemma. The firm acknowledged the deliver and offered updates on the Azure station web drawl.
“We have more than one engineering teams engaged in diagnosing and resolving the dilemma. Extra shrimp print will be offered as soon as possible.”

In the starting build, the dilemma used to be reported in Europe, nevertheless it surely soon became apparent that the outage had a worldwide influence, affecting customers worldwide.
Curiously Microsoft Azure is experiencing frequent considerations across a colossal selection of regions. The affected services embody both Non-Regional and Regional services across the following areas:
- United States: East US, East US 2, Central US, North Central US, South Central US, West Central US, West US, West US 2, West US 3
- Canada: Canada East, Canada Central
- Brazil: Brazil South, Brazil Southeast
- Mexico: Mexico Central
- Europe: North Europe, West Europe, France Central, France South, UK West, UK South, Switzerland North, Switzerland West, Norway East, Norway West, Germany North, Germany West Central, Sweden Central, Sweden South, Poland Central, Italy North, Spain Central
- Asia: Southeast Asia, East Asia, Central India, West India, South India, Japan East, Japan West, Korea Central, Korea South
- Australia: Australia East, Australia Southeast, Australia Central, Australia Central 2
- Heart East: South Africa West, South Africa North, UAE Central, UAE North, Qatar Central, Israel Central
- India: Jio India West, Jio India Central

The Community Infrastructure in these regions is at this time below a “Warning” station, indicating doable disruptions or considerations.
Microsoft 365 Moreover Down:
Microsoft is investigating obtain staunch of entry to considerations and degraded efficiency affecting several Microsoft 365 services and ideas. The incident, acknowledged as MO842351, is below overview, with detailed files on hand in the admin heart for these impacted.
“Microsoft has offered that they are at this time investigating obtain staunch of entry to considerations and degraded efficiency affecting more than one Microsoft 365 services and ideas. The dilemma, acknowledged as incident MO842351, is detailed extra in the admin heart for affected customers.”
In step with the Microsoft station, These lists will substitute as we confirm that assorted services are unaffected.
Impacted services embody, nevertheless aren’t restricted to:
- – Microsoft 365 admin heart
- – Intune
- – Entra
- – Energy Platform
Initial indications are that the following services aren’t impacted:
- – SharePoint Online
- – OneDrive for Industry
- – Microsoft Teams
- – Alternate Online
Present Space
As of the final substitute at 13:13 UTC on July 30, 2024, the investigation used to be ongoing, and Microsoft promised to provide more shrimp print as soon as possible.
Microsoft has mitigated and rerouted user requests to address a fresh provider dilemma. The firm is actively monitoring the scenario to have sure it is resolved. For basically the most in trend updates, customers can search the advice of with the Microsoft station web drawl at https://station.cloud.microsoft or consult with the incident code MO842351 in the admin heart.
Now, “We’ve applied mitigations and rerouted user requests to provide reduction. We’re monitoring the provider to substantiate resolution and extra files is also chanced on at https://station.cloud.microsoft or below MO842351 in the admin heart.”
“We have implemented networking configuration changes and have performed failovers to alternate networking paths to provide reduction. Monitoring telemetry exhibits enchancment in provider availability, and we’re persevering with to display screen to have sure plump restoration.”
“Monitoring telemetry exhibits enchancment in provider availability, and we’re persevering with to display screen to have sure plump restoration.”
16:42 UTC: Root Trigger: Azure Entrance Door Carrier Experiences Efficiency Disorders Because of Usage Spike
An surprising surge in usage has resulted in efficiency degradation in Azure Entrance Door (AFD) parts, causing intermittent errors, timeouts, and latency spikes. In response, the Azure crew implemented network configuration changes and performed failovers to more than a few network paths to mitigate the influence.
Monitoring telemetry has indicated an enchancment in provider availability starting from roughly 14:10 UTC. Alternatively, some bellow services and regions continue to record intermittent errors. The Azure crew is actively investigating these considerations and will must provide an substitute on the ongoing mitigation efforts by 18:00 UTC, or sooner if vital growth is made.
“An surprising usage spike resulted in Azure Entrance Door (AFD) parts performing below acceptable thresholds, main to intermittent errors, timeout, and latency spikes.”
“We have implemented network configuration changes and have performed failovers to provide alternate network paths for reduction. Our monitoring telemetry exhibits enchancment in provider availability from roughly 14:10 UTC onwards, nevertheless we’re investigating reviews of bellow services and regions which might well per chance be smooth experiencing intermittent errors.”
“We are able to provide an substitute on our persevered mitigation efforts by 18:00 UTC, or sooner if we now have growth to portion.” Microsoft’s sleek station substitute”
17:59 UTC: Community Configuration Adjustments Mitigate Usage Spike, Minimize Facet Effects
Microsoft has updated that its fresh network configuration changes have successfully mitigated the impacts of a usage spike that precipitated intermittent errors in sure services. Alternatively, the firm admitted that these changes have resulted in some aspect effects affecting bellow services and regions.
Azure crew is actively updating its mitigation methodology to decrease these aspect effects and is applying Safe Deployment Practices to have sure a serene rollout. The updated mitigation methodology will be deployed in phases, starting with the Asia Pacific regions and lengthening to other areas.
“As we overview reviews of bellow services and regions which might well per chance be smooth experiencing intermittent errors, we beget that our network configuration changes have successfully mitigated the impacts of the usage spike, nevertheless that these changes are causing some aspect effects to sure services. We are updating our mitigation methodology to decrease these aspect effects, and applying these following Safe Deployment Practices – starting build in Asia Pacific regions and then increasing in phases.”
In case you is possible to be experiencing considerations connecting to Azure services, we recommend:
- Monitoring the Azure station web drawl: Preserve an glimpse on the reliable Azure station web drawl for basically the most in trend updates on the outage.
- Checking for updates: Generally overview the Microsoft Azure web drawl and social media channels for any updates on the dilemma.
- Contacting Microsoft Help: In case you is possible to be experiencing continual considerations, take into consideration contacting Microsoft Help for assistance.
The Microsoft Azure worldwide outage has disrupted diverse services, affecting customers worldwide. Microsoft is actively investigating the dilemma and working to unravel it as soon as possible. We are able to provide updates as more files becomes on hand.
This myth is below active development. Please stop tuned for updates.
Change 31 July 2024: Microsoft said the initial trigger for the outage used to be the DDoS Attack. Learn more in regards to the incident here.
Source credit : cybersecuritynews.com