I'm experiencing some licensing issues with Office 365 on two new devices. They're both showing the error code 772, which I couldn't find much information about. We're using Microsoft 365 Apps for Enterprise. Interestingly, when I check the licensing status on productive clients, I don't see any issues in the app, but running the following commands reveals some problems:
cd "C:Program FilesMicrosoft OfficeOffice16"
cscript ospp.vbs /dstatus
The output indicates that the license status is showing an error code (0xC004F009) along with a description noting the grace period has expired. The installation XML seems properly configured with user-based license activated. The users have active licenses assigned in the M365 Admin Portal. Could this be a configuration issue on my end, or might it be related to the recent outage? Any insights would be hugely appreciated!
2 Answers
I did reboot and also ran the Office Repair on those new devices, but that didn't help. I’ve been tweaking the configuration all morning trying to find the root cause with no luck. Looking at the XML with the Office Deployment Tool seemed fine when I checked for a user-based license. A colleague of mine with a similar setup has reported the same error and is also in a grace period, so I'm starting to think this might stem from Microsoft's side after their recent outage.
Have you tried a standard reboot or a full reinstall from portal.office.com? Sometimes, a simple fix like restarting can surprisingly resolve these kinds of issues. Also, if you're managing these devices through a remote monitoring and management tool, you might want to consider pushing a fresh install from there as well.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures