🛡️ Azure SQL Database is located in a less cost-effective region🟢

• Contextual name: 🛡️ Database is located in a less cost-effective region🟢
• ID: /ce/ca/azure/sql-database/database-cost-effective-region
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure SQL Database
  • 🔌 Azure SQL Database - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies Azure SQL Database that are provisioned in Azure regions known to have higher pricing compared to nearby alternatives.

Rationale

Selecting the appropriate Azure region is essential for optimizing both cost and performance. Service pricing can vary across regions due to factors such as infrastructure expenses, energy costs, and local taxes. Deploying workloads in cost-efficient regions can result in substantial savings on monthly Azure expenditures.

Impact

Migrating workloads to different regions requires careful planning to avoid service disruptions and to ensure latency, compliance, and data sovereignty requirements continue to be met.

Audit

This policy flagged an Azure SQL Database as INCOMPLIANT if it is running in one of the following regions identified as less cost-efficient:

Region	Recommended Alternative
westus, westcentralus	westus3, westus2

... see more

Remediation

Open File

Remediation

Migrate Azure SQL Database Resources to Another Region with Azure Resource Mover

Workflow Summary

1. Verify that you have Owner access on the subscription containing the resources to be moved.
2. Ensure the subscription has sufficient quota to create the resources in the target region.
3. Confirm that the target region supports the features of your Azure SQL databases and elastic pools.
4. In the target region, create a target server for each source server and ensure proper user access.
5. Check if the databases are encrypted with transparent data encryption (TDE) and plan for moving any associated Azure Key Vaults.
6. Remove advanced data security settings, autotuning settings, database alerts, and server-level firewall rules before initiating the move.
7. In the Azure portal, use Azure Resource Mover to select the source subscription and region, and the destination region.
8. Select the resources to move, ensuring they are supported for migration.
9. Review and initiate the move process, monitoring for any issues.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Resource Optimization			24		no data