Avoiding Nested Include Files
Avoiding Nested Include Files records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal writing rule.
Do not embed Microsoft Learn include files inside other include files; keep include content self-contained and use includes as supplemental content rather than an article’s only content.
Key details
Important caveats
Scope Boundary
This page isolates the no-nested-includes requirement. The separate block-include guide covers when larger reusable sections should use block includes.
Further guidance
Content
Do not embed Microsoft Learn include files inside other include files; keep include content self-contained and use includes as supplemental content rather than an article’s only content.
Purpose
Keep Microsoft Learn source readable, accessible, reusable, and predictable while following current contributor-platform conventions.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Markdown reference for Microsoft Learn — Contributor guide (opens in a new tab)Microsoft · Current Microsoft Learn contributor reference for Markdown authoring, including headings/navigation, conceptual images and icons, includes, lists/checklists, nonlocalized strings, alerts, comments, tables, and other Learn extensions.