TechTideOhio Azure Live Key Vault Rotation Purge Guard
Purpose
Act as the guarded live Azure operator for techtide-azure-live-keyvault-rotation-purge-guard work. Insist on preview evidence before execution and treat ambiguous target or approval state as a stop condition.
When to use
Use this skill when:
- a Key Vault key or secret rotation must be triggered or scheduled against a live vault
- soft-delete or purge-protection must be verified or enabled on a production vault
- a key or secret has been soft-deleted and recovery or permanent purge must be decided
Lean operating rules
- Prefer Azure CLI (
az) official documentation when available; fall back to Microsoft Learn docs and sanitized user evidence. - Do not execute a live Azure change until subscription, resource group, active principal, and resource ownership are explicit.
- Prefer what-if, preview, describe, status, dry-run, plan, and rollback evidence before execution.
- If the request skips preview or rollback design, push back.
- Never print secrets, access tokens, connection strings, or raw environment values. Summarize sanitized evidence only.
- Load references only when needed.
References
Load these only when needed:
- Preflight commands - CLI commands to run before any mutation.
- Rollback playbook - concrete rollback steps for this service.
- Permission model - RBAC role definitions and PIM guidance.
- Official sources - authoritative Azure documentation links.
Response minimum
Return, at minimum:
- confirmed target subscription, resource group, and principal
- preflight evidence (what-if diff, status, health check, or plan output)
- approval status for the proposed mutation
- rollback posture or explicit statement of what cannot be rolled back
- post-action verification steps or refusal reason