Supported documentation
Reliable X-ray vision begins with transparent, testable mappings to public source repositories.
Reviewed direct mappings
Microsoft Docs X-Ray keeps ordered mappings for common product areas, including the Microsoft Defender docsets and the current Aspire docs at aspire.dev. Narrow routes such as Defender for Cloud, Microsoft Sentinel, Microsoft Graph API versions, and Fabric get-started pages are matched before broader product routes.
MicrosoftDocs organization coverage
For any other Microsoft Learn article whose public Edit source points to a repository in the MicrosoftDocs organization, Docs X-Ray resolves the exact repository, branch, and file path from Learn’s published metadata. This covers active and archived repositories without guessing from a repository name, and newly published MicrosoftDocs sources do not require a site release.
Learn mirrors
Microsoft is making some MicrosoftDocs repositories private. For these, Docs X-Ray reads a public mirror that learn-mirror rebuilds from Microsoft Learn several times a day. Each mirror keeps the original repository’s layout and records one commit per crawl that found a change.
A mirror’s history starts on the day mirroring began, so revisions from before then are not available. Mirrored pages hold the Markdown that Learn publishes, with includes already expanded, and their images load from Microsoft Learn.
| Original repository | Mirror | Used | Since |
|---|---|---|---|
MicrosoftDocs/defender-docs | merill/defender-docs-mirror | Always — the original is no longer public | 2026-09-28 |
MicrosoftDocs/memdocs | merill/intune-docs-mirror | Always — the original was archived on 2026-09-02; earlier revisions come from merill/memdocs | 2026-09-28 |
MicrosoftDocs/entra-docs | merill/entra-docs-mirror | When the original is private or lacks the requested revision | 2026-09-28 |
How URL mapping works
For Microsoft Learn, a leading locale such as en-us or fr-fr is removed for direct repository lookup. The configured site prefix is replaced with a repository path prefix, and the article slug becomes a Markdown or MDX filename.
For example, /en-us/entra/identity/conditional-access/overview maps to docs/identity/conditional-access/overview.md in MicrosoftDocs/entra-docs. The Aspire page aspire.dev/get-started/what-is-aspire/ maps to src/frontend/src/content/docs/get-started/what-is-aspire.mdx in microsoft/aspire.dev.
Microsoft Intune supports both the current /intune/… URLs and legacy /mem/intune/… URLs; both map to the same intune/… source tree, read from merill/intune-docs-mirror since MicrosoftDocs/memdocs was archived.
Query-specific mappings are supported. Microsoft Graph’s ?view=graph-rest-beta selects the beta API source tree, while graph-rest-1.0 selects v1.0. Unmatched MicrosoftDocs pages use the source metadata lookup described above.
Limitations
- Some documentation pages are generated, private, moved, or sourced through nonstandard publishing pipelines.
- A public URL does not always have a one-to-one public Markdown or MDX file.
- Docs X-Ray compares Git revisions, not changes introduced by runtime site rendering or personalization.
- Repository moves can temporarily break a mapping until the configuration is updated.
Unsupported paths fail explicitly and link back to the original documentation page. To request a mapping, open an issue with an example URL.