Anyone else seeing Microsoft sign-in problems slow things down?

If the failures are widespread and clear up without a tenant-side change, check Microsoft’s service health page before making broad configuration changes. A provider-side issue can look like a local sign-in problem, and an incident notice may help explain why several services are affected at once.

Look at the sign-in logs and note whether failures cluster around a particular flow, such as non-interactive token renewal, or show a common server error. That can separate a general authentication outage from a problem limited to one app, browser, or policy. I wouldn’t rely on an incident number from an unverified discussion; check the official health page directly.

For users stuck in a browser sign-in loop, trying a private window or clearing that app’s cached sign-in state can be a reasonable, targeted test. It may help with stale local state, but it won’t fix a service-side failure, so avoid making it the explanation for every affected user.

Check device time too, especially for people using time-based MFA. A noticeable clock mismatch can interfere with authentication. Confirm automatic time and time zone are correct, then retry. It’s a quick, low-risk check, though it only fits cases where the trouble is limited to particular devices.

Ask whether the prompt itself changed, for example whether users are being asked for a passkey instead of their usual MFA method. That detail, along with the affected app and exact failure time, is useful when comparing reports and reviewing logs. Don’t have users weaken MFA or repeatedly reset credentials just to get past an unexplained issue.