Microsoft confirms auth issues affecting Microsoft 365 users
Microsoft is investigating an ongoing incident that is causing users to experience errors with some Microsoft 365 authentication features.
As the company revealed earlier today in an incident alert published in the admin center, users may experience errors during self-service password resets and when viewing or registering authentication methods in MySignIns, while admins may be unable to add multi-factor authentication (MFA) sign-in methods to some users.
Microsoft acknowledged the issues following a wave of customer reports starting on at least April 18th regarding MFA errors when trying to sign up for Microsoft 365 services.
“Your organisation requires that you register additional authentication methods, but no supported methods are currently enabled for your account,” the error reads.
“Ask your admin to enable more authentication methods for you to select, or tell them to register one or more methods for you.”
Redmond says this incident is caused by a recent change aiming to improve MFA sign-in functionality. Since acknowledging it less than two hours ago, Microsoft engineers have validated a configuration update designed to mitigate the issues temporarily while working on a long-term solution.
“We’ve identified that some of the infrastructure which processes authentication related requests is not performing within expected thresholds,” the company explained. “We’re making some configuration changes to mitigate impact and telemetry is showing improvement.”
These ongoing Microsoft 365 issues currently impact customers located on or served through affected infrastructure in Europe, the Middle East, Africa (EMEA), and Asia Pacific (APAC).
According to reports from affected users at NHSmail, the national secure collaboration service for health and social care in England, those impacted see “we’re sorry, we ran into a problem” or “no methods available” errors while setting up MFA on NHS.net accounts.
Microsoft mitigated another MFA incident in January, preventing affected customers from accessing Microsoft 365 Office apps. At the time, Microsoft 365 users impacted by the incident reported that MFA registration and reset were not working.
After resolving the incident, the company explained that the outage was due to an unexpected sudden increase in CPU resource usage, which rendered the infrastructure responsible for registering authentication methods for Multi-Factor Authentication (MFA) operations unresponsive.
In May, Microsoft also fixed a Microsoft 365 outage affecting multiple services across North America, including the company’s Teams collaboration platform, while one month earlier, it resolved a licensing issue that blocked access to Microsoft 365 services for some customers with Family subscriptions.
Update June 13, 10:31 EDT: Microsoft says the incident has been mitigated and that it was caused by database infrastructure that processes authentication-related requests not performing within expected thresholds.
Patching used to mean complex scripts, long hours, and endless fire drills. Not anymore.
In this new guide, Tines breaks down how modern IT orgs are leveling up with automation. Patch faster, reduce overhead, and focus on strategic work — no complex scripts required.
Source link
