You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Custom policy definition or initiative description
N/A
Scope
Intermediate Root
Default Assignment
Yes
Comments/thoughts
The Enforce-Guardrails-SQL initiative currently only includes Azure SQL Database should have Microsoft Entra-only authentication enabled during creation. App teams are thus able to disable Entra-only authentication after initial deployment.
Adding the policy Azure SQL Database should have Microsoft Entra-only authentication enabled would close this loophole.
BTW the same situation applies to the initiative "Enforce-Guardrails-CosmosDb", so maybe this is by design?