Skip to content

Commit 883ff82

Browse files
stevemunkpbrasil
andauthored
Update articles/azure-maps/private-endpoints.md
Co-authored-by: Peter Brasil <[email protected]>
1 parent dad95f3 commit 883ff82

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/azure-maps/private-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Within this zone, a DNS record maps your Azure Maps account's unique ID and regi
8282
Clients inside the virtual network resolve the hostname to a private IP address for private connectivity, while clients outside the network resolve the same hostname to the Azure Maps public endpoint. This split‑horizon DNS approach lets you use a single endpoint URL both inside and outside the virtual network.
8383

8484
If you don't use automatic DNS integration, configure DNS manually so the Azure Maps account hostname
85-
(`<maps-account-client-id>.<location>.privatelink.account.maps.azure.com`) resolves to the private endpoint IP address within your network. For more information, see [Azure Private Endpoint DNS documentation](../private-link/private-endpoint-dns.md).
85+
(`<maps-account-client-id>.<location>.account.maps.azure.com`) resolves to the private endpoint IP address within your network. For more information, see [Azure Private Endpoint DNS documentation](../private-link/private-endpoint-dns.md).
8686

8787
### 3. Use the private endpoint in your applications
8888

0 commit comments

Comments
 (0)