Over the past two weeks, we've seen a noticeable increase in Microsoft 365 users receiving license validation errors. Examples include Account Validation Error Code 0x0 and generic "Something went wrong" messages with tags such as [7ita9] and [5fcl8].
We migrated to Microsoft 365 late last year and had very few problems until now. Previously, users could access the Office apps both on and off our network without trouble. Has anyone else noticed a recent increase in these errors, particularly among existing users, and is there a known service-side cause or recommended fix?
2 Answers
We saw similar failures last week, so this may be related to a Microsoft-side licensing or authentication problem rather than a local configuration change. I’d check the Microsoft 365 service health dashboard and confirm whether the issue is still active before making widespread changes.
Our pattern has been different: new users are mostly fine, while established users are the ones seeing the validation errors. That points more toward cached credentials, expired tokens, or an account licensing refresh problem than an issue with initial provisioning. Reauthenticating the affected account or refreshing the Office sign-in state may help, but I’d still look for a tenant-wide incident first.
That matches what we’re seeing too. The problem seems limited to existing users, which makes a client or token refresh issue more likely than a problem assigning licenses to new accounts.
It may be a combination of both: the service could have had an incident, while some clients still have stale authentication or licensing tokens afterward.