⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 Azure → 📁 MySQL Database

🛡️ Azure MySQL Server is located in a less cost-effective region🟢

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

Logic

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

Description

Open File

Description

This policy identifies Azure MySQL 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 MySQL Database 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

Move Azure Database for MySQL Server to Another Region with Geo-Redundant Restore

Workflow Summary

1. Ensure geo-redundancy is enabled on the source server.
2. In the Azure portal, navigate to the source server's Overview page.
3. Select Restore and choose the Geo-redundant restore option.
4. Provide a new server name and configure networking settings as needed.
5. Review the configuration and initiate the restore process.
6. Once the restore is complete, verify the new server's functionality.
7. If desired, delete the source server to avoid unnecessary charges.

1. Ensure Geo-Redundancy is Enabled

• Verify that geo-redundancy is enabled on the source server. This can be done by checking the server's backup configuration in the Azure portal.
• If geo-redundancy is not enabled, you may need to enable it and wait for the configuration to take effect. Note that for Zone-redundant High Availability servers, geo-redundancy can only be enabled during server creation.

2. Navigate to the Source Server's Overview Page

... see more

policy.yaml

Open File

Linked Framework Sections

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