Azure Compliance ControlsAzure Database for MySQL
MySQL servers should have geo-redundant backup enabled
Azure Database for MySQL allows you to choose the redundancy option for your database server. It can be set to a geo-redundant backup storage, replicated to a paired region. Configuring geo-redundant storage for backup is only allowed during server create.
What this control checks
Geo-redundant backup setting on MySQL database servers
Framework mappings
The clauses this control is mapped to in each framework.
- CP-6 Alternate Storage Site
- CP-6(1) Separation From Primary Site
- CP-9 System Backup
FedRAMP Moderate Baseline Rev 4
- CP-6 Alternate Storage Sites
- CP-6(1) Separation From Primary Site
- CP-9: Information System Backup
- 3.8.9: Protect the confidentiality of backup CUI at storage locations.
- 5.2 Policy for Information System Audit (IS Audit)
- 6 Business Continuity Planning (BCP) and Disaster Recovery
- 6.2 Recovery strategy / Contingency Plan
- 6.3 Backup and Recovery
- MP.L2-3.8.9 Protect the confidentiality of backup CUI at storage locations
- CP-6 Alternate Storage Sites
- CP-6(1) Separation From Primary Site
- CP-9 System Backup
- 1617.09l1Organizational.23-09.l 09.05 Information Back-Up
- 1622.09l2Organizational.23-09.l 09.05 Information Back-Up
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
mysql_db_server_geo_redundant_backup_enabled - Checkov Check:
CKV_AZURE_94 - Powerpipe Control:
azure_compliance.control.mysql_db_server_geo_redundant_backup_enabled - Azure Policy Definition:
82339799-d096-41ae-8538-b108becf0970
Last reviewed: 2026-10-13