Microsoft confirms outage affecting MFA, My Sign-Ins platform

MICROSOFT CONFIRMS OUTAGE AFFECTING MFA, MY SIGN-INS PLATFORM

OverviewAn ongoing incident is affecting a portion of Microsoft customers who rely on multi-factor authentication (MFA) and the My Sign-Ins management portal. Users attempting to set up MFA or access the My Sign-Ins site have reported difficulties, with many encountering 504 Gateway Timeout errors. Microsoft confirmed the issue and stated that they are actively working to restore normal service by shifting traffic to alternate infrastructure and by monitoring system telemetry to verify full recovery.

What Happened

• The incident centers on the My Sign-Ins portal and the MFA setup workflow. Microsoft indicated that some users may be unable to complete MFA enrollment or reach the mysignins.microsoft.com endpoint.
• The service status message described the problem as a 504 Gateway Timeout when attempting to load the My Sign-Ins site. This type of error points to a backend response delay or failure within the service path used to authenticate and configure MFA.
• The company disclosed that it has switched to alternative, healthy infrastructure as part of the mitigation process and is actively observing telemetry to confirm stabilization and recovery.

Impact and Scope

• The outage directly impacts scenarios where users need to enroll in MFA or sign in to My Sign-Ins for credential management.
• Regions affected have not been publicly enumerated by Microsoft at this time. The incident was flagged as ongoing, with initial acknowledgement occurring around early morning hours.
• The outage follows recent past activity in Microsoft’s ecosystem where other authentication and access-related issues have occurred across products, underscoring the sensitivity of identity and access services to outages.

Company Response and Mitigation

• Immediate action involved failing over to healthy, alternate infrastructure to route around the fault point and reduce user impact.
• Microsoft stated that mitigation actions have been completed, and the team is continuing to monitor overall service health and performance.
• As the incident evolves, the company is evaluating additional mitigation options. This includes potential optimizations to how service requests are processed to further stabilize the MFA enrollment and My Sign-Ins access pathways.
• Monitoring and telemetry play a central role in the response, with ongoing analysis intended to ensure a robust recovery and prevent reoccurrence.

Timeline and Milestones (as described in public notices)

• Around 5:00 AM Eastern Time: Microsoft acknowledged the issue publicly and began active remediation efforts.
• Following the acknowledgement: Traffic was redirected to alternate infrastructure to mitigate impact and begin stabilizing the service.
• Ongoing: Microsoft continues to monitor service health and evaluates additional mitigation strategies as elevated error rates persist.

Context and Related Issues

• The disruption to MFA enrollment and My Sign-Ins access sits in a broader pattern where identity and authentication services can experience outages that ripple through enterprise workflows.
• Earlier in the year, Microsoft resolved a separate issue related to Teams Free functionality, and there have been other outages affecting Outlook.com sign-in and mailbox access. While those incidents involved different surfaces, they illustrate the interconnected nature of Microsoft’s identity, collaboration, and mail services.
• The current outage highlights that even widely deployed authentication features can encounter regional or systemic faults, emphasizing the importance of resilience planning and rapid recovery processes for identity-related infrastructure.

What This Means for Users

• Users trying to enroll in MFA may see delays or errors preventing successful setup until the service stabilizes.
• Access to the My Sign-Ins portal may be intermittently unavailable, affecting the ability to review or manage authentication rules and device registrations.
• For organizations, this underscores the need to monitor identity service health dashboards, communicate changes to end users, and prepare contingency plans in case of authentication interruptions.

Ongoing Situation and Next Steps

• Microsoft continues to investigate the root cause, with a focus on stabilizing the affected pathways and ensuring accurate service telemetry.
• The company has not provided a fixed restoration timestamp, reflecting the evolving nature of complex backend outages.
• Expect further updates as service health metrics shift and mitigation options are validated. Until a full recovery is confirmed, users and administrators should anticipate potential intermittent behavior and plan accordingly.

Closing NoteThe outage affecting MFA setup and the My Sign-Ins platform is a developing situation. As Microsoft implements additional mitigations and validates service stability, more detailed information about regional impact and a definitive restoration timeline may emerge.