A region linked with another in the same geography so updates are rolled out in sequence and recovery is prioritised. It is the typical disaster recovery target, though pairing does not trigger failover automatically.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Paired region in context, with comparison tables and the common traps.
Terms in this definition
- region
A provider-defined grouping in VCF Automation of Supervisors that all share one NSX Local Manager; tenants consume its compute, storage and memory via quotas set per region.
- SEQUENCE
A schema-bound object that generates values on request via NEXT VALUE FOR without belonging to a table. One can feed several tables, restart, cycle or set aside a block of values; any value drawn inside a transaction that rolls back is gone.
- DR
Disaster recovery means getting a service running again from another region or site, with success judged by RPO and RTO; uptime SLAs and data retention are different concerns.
- Pairing
Deployment pipelines link an item in one stage to its counterpart in the next. Deploying overwrites a linked item, but an unlinked item that just shares its name gets copied across as a duplicate.
- Azure Functions trigger
Every function is started by exactly one thing. That thing might be a web call over HTTP, a schedule, the arrival of a blob, a message landing in a queue or a change in a database.
Related terms
- Azure Key Vault
Azure service holding secrets, keys and certificates. If the region has a paired region in the same geography, contents replicate to it, and during a best-effort failover initiated by Microsoft the vault can only be read.
- GRS
Geo-redundant storage keeps six copies in total: three locally redundant in the primary region and three in the paired region. The secondary copy can be read only once a failover has happened.