Micro .ft Azure Status Page on October 7 at about 3:30 p.m. ET
Last week, users around the world were hit by a major Azure Active Directory authentication issue. The following week’s follow-up exchange / outlook issue affected European and Indian Office Fees 365 / micro .ft 365 customers. This week, the issues of Microsoft .ft’s cloud service continue to affect many Exchange, Outlook, Teams and SharePoint users.
Microsoft .ft was still warning some OfficeFish365 / microsoft.ft365 customers as the Admin Center initiated some potential residual exchange / outlook issues, including accessing problems and syncing problems between Outlook Mobile and Desktop. I asked Microsoft if these issues were related to last week’s Azure Active Directory authentication issues, but the company said it had no comment. (I’m hearing that the issues were probably not inter-related, for its value.)
October On October, mainly U.S. In, users started reporting to ET in the afternoon and were having trouble accessing issues to their admin center dashboards. Around 2:30 p.m., users went to Twitter and other social channels to report being unable to access Microsoft 365 services, including Teams, Exchange, Naline, Outlook.com, SharePoint and OneDrive for Naline and Business. At the same time, warnings of issues with Azure Active Directory and Azure Networking Services pop up on the Azure Status page.
Around 4:00 p.m., some OfficeFish 365 / micro .ft365 customers began reporting their services being recovered. (For my part, I still can’t access my M365 admin center, even until 5:00 p.m.)
The Azure team also posted an initial root cause analysis at the same time on issues that users have experienced using the Microsoft .ft or Azure services. In that report, Microsoft said that between 2 p.m. and 3:40 p.m., and in the subset of those customers, there were issues related to the resources that could benefit the Azure network infrastructure in the regions. (According to company officials, “resources with local dependence in the same area should not be affected.”
Microsoft has identified that “recent changes (to those) applied to WAN (wide field-networking) resources as a result of connection delays or failure between fields.” To reduce, the Azure team reversed a recent change in healthy configuration.
On October 7, the Azure team also noted that some subsets of customers experienced traffic heading to “unwanted backends” along the Azure front door. Microsoft blamed the issue on a “configuration change” (s) caused by “incorrect routing traffic” and reversed the change to fix the issue.
The Micro .ft 5 365 team was held accountable for its part Inability to access services on “Network Infrastructure Change” Which has affected multiple micro .ft365 services, including Teams, Outlook, SharePoint, OneDrive for Business and Outlook.com. The same team also said it added extra capacity this afternoon to handle “observed spikes in admin center traffic due to actions to reduce previous incidents with equal effect.”
After last week’s Azure AD issue – due to a defective test of a modification, with rollback failure – this week is not a good look for outage micros .ft cloud.
