The Microsoft Azure outage explained: What happened, who was impacted, and what can we learn from it?

"Microsoft has confirmed its Azure cloud services are back online after a major outage impacted services across multiple regions. It's a tough time to be a cloud provider, with the Azure incident coming hot on the heels of an that knocked a wide range of companies and services offline last week. According to Microsoft, the Azure outage was caused by a CDN configuration error, lasted eight hours, and saw a wide range of Microsoft customers affected, including Alaska Airlines, websites for Heathrow, NatWest, and more."

"Even Microsoft's own 365 suite was affected by the outage while proceedings at the Scottish Parliament in Edinburgh were paused due to technical difficulties. In a service update, Microsoft said error rates and latency are "back to pre-incident levels", but warned that a "smaller number of customers may still be seeing issues" akin to the turbulent recovery period experienced by AWS customers last week."

"Microsoft has detailed its initial take on the outage on the Azure status page, noting that the incident started at 3.45pm UTC and was spotted within 20 minutes, with manual recovery beginning at 6.45pm. The outage was resolved by midnight. The outage affected customers and Microsoft services using Azure Front Door (AFD), which is Microsoft's content delivery network service, causing latency issues, timeouts and errors."

Microsoft confirmed Azure cloud services returned online after an eight-hour outage caused by a CDN configuration error in Azure Front Door (AFD). The outage produced latency, timeouts and errors affecting many customers, including Alaska Airlines, Heathrow, NatWest, and Microsoft 365. Proceedings at the Scottish Parliament were paused due to related technical difficulties. Microsoft reported error rates and latency have returned to pre-incident levels while warning a smaller number of customers may still experience issues. The incident began at 3.45pm UTC, was noticed within 20 minutes, manual recovery started at 6.45pm, and the outage was resolved by midnight.

Read at IT Pro