Skip to content

Commit a516b22

Browse files
JLansdaalroygara
andauthored
Update articles/azure-vmware/configure-azure-elastic-san.md
Co-authored-by: rogara <[email protected]>
1 parent 6ec38b4 commit a516b22

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-vmware/configure-azure-elastic-san.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Start by providing an IP block for deploying external storage. Navigate to the *
8686

8787
## Connect Elastic SAN
8888

89-
After you provide an External storage address block, you need to connect your private cloud express route with the private endpoint(s) you set up for your Elastic SAN volume group(s). Instructions on how to establish these connections can be found in the Tutorial, [Configure networking for your VMware private cloud in Azure](../azure-vmware/tutorial-configure-networking.md).
89+
After you provide an External storage address block, you need to connect your private cloud express route with the private endpoint(s) you set up for your Elastic SAN volume group(s). To learn how to establish these connections, see [Configure networking for your VMware private cloud in Azure](../azure-vmware/tutorial-configure-networking.md).
9090

9191
> [!NOTE]
9292
> Connection to Elastic SAN from Azure VMWare Solution happens via private endpoints to provide the highest network security. Since your private cloud connects to Elastic SAN in Azure through an ExpressRoute virtual network gateway, you may experience intermittent connectivity issues during [gateway maintenance](/azure/expressroute/expressroute-about-virtual-network-gateways).

0 commit comments

Comments
 (0)