⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 Azure → 📁 SQL Virtual Machine

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

• Contextual name: 🛡️ Virtual Machine is located in a less cost-effective region🟢
• ID: /ce/ca/azure/sql-virtual-machine/virtual-machine-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 Virtual Machine
  • 🔌 Azure SQL Virtual Machine - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies Azure SQL Virtual Machines 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 Virtual Machine as INCOMPLIANT if it is running in one of the following regions identified as less cost-efficient:

Region	Recommended Alternative

... see more

Remediation

Open File

Remediation

Migrate Azure SQL Server VM to a Different Region with Azure Site Recovery

Workflow Summary

1. Verify that the source SQL Server VM and target region meet all prerequisites for migration.
2. Prepare the source VM by updating certificates, installing updates, and confirming network connectivity.
3. Configure Azure Site Recovery by creating a Recovery Services vault and enabling replication for the VM.
4. Perform a test failover to the target region to validate functionality and replication.
5. Execute the actual migration by initiating a failover and committing the move to the target region.
6. Clean up post-migration by stopping replication, removing the source VM from the vault, and deleting residual resources.

1. Verify Prerequisites

Before initiating the migration, confirm the following:

• Source and Target Region Support: Ensure that moving from your source region to your target region is supported.
• Permissions: Verify that you have the necessary permissions: Virtual Machine Contributor and Site Recovery Contributor.

... see more

policy.yaml

Open File

Linked Framework Sections

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