azure-drift-detector

Azure drift detection compares live Azure resources against stored IaC state in .azure/deployments and requirements.json. It reports differences by severity and provides guided reconciliation options to accept, revert, or document the drift.

The best way to reconcile Azure deployment drift is running drift checks that compare live resources against stored IaC state. You can accept the live state, revert Azure resources to match the state, or document the baseline differences for audit.

Yes, you need az and jq installed to run Azure drift detection. The engine requires these dependencies to query live Azure resources and process the JSON state data stored in .azure/deployments and requirements.json.

Yes, you can run pre-deployment validation to prevent Azure IaC conflicts. The drift detection engine supports scheduled checks and pre-deployment validation to surface differences between live resources and stored state before applying new changes.

Drift detection compares live Azure Function Apps and storage against stored IaC state by evaluating configurations in .azure/deployments and requirements.json. It identifies mismatches, categorizes them by severity, and outputs guided reconciliation decisions.

You should document configuration drift instead of reverting Azure resources when the live changes are intentional. Documenting maintains an auditable baseline of the accepted differences, while reverting realigns the live Azure environment to the stored IaC state.