freshness review - 8/12

Author: duongau

articles/frontdoor/private-link.md

@@ -5,7 +5,7 @@ services: frontdoor
 author: duongau
 ms.service: azure-frontdoor
 ms.topic: conceptual
-ms.date: 05/17/2023
+ms.date: 08/12/2024
 ms.author: duau
 ms.custom: references_regions
 ---
@@ -20,26 +20,26 @@ Azure Front Door Premium can connect to your origin using Private Link. Your ori
 
 ## How Private Link works
 
-When you enable Private Link to your origin in Azure Front Door Premium, Front Door creates a private endpoint on your behalf from an Azure Front Door managed regional private network. You'll receive an Azure Front Door private endpoint request at the origin pending your approval.
+When you enable Private Link to your origin in Azure Front Door Premium, Front Door creates a private endpoint on your behalf from an Azure Front Door managed regional private network. You receive an Azure Front Door private endpoint request at the origin pending your approval.
 
 > [!IMPORTANT]
 > You must approve the private endpoint connection before traffic can pass to the origin privately. You can approve private endpoint connections by using the Azure portal, Azure CLI, or Azure PowerShell. For more information, see [Manage a Private Endpoint connection](../private-link/manage-private-endpoint.md).
 
-After you enable an origin for Private Link and approve the private endpoint connection, it can take a few minutes for the connection to be established. During this time, requests to the origin will receive an Azure Front Door error message. The error message will go away once the connection is established.
+After you enable an origin for Private Link and approve the private endpoint connection, it can take a few minutes for the connection to be established. During this time, requests to the origin receives an Azure Front Door error message. The error message goes away once the connection is established.
 
-Once your request is approved, a private IP address gets assigned from the Azure Front Door managed virtual network. Traffic between your Azure Front Door and your origin will communicate using the established private link over the Microsoft backbone network. Incoming traffic to your origin is now secured when arriving at your Azure Front Door.
+Once your request is approved, a private IP address gets assigned from the Azure Front Door managed virtual network. Traffic between your Azure Front Door and your origin communicates using the established private link over the Microsoft backbone network. Incoming traffic to your origin is now secured when arriving at your Azure Front Door.
 
 :::image type="content" source="./media/private-link/enable-private-endpoint.png" alt-text="Screenshot of enable Private Link service checkbox from origin configuration page.":::
 
 ## Association of a private endpoint with an Azure Front Door profile
 
 ### Private endpoint creation
 
-Within a single Azure Front Door profile, if two or more Private Link enabled origins are created with the same set of Private Link, resource ID and group ID, then for all such origins only one private endpoint gets created. Connections to the backend can be enabled using this private endpoint. This setup means you only have to approve the private endpoint once because only one private endpoint gets created. If you create more Private Link enabled origins using the same set of Private Link location, resource ID and group ID, you won't need to approve anymore private endpoints.
+Within a single Azure Front Door profile, if two or more Private Link enabled origins are created with the same set of Private Link, resource ID and group ID, then for all such origins only one private endpoint gets created. Connections to the backend can be enabled using this private endpoint. This setup means you only have to approve the private endpoint once because only one private endpoint gets created. If you create more Private Link enabled origins using the same set of Private Link location, resource ID, and group ID, you don't need to approve anymore private endpoints.
 
 #### Single private endpoint
 
-For example, a single private endpoint gets created for all the different origins across different origin groups but in the same Azure Front Door profile as shown in the below table:
+For example, a single private endpoint gets created for all the different origins across different origin groups but in the same Azure Front Door profile as shown in the following table:
 
 :::image type="content" source="./media/private-link/single-endpoint.png" alt-text="Diagram showing a single private endpoint created for origins created in the same Azure Front Door profile.":::
 
@@ -63,30 +63,30 @@ A new private endpoint gets created in the following scenario:
 
 ### Private endpoint removal
 
-When an Azure Front Door profile gets deleted, private endpoints associated with the profile will also get deleted. 
+When an Azure Front Door profile gets deleted, private endpoints associated with the profile also get deleted. 
 
 #### Single private endpoint
 
-If AFD-Profile-1 gets deleted, then the PE1 private endpoint across all the origins will also be deleted.
+If AFD-Profile-1 gets deleted, then the PE1 private endpoint across all the origins also gets deleted.
 
-:::image type="content" source="./media/private-link/delete-endpoint.png" alt-text="Diagram showing if AFD-Profile-1 gets deleted then PE1 across all origins will get deleted.":::
+:::image type="content" source="./media/private-link/delete-endpoint.png" alt-text="Diagram showing if AFD-Profile-1 gets deleted then PE1 across all origins get deleted.":::
 
 #### Multiple private endpoints
 
-* If AFD-Profile-1 gets deleted, all private endpoints from PE1 through to PE4 will be deleted.
+* If AFD-Profile-1 gets deleted, all private endpoints from PE1 through to PE4 gets deleted.
 
     :::image type="content" source="./media/private-link/delete-multiple-endpoints.png" alt-text="Diagram showing if AFD-Profile-1 gets deleted, all private endpoints from PE1 through PE4 gets deleted.":::
 
-* Deleting a Front Door profile won't affect private endpoints created for a different Front Door profile. 
+* Deleting an Azure Front Door profile doesn't affect private endpoints created for a different Front Door profile. 
 
-    :::image type="content" source="./media/private-link/delete-multiple-profiles.png" alt-text="Diagram showing Azure Front Door profile getting deleted won't affect private endpoints in other Front Door profiles.":::
+    :::image type="content" source="./media/private-link/delete-multiple-profiles.png" alt-text="Diagram showing Azure Front Door profile getting deleted but doesn't affect private endpoints in other Front Door profiles.":::
 
     For example:
 
-    * If AFD-Profile-2 gets deleted, only PE5 will be removed.
-    * If AFD-Profile-3 gets deleted, only PE6 will be removed.
-    * If AFD-Profile-4 gets deleted, only PE7 will be removed.
-    * If AFD-Profile-5 gets deleted, only PE8 will be removed.
+    * If AFD-Profile-2 gets deleted, only PE5 is removed.
+    * If AFD-Profile-3 gets deleted, only PE6 is removed.
+    * If AFD-Profile-4 gets deleted, only PE7 is removed.
+    * If AFD-Profile-5 gets deleted, only PE8 is removed.
 
 ## Region availability
 
@@ -101,8 +101,8 @@ Azure Front Door private link is available in the following regions:
 | East US 2 | UK South | | East Asia |
 | South Central US | West Europe | | |
 | West US 3 | Sweden Central | | |
-| US Gov Arizona |||
-| US Gov Texas |||
+| US Gov Arizona | | | |
+| US Gov Texas | | | |
 
 
 ## Limitations
@@ -112,7 +112,7 @@ Origin support for direct private endpoint connectivity is currently limited to:
 * Web App
 * Internal load balancers, or any services that expose internal load balancers such as Azure Kubernetes Service, Azure Container Apps or Azure Red Hat OpenShift
 * Storage Static Website
-* Application Gateway (Preview only. Please do not put production workloads)
+* Application Gateway (Preview only. Don't use in production environments)
 
 > [!NOTE]
 > * This feature isn't supported with Azure App Service Slots or Functions.