Is anyone else seeing Microsoft 365 authentication problems in North America, especially in the Northeast US? This morning we saw a noticeable increase in users unable to authenticate to Microsoft 365 applications, particularly when using shared-device access. The main symptom appears to be that access or licensing tokens cannot be generated or refreshed. Service monitoring sites are also showing a possible outage, so I'm trying to determine whether this is a broader Microsoft service issue or something specific to our environment.
4 Answers
The impact seems especially noticeable for users whose existing tokens have expired and need to be refreshed. Tokens that are already valid may continue working for a while, but shared Office deployments and remote farms can still break when reactivation is required.
We’re seeing the same issue across North American users. It initially looked like a federation problem, but the symptoms point more toward Microsoft 365 token or license activation failing after authentication.
There are also reports of slowness or temporary unavailability in some Microsoft security and administration portals, including in Europe. Those portals may recover intermittently, but the primary issue for us remains Microsoft 365 application authentication and licensing activation.
The service health dashboard is reporting an incident that matches this behavior. We’re seeing authentication succeed, but the licensing or access token activation does not complete, primarily on non-persistent VDI and shared-computer deployments.
That lines up with what we’re seeing. The shared-device scenarios are being affected much more than regular users.
Exactly. Some environments had been running for years, but users started failing once their token renewal was needed. It would be helpful if the applications had a better outage grace period.