An Azure relational database service.
For Azure SQL Database, when backup storage redundancy is set to Geo-redundant (GRS or GZRS), backups are always replicated to the paired secondary region, regardless of whether that region is generally restricted for creating customer resources.
From the backup platform perspective:
- GRS “copies your data asynchronously three times to a single physical location in the paired secondary region.” This is an internal platform operation and does not require that customer access be enabled to that region.
- Geo-restore for Azure SQL Database “uses geo-replicated backups as the source” and “you can restore a database on any logical server in any Azure region from the most recent geo-replicated backups,” as long as the database is configured with geo-redundant or geo-zone-redundant backup storage.
Implications for the described scenario (Sweden Central with paired Sweden South):
- Backups of the database in Sweden Central configured with GRS/GZRS will still be replicated to the paired region (Sweden South) by the platform.
- Geo-restore will allow restoring the database to a logical server in any Azure region in the same subscription, not just the paired region. Therefore, even if direct customer access to Sweden South is restricted, geo-restore can be performed to another accessible region.
- The main consideration is that GRS/GZRS implies data is stored in the paired region, which may affect data residency/compliance requirements. If data must not leave a single region, use LRS or ZRS instead and enforce this via Azure Policy (for example, using the built-in policy “Azure SQL DB should avoid using GRS backup”).
There is no indication in the documentation that lack of customer access to the paired region prevents replication or breaks restore; the platform manages geo-replication and geo-restore as long as GRS/GZRS is configured.
References: