Sitecore Cloud - Status Page Last updated 2 minutes ago

  Mar 16, 2021

Permanent link to this event

Authentication Issue while accessing Azure Active Directory

Event Description: Starting at approximately 19:15 UTC on 15 Mar 2021, a subset of customers may experience issues authenticating into Microsoft services, including the Azure Portal. Microsoft is reporting an active outage for Azure AD. Authentication errors across multiple Microsoft/Azure services.

 

Impact: Customers may experience issues authenticating into Microsoft Services.

 

Additional References: https://status.azure.com/en-us/status

 

 

Planned further action:

We are continuously monitoring the situation and will keep you updated as and when we hear more about it.

Microsoft Engineering teams have been engaged and are investigating. 

 

Updates Summary

Update 09: Issue has been Mitigated by Microsoft
- Posted on Mar 17, 07:19 UTC

Update 08: 

Summary of impact: Between 19:00 UTC (approx) on March 15, 2021, and 09:25 UTC on March 16, 2021 customers may have encountered errors performing authentication operations for any Microsoft and third-party applications that depend on Azure Active Directory (Azure AD) for authentication.

Azure Admin Portal, Teams, Exchange, Azure KeyVault, SharePoint, Storage and other major applications have recovered. Any customers experiencing residual impact will continue to receive updates regarding these via their Azure Service Health notifications.

The Root Cause Analysis investigation relating to this incident is ongoing, and a full RCA will be published when this is completed, or if any other substantive details emerge in the interim.

 

More details: Tracking ID LN01-P8Z


- Posted on Mar 16, 12:36 UTC

Update 07: Microsoft still have a deployment in progress, in line with safe deployment practices, to mitigate residual impact to Azure Storage. As the deployment continues to the impacted regions, some customers may begin to see signs of recovery. 
- Posted on Mar 16, 08:21 UTC

Update 06: We currently have a deployment in progress, in line with safe deployment practices, to mitigate residual impact to Azure Storage. The next update will be provided in 60 minutes or as events warrant.
- Posted on Mar 16, 06:44 UTC

Update 05: 

We have completed rollout of a fix addressing the Azure Active Directory underlying cause, mitigating impact to Azure Active Directory and the Azure Portal. Some customers may continue to see signs of recovery.

At this time, a subset of Azure services may be experiencing residual impact due to downstream impact to Azure Storage service; we are currently preparing deployments, in line with safe deployment practices, to mitigate residual impact to Azure Storage. The next update will be provided in 60 minutes or as events warrant.


- Posted on Mar 16, 04:40 UTC

Update 04: We have completed rollout of a fix addressing the Azure Active Directory underlying cause, mitigating impact to Azure Active Directory and the Azure Portal. Some customers may be seeing preliminary signs of recovery.

At this time, a subset of Azure services may be experiencing residual impact due to downstream impact to Azure Storage and Azure Key Vault services; These services are continuing to pursue recovery actions. The next update will be provided in 60 minutes or as events warrant
- Posted on Mar 16, 02:40 UTC

Update 03: Various downstream Azure services continue their recovery actions following the completed rollout of the fix to the Azure AD underlying cause. At this time, some customers may notice that the ability to log into the Portal has been restored, but that some resource or subscription information may not currently be visible from the Portal UI. We will continue to provide updates as more information is known with the next update to be provided in 60 minutes.
- Posted on Mar 16, 00:53 UTC

Update 02: Engineering teams have rolled out a fix to all affected regions for Azure AD. Internal telemetry and customer reports suggests that the error rate for dependent services is rapidly decreasing. Microsoft services are in the process of recovery. Some services and offerings may have varying times of recovery following the underlying fix. We recommend that customers with custom applications that use Azure AD refresh their metadata cache. The next update will be provided in 60 minutes or as events warrant.
- Posted on Mar 15, 23:07 UTC

Update 01: Microsoft Engineering teams have rolled out a fix to all affected regions. Internal telemetry and customer reports suggests that the error rate for dependent services is rapidly decreasing. The next update will be provided in 60 minutes or as events warrant.
- Posted on Mar 15, 22:40 UTC