The config had shifted, and no one knew why. The pipeline was clean yesterday. Today, policy violations were creeping in. This is the silent danger of IaC drift.
Infrastructure as Code drift happens when deployed resources no longer match the declared configuration in your repository. In Databricks, that drift can unlock risky changes. Masking rules may be disabled. Access levels may be altered. Permissions can expand without review. Every deviation puts sensitive data in play.
Databricks Data Masking is built to protect against exposure. Applied correctly, it hides PII and sensitive fields from unauthorized users. But masking only holds if enforcement matches your IaC definitions. Drift breaks that link. Your code says “mask,” the live environment says otherwise.
IaC drift detection closes that gap. The detection process continuously compares actual Databricks resources to your IaC source of truth. Any mismatch is flagged. This includes masking policy changes and role assignments. Automated checks can run on every commit, every deploy, and even on a schedule to monitor long-running environments.