Microsoft resolves a service disruption that affected Office 365, Outlook.com, Teams and other cloud-based services
Microsoft has fixed problems affecting its online authentication systems that left a portion of its userbase locked out of multiple cloud-based services unless they were logged in already.
The issues, which occurred on Monday evening, have since been resolved and the services seem to be up and running normally again. Most customers saw their access restored and systems fully recovered after Microsoft’s engineers were able to successfully roll back their systems on early Tuesday morning.
According to the Azure status history page, the downtime started approximately at 21:25 UTC on Monday and affected users who were trying to login into its various services including Microsoft 365, Azure, Dynamics 365, as well as into other custom applications that use Azure Active Directory (AAD) authentication.
⚠️ We are investigating an issue impacting Azure AD Authentication. More information and updates can be found on the Azure Status page at https://t.co/Dw19fIGsXf
— Azure Support (@AzureSupport) September 28, 2020
“Users who were not already authenticated to the cloud services using Azure AD would have seen multiple authentication request failures. Impact was primarily in the Americas based on the issue being exacerbated by load, but users in other regions may also have experienced some impact. Users that had previously authenticated prior to the issue may not have experienced any noticeable effect,” said Microsoft.
In another tweet, the Azure Support account confirmed that both the Azure Public and Azure Government clouds were affected by the issue impacting AAD authentication.
Engineers have confirmed that an issue that impacted Azure AD Authentication in the Azure Public and Azure Government clouds is now mitigated. A detailed resolution statement has been posted to the Azure Status History page at https://t.co/yK1I9ll9jj.
— Azure Support (@AzureSupport) September 29, 2020
While the results of Microsoft’s in-depth investigation are still a few days away, the company has identified the likely culprits behind the whole situation. The root cause seems to be a combination of three separate and unrelated issues, including a code defect in a service update, a tooling error in the Azure AD safe deployment system, and a code defect in Azure AD’s rollback mechanism.