Microsoft Writing Style Guide: Overview and Philosophy
Microsoft Writing Style Guide: Overview and Philosophy
Discover how Microsoft’s approach to content creates warm, crisp, and accessible documentation that empowers customers to achieve more
Table of Contents
Introduction
The Microsoft Writing Style Guide represents one of the most comprehensive and opinionated style guides in the technology industry.
Unlike academic style guides (Chicago, APA) or journalism guides (AP), Microsoft’s guide is purpose-built for technology content—user interfaces, documentation</documentation, marketing, and developer resources.
This article series provides:
- In-depth analysis of Microsoft’s writing principles and strategies
- Comparative context against Google, Apple, Wikipedia, and Diátaxis
- Actionable guidance consolidated for writing prompts and AI agents
- Practical application to your documentation workflows
Why study Microsoft’s guide? Beyond its use for Microsoft content, the guide embodies modern best practices for technology writing that apply broadly: accessibility-first design, global-ready content, and conversational clarity.
Prerequisites: Familiarity with Foundations of Technical Documentation provides helpful context but is not required.
What Is the Microsoft Writing Style Guide?
The Microsoft Writing Style Guide is a comprehensive reference for anyone writing content at or for Microsoft—from technical documentation to marketing copy to user interface text. First published internally, it evolved into a public resource at learn.microsoft.com/style-guide.
Scope and Audience
Content types covered:
- Technical documentation and tutorials
- User interface text (buttons, dialogs, error messages)
- Marketing and promotional content
- Developer documentation (APIs, SDKs, code samples)
- Chatbots and virtual agents
- Accessibility-focused content
Intended users:
- Technical writers and content strategists
- Product managers and UX designers
- Developers writing documentation
- Localization teams
- Anyone creating Microsoft-related content
Design Philosophy
Microsoft’s guide is built on a modern, minimalist design philosophy:
“Our modern design hinges on crisp simplicity. Bigger ideas and fewer words. Less head, more heart.”
This philosophy manifests in:
- Brevity over completeness — Say only what’s necessary
- Warmth over formality — Sound like a helpful colleague
- Action over description — Help users do, not just understand
- Accessibility over convenience — Design for all users first
Guide Structure and Organization
The Microsoft Writing Style Guide is organized into 17 major sections, each addressing specific aspects of content creation.
Core Sections (Hierarchical Overview)
| Section | Purpose | Key Topics |
|---|---|---|
| Top 10 Tips | Quick-start principles | Essential rules in one page |
| Brand Voice | Personality and tone | Three voice principles, customer focus |
| Bias-free Communication | Inclusive language | Gender-neutral, disability-aware writing |
| Global Communications | Internationalization | Localization tips, culture-neutral content |
| Accessibility | Universal design | Screen readers, visual accessibility |
| Scannable Content | Structure for skimmers | Headings, lists, tables |
| Grammar and Parts of Speech | Language mechanics | Verbs, pronouns, modifiers |
| Word Choice | Vocabulary decisions | Simplicity, jargon avoidance |
| Punctuation | Marks and spacing | Commas, dashes, quotation marks |
| Capitalization | Case conventions | Sentence vs. title style |
| Numbers | Numeral formatting | Dates, measurements, ranges |
| Text Formatting | Visual presentation | Bold, italic, code formatting |
| Procedures and Instructions | Task guidance | Step-by-step patterns, UI terminology |
| Developer Content | Code-focused writing | API docs, code examples |
| Chatbots and Virtual Agents | Conversational UI | Bot personality, dialogue patterns |
| A–Z Word List | Terminology reference | Specific usage decisions |
The Top 10 Tips for Microsoft Style
Microsoft distills its philosophy into 10 foundational tips—the minimum viable style guide for anyone writing Microsoft content.
Tip 1: Use Bigger Ideas, Fewer Words
“Our modern design hinges on crisp minimalism. Shorter is always better.”
Application:
- Cut unnecessary words ruthlessly
- One idea per sentence
- Lead with the main point
❌ Before: “In order to successfully complete the installation process, you will need to ensure that you have administrator privileges on your computer.”
✅ After: “To install, you need administrator privileges.”
Tip 2: Write Like You Speak
“Read your text aloud. Avoid jargon and overly complex or technical language. It should sound like a friendly conversation.”
Application:
- Read drafts aloud
- Replace formal phrases with everyday language
- If it sounds stilted, rewrite
❌ Before: “Utilize the configuration interface to establish your preferences.”
✅ After: “Use Settings to set up your preferences.”
Tip 3: Project Friendliness
“Use contractions: it’s, you’ll, you’re, we’re, let’s.”
Application:
- Contractions are required, not optional
- Creates warmth and approachability
- Matches how real people communicate
❌ Before: “You will need to restart your computer. It is important that you save your work.”
✅ After: “You’ll need to restart your computer. It’s important to save your work.”
Tip 4: Get to the Point Fast
“Lead with what’s most important. Front-load keywords for scanning. Make customer choices and next steps obvious.”
Application:
- Put conclusions first, explanations second
- Begin sentences with key information
- Structure for scanners, not readers
❌ Before: “After considering various options and reviewing the available features, you might want to try the new collaboration tools.”
✅ After: “Try the new collaboration tools. They offer…”
Tip 5: Be Brief
“Give customers just enough information to make decisions confidently. Prune every excess word.”
Application:
- Information minimalism
- Every word must earn its place
- Trust users to figure out obvious details
Tip 6: When in Doubt, Don’t Capitalize
“Default to sentence-style capitalization—capitalize only the first word of a heading or phrase and any proper nouns or names. Never Use Title Capitalization (Like This). Never Ever.”
Application:
- Sentence case for ALL headings — no exceptions
- Only capitalize proper nouns and first words
- This is one of Microsoft’s strongest mandates
❌ Never: “Getting Started With Azure Functions”
✅ Always: “Getting started with Azure Functions”
Tip 7: Skip Periods (and : ! ?)
“Skip end punctuation on titles, headings, subheadings, UI titles, and items in a list that are three or fewer words.”
Application:
- No periods on headings
- No periods on short list items (≤3 words)
- Reduces visual clutter
Tip 8: Remember the Last Comma
“In a list of three or more items, include a comma before the conjunction.”
Application:
- Oxford comma is mandatory
- “Red, white, and blue” — always include the final comma
- Prevents ambiguity
Tip 9: Don’t Be Spacey
“Use only one space after periods, question marks, and colons—and no spaces around dashes.”
Application:
- Single space after sentences
- No spaces around em dashes: “word—word”
- Clean, modern typography
Tip 10: Revise Weak Writing
“Most of the time, start each statement with a verb. Edit out you can and there is, there are, there were.”
Application:
- Begin with action verbs
- Eliminate “you can” (just state the action)
- Remove “there is/are” constructions
❌ Before: “There are three options you can choose from.”
✅ After: “Choose from three options.”
Core Philosophy: Customer-Centered Empowerment
Beyond mechanics, Microsoft’s guide reflects a philosophical stance about the relationship between content and customer.
The Empowerment Narrative
Microsoft’s brand mission—“Empower every person and every organization on the planet to achieve more”—shapes its writing philosophy:
- Focus on customer goals, not product features
- Enable action, don’t just inform
- Build confidence, don’t overwhelm
- Respect time, be efficient
Three Voice Principles
Microsoft’s voice rests on three pillars:
| Principle | Description | Manifests As |
|---|---|---|
| Warm and relaxed | Natural, grounded, occasionally fun | Contractions, conversational tone, friendly phrasing |
| Crisp and clear | To the point, simple above all | Short sentences, scanning-first structure, minimal jargon |
| Ready to lend a hand | On the customer’s side, anticipating needs | Helpful next steps, proactive guidance, empathetic errors |
Customer Focus Over Self-Promotion
“Talk about what customers can do, not what the product can do.”
❌ Product-focused: “Azure Functions supports multiple programming languages.”
✅ Customer-focused: “Build functions in the language you prefer—Python, JavaScript, C#, and more.”
When to Use Microsoft Style
Ideal Applications
Use Microsoft style when:
- Writing for Microsoft products or platforms
- Creating user-facing technology content
- Building documentation for global audiences
- Writing conversational UI (chatbots, assistants)
- Prioritizing accessibility and inclusivity
Considerations for Other Contexts
Microsoft style may need adaptation when:
- Writing academic or research content (formal tone expected)
- Creating encyclopedic reference material (neutral voice preferred)
- Following existing organizational style guides
- Writing for audiences expecting different conventions
Complementary Frameworks
Microsoft style works alongside:
- Diátaxis — Content architecture (what to write)
- WCAG — Accessibility standards (how to make it accessible)
- Your organization’s terminology — Product-specific words
References
📘 Official Sources
Microsoft Writing Style Guide 📘 [Official]
The complete, authoritative source for Microsoft writing standards.Top 10 Tips for Microsoft Style and Voice 📘 [Official]
Quick-reference page for essential principles.Microsoft Brand Voice 📘 [Official]
Deep-dive on voice principles and philosophy.
📗 Verified Community Sources
- Diátaxis Framework 📗 [Verified Community]
Complementary content architecture framework.