Skip to content

Commit 8fef07e

Browse files
authored
Update troubleshoot-private-endpoint-connectivity.md
1 parent 163329a commit 8fef07e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/private-link/troubleshoot-private-endpoint-connectivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Review these steps to make sure all the usual configurations are as expected to
100100
1. Source Virtual Machine should have the route to Private Endpoint IP next hop as InterfaceEndpoints in the NIC Effective Routes.
101101

102102
a. If you are not able to see the Private Endpoint Route in the Source VM, check if
103-
- The Source VM and the Private Endpoint belongs to the same VNET. If yes, then you need to engage support.
103+
- The Source VM and the Private Endpoint are part of the same VNET. If yes, then you need to engage support.
104104
- The Source VM and the Private Endpoint are part of different VNETs that are directly peered with each other. If yes, then you need to engage support.
105105
- The Source VM and the Private Endpoint are part of different VNETs that are not directly peered with each other, then check for the IP connectivity between the VNETs.
106106

0 commit comments

Comments
 (0)