Merge pull request #291428 from AbdullahBell/private-link-freshness

Jill Grant · web-flow · commit 9a54ca6962d2 · 2024-12-04T21:54:12.000-07:00
Private Link: Freshness: 19 articles
diff --git a/articles/private-link/create-private-endpoint-bicep.md b/articles/private-link/create-private-endpoint-bicep.md
@@ -5,7 +5,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 03/28/2024
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: subject-armqs, mode-arm, template-concept, devx-track-bicep
 #Customer intent: As someone who has a basic network background but is new to Azure, I want to create a private endpoint using Bicep.
diff --git a/articles/private-link/create-private-endpoint-cli.md b/articles/private-link/create-private-endpoint-cli.md
@@ -5,7 +5,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 06/14/2023
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: mode-api, devx-track-azurecli, template-quickstart
 #Customer intent: As someone who has a basic network background but is new to Azure, I want to create a private endpoint by using the Azure CLI.
diff --git a/articles/private-link/create-private-endpoint-portal.md b/articles/private-link/create-private-endpoint-portal.md
@@ -5,7 +5,7 @@ description: In this quickstart, learn how to create a private endpoint using th
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 02/26/2024
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: mode-ui, template-quickstart
 #Customer intent: As someone who has a basic network background but is new to Azure, I want to create a private endpoint on a SQL server so that I can securely connect to it.
diff --git a/articles/private-link/create-private-endpoint-powershell.md b/articles/private-link/create-private-endpoint-powershell.md
@@ -5,7 +5,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 02/26/2024
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: devx-track-azurepowershell, mode-api, template-quickstart
 #Customer intent: As someone who has a basic network background but is new to Azure, I want to create a private endpoint by using Azure PowerShell.
diff --git a/articles/private-link/create-private-endpoint-template.md b/articles/private-link/create-private-endpoint-template.md
@@ -5,7 +5,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 03/28/2024
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: subject-armqs, mode-arm, template-quickstart, devx-track-arm-template
 #Customer intent: As someone who has a basic network background but is new to Azure, I want to create a private endpoint by using an ARM template.
diff --git a/articles/private-link/create-private-endpoint-terraform.md b/articles/private-link/create-private-endpoint-terraform.md
@@ -2,7 +2,7 @@
 title: 'Quickstart: Create a private endpoint - Terraform'
 description: In this quickstart, you learn how to create a private endpoint using Terraform.
 ms.topic: quickstart
-ms.date: 02/22/2024
+ms.date: 12/04/2024
 ms.custom: devx-track-terraform
 ms.service: azure-virtual-network
 author: asudbring
diff --git a/articles/private-link/create-private-link-service-bicep.md b/articles/private-link/create-private-link-service-bicep.md
@@ -6,7 +6,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 03/12/2024
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: subject-armqs, mode-arm, template-quickstart, devx-track-bicep
 ---
diff --git a/articles/private-link/create-private-link-service-cli.md b/articles/private-link/create-private-link-service-cli.md
@@ -5,7 +5,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 03/28/2024
+ms.date: 12/04/2024
 ms.author: abell
 ms.devlang: azurecli
 ms.custom: mode-api, devx-track-azurecli, template-quickstart
diff --git a/articles/private-link/create-private-link-service-portal.md b/articles/private-link/create-private-link-service-portal.md
@@ -6,7 +6,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 08/29/2023
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: mode-ui, template-quickstart
 #Customer intent: As someone with a basic network background who's new to Azure, I want to create an Azure Private Link service by using the Azure portal
diff --git a/articles/private-link/create-private-link-service-powershell.md b/articles/private-link/create-private-link-service-powershell.md
@@ -5,7 +5,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 06/23/2023
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: devx-track-azurepowershell, mode-api, template-quickstart
 #Customer intent: As someone with a basic network background, but is new to Azure, I want to create an Azure private link service
