Skip to content

Commit fdd313a

Browse files
committed
Implement feedback
1 parent d3e323a commit fdd313a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/digital-twins/how-to-enable-private-link.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ armclient PATCH /subscriptions/<your-Azure-subscription-ID>/resourceGroups/<your
247247

248248
---
249249

250-
## Deploy with ARM
250+
## Deploy with ARM templates
251251

252252
You can also set up Private Link with Azure Digital Twins using an ARM template.
253253

@@ -269,12 +269,14 @@ Here are some common issues experienced with Private Link for Azure Digital Twin
269269

270270
**Resolution:** This error occurs when `publicNetworkAccess` has been disabled for the Azure Digital Twins instance and API requests are expected to come through Private Link, but the call was routed through the public network (possibly over a load balancer configured for a virtual network). Make sure that your API client is resolving the private IP for the private endpoint when trying to access the API through the endpoint hostname.
271271

272-
To facilitate hostname resolution to the private IP of the private endpoint in a subnet, you can configure a private DNS zone. Verify that the private DNS zone is correctly linked to the virtual network and uses the right zone name, such as `privatelink.digitaltwins.azure.net`.
272+
To facilitate hostname resolution to the private IP of the private endpoint in a subnet, you can configure a [private DNS zone](../private-link/private-endpoint-dns.md). Verify that the private DNS zone is correctly linked to the virtual network and uses the right zone name, such as `privatelink.digitaltwins.azure.net`.
273273

274274
* **Issue:** When trying to access Azure Digital Twins through a private endpoint, the connection times out.
275275

276276
**Resolution:** Verify that there are no [network security group](../virtual-network/network-security-groups-overview.md) rules that prohibit the client from communicating to the private endpoint and its subnet. Communication on TCP port 443 must be permitted between the client's source IP address/subnet, and the private endpoint destination IP address/subnet.
277277

278+
For more Private Link troubleshooting suggestions, see [Troubleshoot Azure Private Endpoint connectivity problems](../private-link/troubleshoot-private-endpoint-connectivity.md).
279+
278280
## Next steps
279281

280282
Quickly set up a protected environment with Private Link using an ARM template: [Azure Digital Twins with Azure function and Private Link](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.digitaltwins/digitaltwins-with-function-private-link).

0 commit comments

Comments
 (0)