TechTideOhio Azure RBAC Review
Purpose
Review Azure access decisions against least privilege, scope minimization, and operational safety.
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.