diff --git a/articles/private-link/create-private-link-service-template.md b/articles/private-link/create-private-link-service-template.md
@@ -5,7 +5,7 @@ description: In this quickstart, you use an Azure Resource Manager template (ARM
 author: abell
 ms.service: azure-private-link
 ms.topic: quickstart
-ms.date: 03/12/2024
+ms.date: 12/04/2024
 ms.author: abell
 ms.custom: subject-armqs, mode-arm, template-quickstart, devx-track-arm-template
 ---
diff --git a/articles/private-link/disable-private-endpoint-network-policy.md b/articles/private-link/disable-private-endpoint-network-policy.md
@@ -1,12 +1,13 @@
 ---
 title: Manage network policies for private endpoints
 titleSuffix: Azure Private Link
-description: Learn how to manage network policies for private endpoints.
+description: Learn how to enable and manage network policies for Azure private endpoints in an Azure virtual network. 
+# Customer intent: Learn how to manage network policies for private endpoints.
 services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: how-to
-ms.date: 07/26/2023
+ms.date: 12/04/2024
 ms.author: abell 
 ms.devlang: azurecli
 ms.custom: devx-track-azurepowershell, template-how-to
@@ -34,6 +35,8 @@ The following examples describe how to enable and disable `PrivateEndpointNetwor
 
 ## Enable network policy
 
+Follow these steps to configure Network Security Groups and Route tables for your private endpoints.
+
 # [**Portal**](#tab/network-policy-portal)
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
@@ -46,7 +49,7 @@ The following examples describe how to enable and disable `PrivateEndpointNetwor
 
 1. Select the **default** subnet.
 
-1. In the properties for the **default** subnet, select the checkboxes for **Network Security Groups**, **Route tables**, or both in **NETWORK POLICY FOR PRIVATE ENDPOINTS**.
+1. In the **Edit subnet** pane, under **Network Policy for Private Endpoints**, select the boxes for **Network security groups** or **Route tables** as needed.
 
 1. Select **Save**.
 
@@ -129,7 +132,7 @@ This section describes how to enable subnet private endpoint policies by using a
 
 1. Select the **default** subnet.
 
-1. In the properties for the **default** subnet, select **Disabled** in **NETWORK POLICY FOR PRIVATE ENDPOINTS**.
+1. In the **Edit subnet** pane, under **Network Policy for Private Endpoints**, select the box **Disabled**.
 
 1. Select **Save**.
 
@@ -204,4 +207,11 @@ This section describes how to disable subnet private endpoint policies by using
 
 ## Next steps
 
-- To learn more, see [What is a private endpoint?](private-endpoint-overview.md).
+In this how-to guide, you enabled and disabled network policies for private endpoints in an Azure virtual network. You learned how to use the Azure portal, Azure PowerShell, Azure CLI, and Azure Resource Manager templates to manage network policies for private endpoints.
+
+
+For more information about the services that support private endpoints, see:
+> [!div class="nextstepaction"]
+> [What is a private endpoint?](private-endpoint-overview.md)
+
+
diff --git a/articles/private-link/private-endpoint-dns-integration.md b/articles/private-link/private-endpoint-dns-integration.md
@@ -5,7 +5,7 @@ services: private-link
 author: abell
 ms.service: azure-private-link
 ms.topic: conceptual
-ms.date: 05/02/2024
+ms.date: 12/03/2024
 ms.author: abell
 ms.custom: fasttrack-edit
 ---
@@ -51,7 +51,7 @@ To configure properly, you need the following resources:
 
 The following screenshot illustrates the DNS resolution sequence from virtual network workloads using the private DNS zone:
 
-:::image type="content" source="media/private-endpoint-dns/single-vnet-azure-dns.png" alt-text="Diagram of single virtual network and Azure-provided DNS.":::
+:::image type="content" source="media/private-endpoint-dns/single-vnet-azure-dns.png" alt-text="Diagram of single virtual network and Azure-provided DNS." lightbox="media/private-endpoint-dns/single-vnet-azure-dns.png"::: 
 
 ## <a name="virtual-network-workloads-without-custom-dns-server"></a> Peered virtual network workloads without Azure Private Resolver
 
@@ -64,7 +64,7 @@ You can extend this model to peered virtual networks associated to the same priv
 
 In this scenario, there's a [hub and spoke](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke) networking topology. The spoke networks share a private endpoint. The spoke virtual networks are linked to the same private DNS zone.
 
-:::image type="content" source="media/private-endpoint-dns/hub-and-spoke-azure-dns.png" alt-text="Diagram of hub and spoke with Azure-provided DNS.":::
+:::image type="content" source="media/private-endpoint-dns/hub-and-spoke-azure-dns.png" alt-text="Diagram of hub and spoke with Azure-provided DNS." lightbox="media/private-endpoint-dns/hub-and-spoke-azure-dns.png"::: 
 
 ## Azure Private Resolver for on-premises workloads
 
@@ -88,7 +88,9 @@ The following resources are required for a proper configuration:
 
 The following diagram illustrates the DNS resolution sequence from an on-premises network. The configuration uses a Private Resolver deployed in Azure. The resolution is made by a private DNS zone [linked to a virtual network](../dns/private-dns-virtual-network-links.md):
 
-:::image type="content" source="media/private-endpoint-dns/on-premises-using-azure-dns.png" alt-text="Diagram of on-premises using Azure DNS.":::
+:::image type="content" source="media/private-endpoint-dns/on-premises-using-azure-dns.png" alt-text="Diagram of on-premises using Azure private DNS zone." lightbox="media/private-endpoint-dns/on-premises-using-azure-dns.png"::: 
+
+
 
 ## <a name="on-premises-workloads-using-a-dns-forwarder"></a> Azure Private Resolver with on-premises DNS forwarder
 
@@ -116,7 +118,7 @@ The following diagram illustrates the DNS resolution from an on-premises network
 > [!IMPORTANT]
 > The conditional forwarding must be made to the recommended [public DNS zone forwarder](private-endpoint-dns.md). For example: `database.windows.net` instead of **privatelink**.database.windows.net.
 
-:::image type="content" source="media/private-endpoint-dns/on-premises-forwarding-to-azure.png" alt-text="Diagram of on-premises forwarding to Azure DNS.":::
+:::image type="content" source="media/private-endpoint-dns/on-premises-forwarding-to-azure.png" alt-text="Diagram of on-premises forwarding to Azure DNS." lightbox="media/private-endpoint-dns/on-premises-forwarding-to-azure.png"::: 
 
 ## <a name="virtual-network-and-on-premises-workloads-using-a-dns-forwarder"></a> Azure Private Resolver for virtual network and on-premises workloads
 
@@ -150,7 +152,7 @@ The following diagram shows the DNS resolution for both networks, on-prem
 
 The resolution is made by a private DNS zone [linked to a virtual network](../dns/private-dns-virtual-network-links.md):
 
-:::image type="content" source="media/private-endpoint-dns/hybrid-scenario.png" alt-text="Diagram of hybrid scenario.":::
+:::image type="content" source="media/private-endpoint-dns/hybrid-scenario.png" alt-text="Diagram of hybrid scenario with private DNS zone." lightbox="media/private-endpoint-dns/hybrid-scenario.png"::: 
 
 ## Private DNS zone group
 
diff --git a/articles/private-link/private-endpoint-overview.md b/articles/private-link/private-endpoint-overview.md
@@ -138,7 +138,7 @@ A private-link resource is the destination target of a specified private endpoin
 
 When you use private endpoints, traffic is secured to a private-link resource. The platform validates network connections, allowing only those that reach the specified private-link resource. To access more subresources within the same Azure service, more private endpoints with corresponding targets are required. In the case of Azure Storage, for instance, you would need separate private endpoints to access the *file* and *blob* subresources.
 
-Private endpoints provide a privately accessible IP address for the Azure service, but do not necessarily restrict public network access to it. All other Azure services require additional [access controls](../event-hubs/event-hubs-ip-filtering.md), however. These controls provide an extra network security layer to your resources, providing protection that helps prevent access to the Azure service associated with the private-link resource.
+Private endpoints provide a privately accessible IP address for the Azure service, but don't necessarily restrict public network access to it. All other Azure services require additional [access controls](../event-hubs/event-hubs-ip-filtering.md), however. These controls provide an extra network security layer to your resources, providing protection that helps prevent access to the Azure service associated with the private-link resource.
 
 Private endpoints support network policies. Network policies enable support for Network Security Groups (NSG), User Defined Routes (UDR), and Application Security Groups (ASG). For more information about enabling network policies for a private endpoint, see [Manage network policies for private endpoints](disable-private-endpoint-network-policy.md). To use an ASG with a private endpoint, see [Configure an application security group (ASG) with a private endpoint](configure-asg-private-endpoint.md).
 
@@ -152,8 +152,8 @@ You can connect to a private-link resource by using the following connection app
 
 - **Manually request**: Use this method when you don't have the required permissions and want to request access. An approval workflow is initiated. The private endpoint and later private-endpoint connections are created in a *Pending* state. The private-link resource owner is responsible to approve the connection. After it's approved, the private endpoint is enabled to send traffic normally, as shown in the following approval workflow diagram:  
 
-![Diagram of the workflow approval process.](media/private-endpoint-overview/private-link-paas-workflow.png)
- 
+:::image type="content" source="media/private-endpoint-overview/private-link-paas-workflow.png" alt-text="Diagram of the workflow approval process." lightbox="media/private-endpoint-overview/private-link-paas-workflow.png":::
+
 Over a private-endpoint connection, a private-link resource owner can: 
 
 - Review all private-endpoint connection details. 
diff --git a/articles/private-link/private-link-faq.yml b/articles/private-link/private-link-faq.yml
@@ -6,7 +6,7 @@ metadata:
   author: abell
   ms.service: azure-private-link
   ms.topic: faq
-  ms.date: 03/18/2024
+  ms.date: 12/04/2024
   ms.author: abell
 title: Azure Private Link frequently asked questions (FAQ)
 summary: |
@@ -29,7 +29,7 @@ sections:
           What is the difference between Service Endpoints and Private Endpoints?
         answer: |
           - Private Endpoints grant network access to specific resources behind a given service providing granular segmentation. Traffic can reach the service resource from on premises without using public endpoints.
-          - A Service Endpoint remains a publicly routable IP address.  A Private Endpoint is a private IP in the address space of the virtual network where the private endpoint is configured.
+          - A Service Endpoint remains a publicly routable IP address. A Private Endpoint is a private IP in the address space of the virtual network where the private endpoint is configured.
           
       - question: |
           What is the relationship between Private Link Service and Private Endpoint?
@@ -52,19 +52,19 @@ sections:
   - name: Private Endpoint
     questions:
       - question: |
-          Can I create multiple Private Endpoints in same VNet? Can they connect to different services? 
+          Can I create multiple Private Endpoints in same virtual network? Can they connect to different services? 
         answer: |
-          Yes. You can have multiple Private Endpoints in same VNet or subnet. They can connect to different services.  
+          Yes. You can have multiple Private Endpoints in same virtual network or subnet. They can connect to different services.  
 
       - question: |
            Can we link multiple private DNS zones with the same name? 
         answer: |
-           No, creating multiple zones with the same name for a single virtual network is not supported.  
+           No, creating multiple zones with the same name for a single virtual network isn't supported.  
 
       - question: |
           Do I require a dedicated subnet for Private Endpoints? 
         answer: |
-          No. You don't require a dedicated subnet for Private Endpoints. You can choose a Private Endpoint IP from any subnet from the VNet where your service is deployed.  
+          No. You don't require a dedicated subnet for Private Endpoints. You can choose a Private Endpoint IP from any subnet from the virtual network where your service is deployed.  
 
       - question: |
           Can a private endpoint connect to Private Link services across Microsoft Entra tenants? 
@@ -99,7 +99,7 @@ sections:
   - name: Private Link Service
     questions:
       - question: |
-          What are the pre-requisites for creating a Private Link Service? 
+          What are the prerequisites for creating a Private Link Service? 
         answer: |
           Your service backends should be in a Virtual Network and behind a Standard Load Balancer.
 
@@ -114,8 +114,8 @@ sections:
       - question: |
           What is the NAT (Network Address Translation) IP Configuration used in Private Link Service? How can I scale in terms of available ports and connections? 
         answer: |
-          - The NAT IP configuration ensures the source (consumer) and destination (service provider) address space don't have IP conflicts. The configuration provides source NAT for the private link traffic for the destination. The NAT IP address will show up as source IP for all packets received by your service and destination IP for all packets sent by your service.  NAT IP can be chosen from any subnet in a service provider's Virtual Network.
-          - Each NAT IP provides 64k TCP connections (64k ports) per VM behind the Standard Load Balancer. In order to scale and add more connections, you can either add new NAT IPs or add more VMs behind the Standard Load Balancer. Doing so will scale the port availability and allow for more connections. Connections will be distributed across NAT IPs and VMs behind the Standard Load Balancer.
+          - The NAT IP configuration ensures the source (consumer) and destination (service provider) address space don't have IP conflicts. The configuration provides source NAT for the private link traffic for the destination. The NAT IP address shows up as source IP for all packets received by your service and destination IP for all packets sent by your service. NAT IP can be chosen from any subnet in a service provider's Virtual Network.
+          - Each NAT IP provides 64k TCP connections (64k ports) per VM behind the Standard Load Balancer. In order to scale and add more connections, you can either add new NAT IPs or add more VMs behind the Standard Load Balancer. Doing so scales the port availability and allow for more connections. Connections are distributed across NAT IPs and VMs behind the Standard Load Balancer.
           
       - question: |
           Can I connect my service to multiple Private Endpoints?
@@ -139,12 +139,12 @@ sections:
       - question: |
           Is a dedicated subnet required for Private Link Service? 
         answer: |
-          No. A dedicated subnet isn't required for the Private Link Service. You can choose any subnet in your VNet where your service is deployed.   
+          No. A dedicated subnet isn't required for the Private Link Service. You can choose any subnet in your virtual network where your service is deployed.   
 
       - question: |
           I'm a service provider using Azure Private Link. Do I need to make sure all my customers have unique IP space and don’t overlap with my IP space? 
         answer: |
-          No. Azure Private Link provides this functionality for you. You aren't required to have non-overlapping address space with your customer's address space. 
+          No. Azure Private Link provides this functionality for you. You aren't required to have nonoverlapping address space with your customer's address space. 
 
 additionalContent: |
 
diff --git a/articles/private-link/private-link-overview.md b/articles/private-link/private-link-overview.md
diff --git a/articles/private-link/rbac-permissions.md b/articles/private-link/rbac-permissions.md
diff --git a/articles/private-link/tutorial-private-endpoint-sql-portal.md b/articles/private-link/tutorial-private-endpoint-sql-portal.md
diff --git a/articles/private-link/tutorial-private-endpoint-storage-portal.md b/articles/private-link/tutorial-private-endpoint-storage-portal.md
