Formatting Nonlocalized Resource Names
Formatting Nonlocalized Resource Names records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.
Use code style for resource names that should not be localized, such as a virtual-machine name, in Microsoft Learn content.
Key details
Important caveats
Scope Boundary
Code style signals that the resource name should remain untranslated; other localization mechanisms may be appropriate when code styling would harm readability.
Further guidance
Content
Use code style for resource names that should not be localized, such as a virtual-machine name, in Microsoft Learn content.
Purpose
Keep programmatic or structural text visually consistent and easier for readers to interpret in Microsoft Learn documentation.
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.
- Text formatting guidelines — Microsoft Learn Contributor Guide (opens in a new tab)Microsoft · Current Microsoft Learn contributor guidance for Git repository/branch names, code style, package and database names, nonlocalized resource names, fenced code blocks, language tags, headings, and link text.