Microsoft 365 services are experiencing downstream impact related to the ongoing Azure outage. Additional updates can be found on the @AzureSupport outage page: https://t.co/U4YACRcMAn.

We've identified the cause of the issue and subsequently reverted it. We have confirmed with customers and internal testing that the issue is fully resolved. More details can be found at MO1181501 and CP1181486.

APOL1 Genetic Testing at No Cost to Patients! Are you incorporating APOL1 genetic testing into your workflow? Discover No-Cost APOL1 Genotyping Program for eligible patients sponsored by Vertex Pharmaceuticals. Learn more today!

We've initiated a rollback of the service to its last known good build, and we're seeing improvement to service availability. We're still reviewing any relevant data to identify the underlying cause of the issue. More details can be found at MO1181501 and CP1181486.

After extended monitoring, we confirmed that impact stemming from the Azure configuration change has been resolved. Full details can be found on MO1181369 or https://t.co/Htn4qQDPCR.

We're investigating an issue in which https://t.co/JbDYsPALYH and https://t.co/ROdao97J8S are reported to be inaccessible. This issue is not related to MO1181369. Please find more details in the Service Health Dashboard (SHD) under CP1181486.

We've confirmed that service health has largely recovered; however, user reports of impact haven't yet returned to pre-incident thresholds. We're continuing to monitor the service to ensure full recovery. See MO1181369 or https://t.co/Htn4qQDPCR for more info.

Our configuration deployment and traffic rebalancing is showing steady service health improvement for the various affected M365 services. Some users may experience residual impact until availability fully recovers. We're monitoring for an extended period to ensure service health

We're closely monitoring the environment to ensure the reversion has taken effect and that all infrastructure returns to a healthy state. In parallel, we're working to manually rebalance service traffic across the environment to achieve withstanding recovery. Users may continue

We've completed the deployment of a healthy configuration and we're continuing our active traffic balancing efforts as well as monitoring service telemetry to ensure widespread recovery. More info can be found in the admin center under MO1181369 or at https://t.co/Htn4qQEnsp.

We've completed the deployment of the previous healthy configuration and are actively rebalancing traffic across healthy infrastructure to actualize recovery across the affected services. More info can be found in the admin center under MO1181369 or at https://t.co/Htn4qQEnsp.

We're deploying a previous healthy configuration to the affected infrastructure to resolve this issue. This is being done in tandem with efforts to rebalance traffic across healthy infrastructure to mitigate impact quickly. More info can be found at https://t.co/Htn4qQEnsp.

We've halted the rollout of the impacting configuration change. We're continuing to route service traffic away from affected infrastructure to recover service availability. In parallel, we're working to revert the impacted infrastructure to a previous state.

We've identified a recent configuration change to a portion of Azure infrastructure which we believe is causing the impact. We're pursuing multiple remediation strategies, including moving traffic away from the impacted infrastructure and blocking the offending change.

We’ve identified portions of internal infrastructure that are experiencing connectivity issues. We’re unblocking these systems and redistributing traffic to support recovery, as we continue our work to reroute affected traffic to restore service health.

Many users are reporting that https://t.co/Htn4qQEnsp is intermittently unavailable. While we work to address that problem, we’ll provide frequent updates to @MSFT365Status to ensure the affected users remain informed.

We're rerouting affected traffic to alternate healthy infrastructure as a near-term resolution while our investigation into the source of the issue is ongoing.

For users that are unable to access the MO1181369 in the admin center, please visit https://t.co/uSHwRmYdzx to view updates on this event.

We’re investigating reports of issues accessing Microsoft 365 services and the Microsoft 365 admin center. More details can be found in the Service Health Dashboard under MO1181369.

We've resolved the issue, and further details are being provided under TM1180557 in the admin center.

We're investigating an issue with text-to-speech functionality during auto-attendant calls in Microsoft Teams. More information can be found under TM1180557 in the admin center.