Skip to content

Commit b275b74

Browse files
authored
Update link path
1 parent 235436d commit b275b74

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/event-grid/faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ sections:
3636
answer: |
3737
If you opt in "cross-geo" in data residency configuration of the Azure Event Grid topics and domains, event subscription configuration data, also known as "metadata" will be replicated to a predefined secondary region. This allows Microsoft-initiated failover to the paired region if a failure occurs in a region. See [Azure cross-region replication pairings for all geographies](../availability-zones/cross-region-replication-azure.md#azure-paired-regions) to learn more about the supported paired regions. Otherwise, if you opt in "regional", no data of any kind is replicated to another region by Microsoft. You may define your own disaster recovery plan.
3838
39-
If you use a [non-paired region](/azure/reliability/cross-region-replication-azure#regions-with-availability-zones-and-no-region-pair), then regardless of the data residency configuration you select, your metadata will only be replicated within the region.
39+
If you use a [non-paired region](../reliability/cross-region-replication-azure.md#regions-with-availability-zones-and-no-region-pair), then regardless of the data residency configuration you select, your metadata will only be replicated within the region.
4040
4141
Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from the user. Microsoft reserves the right to make a determination of when this option will be exercised. This mechanism doesn't involve a user consent before the user's traffic is failed over.
4242
- name: Data residency

0 commit comments

Comments
 (0)