Microsoft 365 Consumer

We've completed our code fix and begun deploying our fixed build version throughout the affected environment, which we're anticipating should be fully released by our next scheduled update. Impacted users will need to restart Microsoft Edge and then Microsoft Teams in order to see remediation following the deployment of the fix.

We've completed our code fix and begun deploying our fixed build version throughout the affected environment, which we're anticipating should be fully released by our next scheduled update. Impacted users will need to restart Microsoft Edge and then Microsoft Teams in order to see remediation following the deployment of the fix.

Our investigation so far indicates impact is associated with a possible third-party networking issue. We're recursively investigating the health of the Microsoft-managed service environment to identify whether any mitigation actions are required and ensure our services are healthy.

We’re analyzing available telemetry and user reports to determine cause of impact and develop a mitigation strategy.

We're continuing to investigate the failures, so that we can identify the root cause and determine the next steps to remediate the impact.

We're reviewing service telemetry data to gain insight into the underlying source of impact and determine our next steps.

A recent configuration change to update the sign in flow is resulting in some password-based sign in requests being blocked. We’re reverting the affected configuration to a previous healthy version and monitoring the service as the change propagates across affected environments to ensure successful restoration.