Microsoft fixes outage affecting MFA setup, MySignIn service
Microsoft fixed an outage that blocked some users from setting up MFA or reaching My Sign-Ins, with affected users seeing 504 errors.
Intelligence analysis by GPT-5.4 Mini
Microsoft briefly disrupted access to its My Sign-Ins page and MFA setup flow, then shifted traffic to healthier infrastructure and later restored service. The company said the incident was tied to a cache configuration change and load spikes during failover.
Microsoft had a problem with one of its sign-in tools. Some people could not set up extra login protection, and some could not open the My Sign-Ins page at all.
It was a bit like a store door that would not open because the automatic lock was jammed. The company moved traffic to different machines to keep the service working again.
Later, Microsoft said a cache change caused the trouble and that a busy rush of traffic made the service stumble. After fixing it, the sign-in page started working again.
Analysis
What happened
Microsoft said it was investigating an issue that stopped some users from setting up multi-factor authentication or accessing mysignins.microsoft.com. In the admin center, the incident was tracked as MO1329260, and affected users saw 504 Gateway Timeout errors when trying to load the service.
The company treated it as an ongoing incident and described it as a critical service issue with visible user impact. It also said it had not yet shared which regions were affected when the outage was first acknowledged around 5 AM ET on June 1, 2026.
Mitigation and recovery
Microsoft later said it had failed over to alternate infrastructure and was monitoring telemetry to confirm recovery. In a June 1, 08:41 EDT update, the company said access to My Sign-Ins had been restored.
The company attributed the incident to a recent cache configuration change. According to Microsoft, that change required a failover, and during the failover the service saw high CPU and memory usage as EU traffic peaked. Microsoft said that prevented MySignIn from processing the volume of requests.
Microsoft also said mitigation actions were rolled back and traffic was restored to the original infrastructure. The incident sits alongside other recent Microsoft service issues mentioned in the article, including problems affecting Teams Free and Outlook.com, showing that identity and productivity services can be sensitive to backend changes and traffic spikes.
Key points
- Microsoft said some users could not set up MFA or access the My Sign-Ins website.
- Affected users encountered 504 Gateway Timeout errors.
- The company failed over to alternate infrastructure and monitored service telemetry.
- Microsoft later said access was restored and tied the incident to a cache configuration change.
- The company said high CPU and memory use during failover, combined with EU traffic peaks, prevented request processing.
Microsoft says access to My Sign-Ins was restored and mitigation steps were rolled back. If that holds, users should be able to complete MFA setup and account-management tasks normally again.
The outage shows that identity services can fail when backend changes interact badly with traffic spikes. If similar configuration changes recur, users could again be blocked from setting up MFA or reaching sign-in management tools.
