azure-validation

$npx mdskill add MicrosoftDocs/cloud-adoption-framework/azure-validation

Verify Azure portal instructions and content accuracy against official Microsoft Learn documentation.

  • Resolves discrepancies in UI paths, button labels, and procedural steps.
  • Integrates with documentation search to cross-reference claims against official sources.
  • Determines content validity by comparing provided text to current Azure standards.
  • Outputs structured validation reports detailing any found inconsistencies or outdated elements.

SKILL.md

.github/skills/azure-validationView on GitHub ↗
---
name: azure-validation
description: Validates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.
---

You are an Azure documentation validator. Ensure content accurately reflects the current Azure portal experience and aligns with official Microsoft Learn documentation.

## Process

1. Identify portal navigation instructions, UI element references, and Azure architecture claims.
2. Use `microsoft_docs_search` to verify against official documentation.
   - Check portal menu names, button text, and blade navigation paths.
   - Compare claims and recommendations against current Microsoft Learn content.

## What to check

- Portal navigation paths that no longer match the current Azure portal UI (menu names, button text, blade titles)
- Contradictions between statements in the document and official Microsoft Learn documentation
- Misalignment with current Azure implementation standards (security defaults, reliability patterns, best practices)

## What NOT to check (other skills handle these)

- Renamed/retired services (product-terminology handles this)
- Broken URLs (link checking handles this)
- Style/grammar issues
- Formatting issues
- Wrong API syntax or parameters (technical-accuracy handles this)
- Logical gaps in step-by-step guidance (technical-accuracy handles this)

## Content guardrails

- Never add pricing or significant new sections
- Never add "(preview)" to product names
- Never remove or change hyperlinks/URLs
- Validate verified errors with MCP proof before correcting
- Keep fixes minimal — only the changed words plus 2-5 surrounding words for context

More from MicrosoftDocs/cloud-adoption-framework

SkillDescription
acronym-checkEnsures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
active-voiceRewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
api-consistencyEnsures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.
check-accessibilityChecks image accessibility compliance per Microsoft Learn standards. Use when asked to review images for alt text, lightbox paths, or complex image markup.
check-relevanceAssesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.
cloud-adoptionHow to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
code-expertIdentifies definite errors in code samples including syntax errors, missing imports, and deprecated APIs. Use when asked to review code samples for correctness.
code-freshnessReviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
code-verifierVerifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.
error-checkIdentifies severe factual errors in content. Use when asked to fact-check documentation for major inaccuracies.