![]() ![]() The design of the Office 365 infrastructure divides work across regions, data centers, and servers.There’s a multitude of reasons why not everyone is affected in the same way by a Microsoft 365 outage, including: Many Reasons Why People Don’t Know About Outages You can also read much of its content on the Azure status history page. The PIR is available to affected customers as a downloadable Word document through the Service Health Dashboard in the Microsoft 365 admin center. However, not every user within affected tenants experienced this length of the outage. The formal length of the incident is five hours and 38 minutes, which is a long time waiting for engineers to resolve a problem. ![]() Even so, sometimes, the human element creates a problem, just like it can within an on-premises data center.Īccording to Microsoft’s post-incident report (PIR), incident MO502273 began at 7:05 AM UTC and finished at 12:43 PM UTC on Wednesday, 25 January. Microsoft 365 is a highly automated operation. And like faults that afflict on-premises infrastructures, the causes of outages come from many sources. Let me explain a big fact about cloud services: outages happen all the time. This could be true in some cases, but it’s not for most, even when an outage happens. Lots of hot air and annoyed words found their way across the internet to confirm everyone’s suspicions that on-premises deployments are infinitely superior to any cloud service. Those whom I offended by writing about the desirability of moving soon-to-be-unsupported Exchange 2013 on-premises servers to the cloud must have enjoyed the January 25 outage suffered by many Microsoft 365 services, including Exchange Online. Brown Smelly Stuff Happens On-Premises Too.Many Reasons Why People Don’t Know About Outages. ![]()
0 Comments
Leave a Reply. |