Microsoft 365 users recently experienced frustrating errors impacting sign-in features, particularly those related to setting up and managing extra security layers like multi-factor authentication (MFA). While not a security breach, this technical glitch prevented many from accessing services correctly or managing their account security settings. The incident, which Microsoft has now mitigated, was traced back to infrastructure handling authentication requests.
Contents
Here’s a quick rundown:
- What happened: Users couldn’t reset passwords, view/register authentication methods (like phone numbers or authenticator apps), and admins struggled to add MFA for some users.
- Who was affected: Users and administrators primarily in Europe, the Middle East, Africa, and Asia Pacific.
- The cause: Microsoft identified issues with the database infrastructure processing authentication requests, possibly linked to a recent update aimed at improving MFA.
- The fix: Microsoft implemented configuration changes, which eventually mitigated the problem.
What Was Going On?
Starting for some users as early as April 18th, but officially acknowledged later by Microsoft, people trying to sign in or manage their Microsoft 365 accounts ran into errors. The most common issues involved multi-factor authentication (MFA) – that extra security step after your password, often involving a code from your phone.
Users trying to register new ways to verify their identity would see messages like, “Your organisation requires that you register additional authentication methods, but no supported methods are currently enabled for your account.” This essentially told them they needed to set up more security, but then offered no way to actually do it. Administrators trying to help users by adding these methods for them also faced difficulties. Password resets were sometimes problematic too.
Microsoft 365 logo and branding
Why Did It Happen?
Microsoft’s investigation pointed to underlying infrastructure. They stated that some of the systems responsible for processing authentication requests weren’t performing as expected. They initially believed this might be connected to a recent change intended to improve MFA sign-in functionality, a common scenario where updates can sometimes introduce unexpected side effects.
Essentially, the digital machinery handling the “Is this really you?” checks for millions of users wasn’t keeping up, leading to the errors.
Where Was the Impact Felt?
The problems weren’t universal but seemed concentrated. Microsoft reported the issues primarily affected customers located in or served by infrastructure within the Europe, Middle East, Africa (EMEA), and Asia Pacific (APAC) regions.
Reports from specific organizations, like those using the NHSmail service for healthcare in England, confirmed users were seeing “we’re sorry, we ran into a problem” or “no methods available” when trying to set up their secure sign-in.
How Did Microsoft Respond?
Upon identifying the scope of the problem based on customer reports and internal monitoring, Microsoft initiated an investigation. They quickly identified the underperforming infrastructure as the root cause.
As a temporary measure, Microsoft began applying configuration changes to the affected systems. They monitored their internal data (telemetry) to see if these changes were helping, and initially reported seeing signs of improvement. Later, they confirmed that these efforts successfully mitigated the incident, meaning the authentication features should be working correctly again for affected users.
Not the First Time
While frustrating, technical glitches affecting large cloud services like Microsoft 365 aren’t entirely uncommon. Microsoft itself dealt with a similar MFA incident in January that blocked access to apps. That time, the issue was also linked to an unexpected surge in system resource usage overloading the authentication registration infrastructure.
Other recent incidents have affected different parts of Microsoft 365, including a May outage impacting services like Teams across North America, and an April licensing issue that locked some users out of their Family subscriptions. These events highlight the complexity of maintaining massive online services and the occasional challenges that arise.
What This Means for Users
For most users who were affected, the primary impact was frustration and potential delays in setting up new accounts or managing their existing security methods. Admins faced extra work in troubleshooting and assisting users. The mitigation means these core functions should now be restored, allowing everyone to manage their authentication methods and reset passwords securely.
While this incident is resolved, it serves as a reminder of how interconnected our digital lives are and how even minor technical issues in core services can ripple outwards.
Want to read more about recent tech hiccups? Check out these related articles:
- New Microsoft 365 outage impacts Teams and other services
- Microsoft shares temp fix for Outlook crashes when opening emails
- Google links massive cloud outage to API management issue
