Skip to content

Commit 1ff751b

Browse files
authored
Update private-endpoint.md
1 parent 88ca835 commit 1ff751b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/app-service/networking/private-endpoint.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Using Private Endpoint for your Web App enables you to:
2424
- Secure your Web App by configuring the Private Endpoint, eliminating public exposure.
2525
- Securely connect to Web App from on-premises networks that connect to the VNet using a VPN or ExpressRoute private peering.
2626

27-
If you just need a secure connection between your VNet and your Web App, a Service Endpoint is the simplest solution. If you also need to reach the web app from on-premises through an Azure gateway, a regionally peered VNet or a globally peered VNet, Private Endpoint is the solution.
27+
If you just need a secure connection between your VNet and your Web App, a Service Endpoint is the simplest solution. If you also need to reach the web app from on-premises through an Azure gateway, a regionally peered VNet, or a globally peered VNet, Private Endpoint is the solution.
2828

2929
For more information, see [Service Endpoints][serviceendpoint].
3030

@@ -59,9 +59,9 @@ In the Web HTTP logs of your Web App, you will find the client source IP. This i
5959
## DNS
6060

6161
As this feature is in preview, we don't change the DNS entry during the preview. You need to manage the DNS entry in your private DNS server or Azure DNS private zone yourself.
62-
If you need to use a custom DNS name, you must add the custom name in your Web App. During the preview, the custom name must be validated like any custom name, using public DNS resolution. See [custom DNS validation][dnsvalidation] for more information.
62+
If you need to use a custom DNS name, you must add the custom name in your Web App. During the preview, the custom name must be validated like any custom name, using public DNS resolution. For more informations, see [custom DNS validation][dnsvalidation].
6363

64-
If you need to use the Kudu console, or Kudu REST API (deployment with Azure DevOps for example), you need to create two records in your Azure DNS private zone or your custom DNS server.
64+
If you need to use the Kudu console, or Kudu REST API (deployment with Azure DevOps self-hosted agents for example), you need to create two records in your Azure DNS private zone or your custom DNS server.
6565
- PrivateEndpointIP yourwebappname.azurewebsites.net
6666
- PrivateEndpointIP yourwebappname.scm.azurewebsites.net
6767

0 commit comments

Comments
 (0)