Formatting URLs in Technical Documentation records the relevant Microsoft Style Guide convention while keeping it explicitly house-style scoped rather than presenting it as a universal grammar rule.
ReviewedEvidence1 sourceSectionWriting & Style
Quick answer
For a complete URL in Microsoft-style documentation, normally use lowercase, avoid hyphenating it, and if a line break is necessary, break before a slash.
Key details
Core IssueMicrosoft style says complete URLs are normally lowercase and should not be hyphenated; long URLs may break before a slash when necessary.
RegisterMicrosoft technical and professional documentation
Important caveats
Scope Boundary
These are Microsoft presentation conventions; preserve case when a real path or resource is case-sensitive or must be reproduced exactly.
Further guidance
Content
For a complete URL in Microsoft-style documentation, normally use lowercase, avoid hyphenating it, and if a line break is necessary, break before a slash.
Purpose
Keep web addresses recognizable and prevent line-break punctuation from being mistaken for part of the address.
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.
Formatting Nonclickable URLs in Technical Documentation records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.
Formatting AI Prompts in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Attributes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Classes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Keywords in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Samples in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it scoped to technical instructions rather than presenting it as a universal grammar rule.
Formatting Constants in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Control Classes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
