Azure Policy: diagnose an expired exemption before disabling the assignment
A production runbook for tying expiry, scope, assignment and compliance together before renewing an Azure Policy exemption or disabling the guardrail.
Read article
Tag
9 articles connected to this technical signal.
A production runbook for tying expiry, scope, assignment and compliance together before renewing an Azure Policy exemption or disabling the guardrail.
Read articleA production runbook for separating ARM rollout, WAF associations, rule priority and request variance before a global Application Gateway policy rollback.
Read articleA production runbook to separate health signal, grace period, service state, VMSS model and local data before changing Replace, Reimage or Restart.
Read articleA production runbook for testing an Azure VM recovery point in isolation, validating the system and application, measuring recovery, then deciding readiness, remediation or rollback.
Read articleA production runbook to separate disk limits, VM I/O caps, burst credits and guest contention before resizing a disk or changing its performance tier.
Read articleA production runbook for qualifying missing Azure Monitor logs with Diagnostic Settings, DCRs, ingestion, KQL, cost controls, validation and rollback before changing alerts.
Read articleA production runbook for deciding an Azure rollback after deployment with Azure Monitor, KQL, impact correlation, regression evidence, validation and controlled recovery.
Read articleStructure architecture documentation that remains useful after production with decisions, limits, validation commands, failure modes, rollback and operational evidence.
Read articlePrepare an Azure Private Endpoint production rollout with a validation matrix that separates DNS, routing, public access closure, TLS, application dependencies and tests from Azure and on premises.
Read article