Skip to content

Commit 9954d0c

Browse files
committed
UUF issue | Fix steps in portal | Acrolinx | SEO | Auto-format markdown
1 parent 7ab2768 commit 9954d0c

File tree

1 file changed

+27
-21
lines changed

1 file changed

+27
-21
lines changed

articles/application-gateway/private-link-configure.md

Lines changed: 27 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,25 @@
11
---
22
title: Configure Azure Application Gateway Private Link
3-
description: This article shows you how to configure Application Gateway Private Link.
3+
description: Learn how-to to set up Azure Application Gateway Private Link using the Azure portal, PowerShell, or CLI.
4+
#customer intent: As a network administrator, I want to configure Azure Application Gateway Private Link so that I can securely connect workloads across VNets and subscriptions.
45
services: application-gateway
56
author: mbender-ms
67
ms.service: azure-application-gateway
7-
ms.custom: devx-track-azurecli, devx-track-azurepowershell
8+
ms.custom:
9+
- devx-track-azurecli, devx-track-azurepowershell
10+
- ai-gen-docs-bap
11+
- ai-gen-description
12+
- ai-seo-date:06/16/2025
813
ms.topic: how-to
9-
ms.date: 06/06/2022
14+
ms.date: 06/16/2025
1015
ms.author: mbender
1116
---
1217

1318
# Configure Azure Application Gateway Private Link
1419

1520
Application Gateway Private Link allows you to connect your workloads over a private connection spanning across VNets and subscriptions. For more information, see [Application Gateway Private Link](private-link.md).
1621

17-
:::image type="content" source="media/private-link/private-link.png" alt-text="Diagram showing Application Gateway Private Link":::
22+
:::image type="content" source="media/private-link/private-link.png" alt-text="Screenshot of diagram showing Application Gateway Private Link.":::
1823

1924
## Configuration options
2025

@@ -24,9 +29,9 @@ Application Gateway Private Link can be configured via multiple options, such as
2429

2530
**Define a subnet for Private Link Configuration**
2631

27-
To enable Private Link Configuration, a subnet, different from the Application Gateway subnet, is required for the private link IP configuration. Private Link must use a subnet that doesn't contain any Application Gateways. Subnet sizing is determined by the number of connections required for your deployment. Each IP address allocated to this subnet ensures 64-K concurrent TCP connections that can be established via Private Link at single point in time. Allocate more IP addresses to allow more connections via Private Link. For example: `n * 64K`; where `n` is the number of IP addresses being provisioned.
32+
To enable Private Link Configuration, a subnet, different from the Application Gateway subnet, is required for the private link IP configuration. Private Link must use a subnet that doesn't contain any Application Gateways. Subnet sizing is determined by the number of connections required for your deployment. Each IP address allocated to this subnet ensures 64-K concurrent TCP connections that can be established via Private Link at single point in time. Allocate more IP addresses to allow more connections via Private Link. For example: `n * 64K`; where `n` is the number of IP addresses being provisioned.
2833

29-
> [!Note]
34+
> [!NOTE]
3035
> The maximum number of IP addresses per private link configuration is eight. Only dynamic allocation is supported.
3136
3237
Complete the following steps to create a new subnet:
@@ -35,41 +40,42 @@ Complete the following steps to create a new subnet:
3540

3641
**Configure Private Link**
3742

38-
The Private link configuration defines the infrastructure used by Application Gateway to enable connections from Private Endpoints. While creating the Private Link configuration ensure a listener is actively utilizing the respected frontend IP configuration.Complete the following steps to create the Private Link configuration:
43+
The Private link configuration defines the infrastructure used by Application Gateway to enable connections from Private Endpoints. While creating the Private Link configuration ensure a listener is actively utilizing the respected frontend IP configuration. Complete the following steps to create the Private Link configuration:
3944

