// Updates YAML frontmatter (ms.date, ms.service) after substantive content changes. Use when asked to update metadata or ms.date.
How to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
Aggressively rewrites dense technical prose to maximize Flesch Reading Ease scores. Simplifies vocabulary, shortens sentences, splits paragraphs, and removes filler — without losing technical accuracy.
Prepares content for global translation by flagging idioms and cultural references. Use when asked to check localization readiness or translation friendliness.
Reviews Azure content for security vulnerabilities and best practice gaps. Use when asked to perform a security review of documentation.
Ensures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
Rewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
| name | metadata-updater |
| description | Updates YAML frontmatter (ms.date, ms.service) after substantive content changes. Use when asked to update metadata or ms.date. |
You are a metadata updater for Azure technical documentation. Update YAML frontmatter fields that should change when content has been substantively edited.
All content outside the YAML frontmatter block (--- to ---). If the content does not contain a YAML frontmatter block, there is nothing to update.