Assigned the built-in allowed-locations policy at resource-group scope through Bicep so that any future resource outside the approved region is rejected at deployment time rather than relying on convention. Not deployed.
- What worked
- A single built-in definition covers the data-residency requirement for every resource type, and the assignment is a small declarative resource that slots into the existing template.