Navigating M365 Error Codes
The Error Code Problem
The Microsoft 365 error code ecosystem is a mess. Some codes are AADSTS errors from Azure AD. Some are Exchange Online errors. Some are Intune MDM codes. Some are SharePoint HRESULT values that date back to the Windows NT era. And they all live in different documentation trees, with different formats, different levels of detail, and wildly inconsistent plain-English explanations.
When an admin hits AADSTS700082 at 2am, they don't want to read five Stack Overflow threads. They want to know: what broke, why, and how do I fix it.
Building the Catalogue
The first version of m365error.com was a static site with about 200 manually catalogued error codes I'd personally hit or seen on r/sysadmin. That took about two weekends.
Getting to 10,000+ codes required a different approach. I built scrapers for:
- Microsoft's official error code documentation
- The Azure AD audit log error reference
- Exchange NDR code documentation
- Community sources (Reddit, TechNet forums, Spiceworks)
Each source had a different structure. The Microsoft docs use a mix of HTML tables and freeform prose. The community sources have the actual explanations and workarounds that the official docs don't include.
The real work was normalization: mapping inconsistent field names, deduplicating codes that appeared across multiple sources with different descriptions, and writing the "plain English" summaries where none existed.
What Makes a Good Error Entry
After writing hundreds of these manually, I developed a template:
- What it means — one sentence, no jargon
- Common causes — bulleted list, most common first
- Fix steps — numbered, actionable, specific to the admin center or CLI
- Still stuck? — link to the official doc, a known good forum thread
The "still stuck" section is the one Microsoft keeps forgetting to write.
Lessons
The most-viewed error codes are rarely the most exotic ones. Admins look up AADSTS50034 (user doesn't exist in tenant) and AADSTS50055 (password expired) dozens of times a week. The long tail matters for completeness, but the high-frequency errors are where the real value is.
If you manage M365, bookmark m365error.com. And if you hit a code that's not in the catalogue, submit it — I'll add it.