AZURE IN TAMIL - INFRASTRUCTURE AS CODE - BICEP PART II - DRIFT DETECTION

Identifying configuration drift between an Azure ARM (or Bicep) template and the actual deployed Azure resources is a common governance and reliability requirement.
Azure gives you multiple ways to detect drift, ranging from built‑in platform features to DIY comparisons.

Drift happens when:
A resource is changed manually in the Azure portal
A script / pipeline modifies resources outside ARM
Azure applies platform defaults or auto‑updates
A template is updated but not redeployed

✅ Goal: Detect where desired state (ARM) ≠ actual state (Azure)

Видео AZURE IN TAMIL - INFRASTRUCTURE AS CODE - BICEP PART II - DRIFT DETECTION канала Skill Up With Stan