Skip to content

Commit 710429e

Browse files
committed
removed public peering
1 parent 2a6dc9f commit 710429e

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/site-recovery/site-recovery-faq.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -262,8 +262,7 @@ sections:
262262
answer: |
263263
Yes, [ExpressRoute can be used](concepts-expressroute-with-site-recovery.md) to replicate on-premises virtual machines to Azure.
264264
265-
- Azure Site Recovery replicates data to an Azure Storage over a public endpoint. You need to set up [Microsoft peering](../expressroute/expressroute-circuit-peerings.md#microsoftpeering) or use an existing [public peering](../expressroute/about-public-peering.md) (deprecated for new circuits) to use ExpressRoute for Site Recovery replication.
266-
- Microsoft peering is the recommended routing domain for replication.
265+
- Azure Site Recovery replicates data to an Azure Storage over a public endpoint. You need to set up [Microsoft peering](../expressroute/expressroute-circuit-peerings.md#microsoftpeering) to use ExpressRoute for Site Recovery replication.
267266
- Replication is supported over private peering only when private endpoints are enabled for the vault.
268267
- If you're protecting VMware machines or physical machines, ensure that the [Networking Requirements](vmware-azure-configuration-server-requirements.md#network-requirements) for Configuration Server are also met. Connectivity to specific URLs is required by Configuration Server for orchestration of Site Recovery replication. ExpressRoute cannot be used for this connectivity.
269268
- After the virtual machines have been failed over to an Azure virtual network, you can access them using the [private peering](../expressroute/expressroute-circuit-peerings.md#privatepeering) setup with the Azure virtual network.

0 commit comments

Comments
 (0)