🛡️ Azure 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/virtual-machine/virtual-machine-cost-effective-region
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: BEST_PRACTICE
• Policy Categories: COST

Stats

not available

Logic

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

Description

Open File

Description

This policy identifies Azure 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 flags an Azure 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 Virtual Machines and associated resources from higher-cost regions to more cost-efficient target regions using Azure Resource Mover, reducing ongoing Azure spend while maintaining continuity and compliance.

Move Azure Virtual Machines to a Lower-Cost Region with Azure Resource Mover

Remediation Workflow (Summary)

1. Perform pre-checks and validations to confirm region support, quotas, VM compatibility, and connectivity.
2. Select and add the VM and associated resources to a move collection.
3. Resolve dependencies such as virtual networks, network security groups, and storage accounts.
4. Prepare the resources by enabling replication and generating ARM templates.
5. Initiate the move to replicate data, create resources in the target region, and cut over workloads.
6. Commit the move to finalize migration and stop replication, or discard the move if it was only a test.
7. Complete post-move tasks by uninstalling agents, updating RBAC, deleting unused source resources, and cleaning up artifacts.

... see more

policy.yaml

Open File

Linked Framework Sections

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