Skip to content

Commit d763801

Browse files
Merge pull request #246279 from chen-karen/main
Update multi-region-replication.md
2 parents 5124d0a + 2028011 commit d763801

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/key-vault/managed-hsm/multi-region-replication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ The following regions are supported as primary regions (Regions where you can re
8080
- Switzerland West
8181

8282
> [!NOTE]
83-
> US Central, US East, West US 2, Switzerland North, West Europe, Central India, Canada Central, Canada East, Japan West, Qatar Central and US West Central cannot be extended as a secondary region at this time.
83+
> US Central, US East, West US 2, Switzerland North, West Europe, Central India, Canada Central, Canada East, Japan West, Qatar Central, Poland Central and US West Central cannot be extended as a secondary region at this time.
8484
8585
## Billing
8686

@@ -92,7 +92,7 @@ The [Managed HSM soft-delete feature](soft-delete-overview.md) allows recovery o
9292

9393
## Private link behavior with Multi-region replication
9494

95-
The [Azure Private Link feature](private-link.md) allows you to access the Managed HSM service over a private endpoint in your virtual network. You would configure private endpoint on the Managed HSM in the primary region just as you would when not using the multi-region replication feature. For the Managed HSM in the secondary region, it is recommended to create another private endpoint once the Managed HSM in the primary region is replicated to the Manged HSM in the secondary region. This will redirect client requests to the Managed HSM closest to the client location.
95+
The [Azure Private Link feature](private-link.md) allows you to access the Managed HSM service over a private endpoint in your virtual network. You would configure private endpoint on the Managed HSM in the primary region just as you would when not using the multi-region replication feature. For the Managed HSM in the secondary region, it is recommended to create another private endpoint once the Managed HSM in the primary region is replicated to the Managed HSM in the secondary region. This will redirect client requests to the Managed HSM closest to the client location.
9696

9797
Some scenarios below with examples: Managed HSM in a primary region (UK South) and another Managed HSM in a secondary region (US West Central).
9898

0 commit comments

Comments
 (0)