Microsoft resolves MFA setup and MySignIn outage
▼ Summary
– Microsoft is investigating an issue preventing users from setting up MFA or accessing the My Sign-Ins website, with users seeing 504 Gateway Timeout errors.
– Microsoft mitigated the issue by failing over to alternative infrastructure and is monitoring service telemetry for full recovery.
– The company classified the incident as ongoing around 5 AM ET, noting elevated error rates persist and additional mitigation options are being evaluated.
– Microsoft later restored access to the My Sign-Ins service, attributing the outage to a recent cache configuration change that required a failover.
– During the failover, high CPU and memory utilization from EU traffic prevented the service from processing requests, and mitigation actions have been rolled back.
Microsoft has resolved a service disruption that left users unable to set up multi-factor authentication (MFA) or access the My Sign-Ins portal, following a day of troubleshooting.
The issue first surfaced when the company’s Microsoft 365 Status account on Twitter reported that some customers were encountering problems setting up MFA or reaching the mysignins.microsoft.com website. According to details shared in the admin center under incident ID MO1329260, affected users were met with 504 Gateway Timeout errors when attempting to access the service.
“We’re investigating an issue where some users may be unable to setup MFA or access the http://mysignins.microsoft.com website,” the status update read. The admin center further clarified that attempts to reach mysignins.microsoft.com were failing, with users seeing the gateway timeout error.
In response, Microsoft switched to alternative healthy infrastructure to reduce the impact and began monitoring service telemetry to confirm full restoration. “We’ve completed mitigation actions, including failing over to alternate infrastructure, and are continuing to monitor service health,” the company stated in the admin center. “As elevated error rates persist, we’re actively evaluating additional mitigation options, including optimizing how service requests are processed to further stabilize the service.”
The outage was first flagged around 5 AM ET and classified as an ongoing incident, a designation typically used for critical service issues with noticeable user impact. Microsoft has not yet specified which regions were affected.
This incident follows other recent service interruptions from Microsoft, including a known issue that prevented some Microsoft Teams Free users from chatting and calling, as well as an Outlook.com outage that blocked customers from accessing their mailboxes due to intermittent sign-in problems.
In a later update on June 1 at 08:41 EDT, Microsoft confirmed that access to the My Sign-Ins service had been restored. The company attributed the disruption to a recent cache configuration change that required a failover. “During the failover, the service experienced high CPU and memory utilization as EU traffic peaked, which prevented the MySignIn service from processing the volume of requests,” Microsoft explained. “Mitigation actions have since been rolled back, and traffic has been restored to the original infrastructure.”
(Source: BleepingComputer)