4045
1. Go to the [Azure portal](https://portal.azure.com)
4146
1. Search for and select **Application Gateways**.
4247
1. Select the name of the application gateway you want to enable private link.
43-
1. Select **Private link**
48+
1. Select **Private link** then select **+ Add**.
4449
1. Configure the following items:
4550

4651
- **Name**: The name of the private link configuration.
4752
- **Private link subnet**: The subnet IP addresses should be consumed from.
4853
- **Frontend IP Configuration**: The frontend IP address that private link should forward traffic to on Application Gateway.
4954
- **Private IP address settings**: specify at least one IP address
55+
5056
1. Select **Add**.
51-
1. Within your **Application Gateways** properties blade, obtain and make a note of the **Resource ID**, this is required if you are setting up a Private Endpoint within a different Microsoft Entra tenant.
57+
1. Within your Application Gateway's settings, obtain and make a note of the **Resource ID**. This is required if you're setting up a Private Endpoint within a different Microsoft Entra tenant.
5258

5359
**Configure Private Endpoint**
5460

5561
A private endpoint is a network interface that uses a private IP address from the virtual network containing clients wishing to connect to your Application Gateway. Each of the clients uses the private IP address of the Private Endpoint to tunnel traffic to the Application Gateway. To create a private endpoint, complete the following steps:
5662

5763
1. Select the **Private endpoint connections** tab.
58-
1. Select **Create**.
59-
1. On the **Basics** tab, configure a resource group, name, and region for the Private Endpoint. Select **Next**.
60-
1. On the **Resource** tab, select **Next**.
61-
1. On the **Virtual Network** tab, configure a virtual network and subnet where the private endpoint network interface should be provisioned to. Select **Next**.
62-
1. On the **Tags** tab, optionally configure resource tags. Select **Next**.
63-
1. Select **Create**.
64-
65-
> [!Note]
64+
1. Select **+ Private endpoint**.
65+
1. On the **Basics** tab, configure a resource group, name, and region for the Private Endpoint. Select **Next: Resource >**.
66+
1. On the **Resource** tab, select **Next: Virtual Network >**.
67+
1. On the **Virtual Network** tab, configure a virtual network and subnet where the private endpoint network interface should be provisioned to. Select **Next: DNS >**.
68+
1. On the **Tags** tab, optionally configure resource tags. Select **Next: Tags >**.
69+
1. Select **Next: Review + create >** then select **Create**.
70+
71+
> [!NOTE]
6672
> If the public or private IP configuration resource is missing when trying to select a _Target sub-resource_ on the _Resource_ tab of private endpoint creation, please ensure a listener is actively utilizing the respected frontend IP configuration. Frontend IP configurations without an associated listener won't be shown as a _Target sub-resource_.
6773
68-
> [!Note]
74+
> [!NOTE]
6975
> If you're provisioning a **Private Endpoint** from within another tenant, you will need to utilize the Azure Application Gateway Resource ID and the _Name_ of the Frontend IP configuration as the target sub-resource. For example, if I had a private IP associated to the Application Gateway and the Name listed in Frontend IP configuration of the portal for the private IP is _PrivateFrontendIp_, the target sub-resource value would be: _PrivateFrontendIp_.
7076
71-
> [!Note]
72-
> If you have to move a **Private Endpoint** to another subscription, you must first delete the existing **Private Endpoint** connection between the **Private Link** and **Private Endpoint**. Once this is completed, you have to re-create a new **Private Endpoint** connection in the new subscription to establish connection between **Private Link** and **Private Endpoint**.
77+
> [!NOTE]
78+
> If you have to move a **Private Endpoint** to another subscription, you must first delete the existing **Private Endpoint** connection between the **Private Link** and **Private Endpoint**. Once this is completed, you have to re-create a new **Private Endpoint** connection in the new subscription to establish connection between **Private Link** and **Private Endpoint**.
7379
7480

7581

@@ -199,4 +205,4 @@ A list of all Azure CLI references for Private Link Configuration on Application
199205

200206
## Next steps
201207

202-
- Learn about Azure Private Link: [What is Azure Private Link](../private-link/private-link-overview.md).
208+
- Learn about Azure Private Link: [What is Azure Private Link](../private-link/private-link-overview.md).

0 commit comments

Comments
 (0)