Azure Governance Policy Guardrails
Purpose
Design or review Azure governance guardrails with Azure Policy in a way that is enforceable, scope-aware, and safe to roll out.
When to use
Use this skill when the user asks for:
- Azure Policy design or review,
- initiatives versus single policy choices,
- management-group or subscription assignment placement,
- exclusions, exemptions, or inheritance concerns,
- tag governance,
- allowed locations, resource types, or SKU restrictions,
- brownfield governance hardening,
- compliance enforcement rollout safety.
Do not use this as a substitute for full regulatory interpretation, SOC operations, or writing full organization-specific policy JSON unless the user asks for that next.
Lean operating rules
- Prefer live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and sanitized user evidence.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
References
Load these only when needed:
- MCP and evidence path - use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
- Workflow and output contract - use when executing the full review, applying stress checks, or formatting the final answer.
- Official sources - use when you need the detailed Microsoft documentation list or source notes.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- the assumptions or blockers that prevent stronger conclusions.
1---2name: techtide-azure-governance-policy-guardrails3description: Use this skill for Azure Policy guardrails, initiatives, assignment scope, management-group inheritance, exclusions, remediation risk, tag governance, allowed regions or SKUs, and staged governance rollout reviews.4---56# Azure Governance Policy Guardrails78## Purpose910Design or review Azure governance guardrails with Azure Policy in a way that is enforceable, scope-aware, and safe to roll out.1112## When to use1314Use this skill when the user asks for:1516- Azure Policy design or review,17- initiatives versus single policy choices,18- management-group or subscription assignment placement,19- exclusions, exemptions, or inheritance concerns,20- tag governance,21- allowed locations, resource types, or SKU restrictions,22- brownfield governance hardening,23- compliance enforcement rollout safety.2425Do not use this as a substitute for full regulatory interpretation, SOC operations, or writing full organization-specific policy JSON unless the user asks for that next.2627## Lean operating rules2829- Prefer live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and sanitized user evidence.30- Separate confirmed facts from inference. If state was not queried or shown, say so.31- Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.32- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.3334## References3536Load these only when needed:3738- [MCP and evidence path](references/mcp-and-evidence.md) - use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.39- [Workflow and output contract](references/workflow-and-output.md) - use when executing the full review, applying stress checks, or formatting the final answer.40- [Official sources](references/official-sources.md) - use when you need the detailed Microsoft documentation list or source notes.4142## Response minimum4344Return, at minimum:4546- the scoped target and evidence level,47- the main risks or control gaps,48- the safest next actions,49- the assumptions or blockers that prevent stronger conclusions.
TechTideOhio