You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-bus-messaging/private-link-service.md
+22-28Lines changed: 22 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Integrate Azure Service Bus with Azure Private Link Service
3
3
description: Learn how to integrate Azure Service Bus with Azure Private Link Service
4
4
author: spelluru
5
5
ms.author: spelluru
6
-
ms.date: 01/04/2022
6
+
ms.date: 08/26/2022
7
7
ms.topic: article
8
8
ms.custom: devx-track-azurepowershell
9
9
---
@@ -70,36 +70,30 @@ If you already have an existing namespace, you can create a private endpoint by
70
70
1. Select the **Azure subscription** in which you want to create the private endpoint.
71
71
2. Select the **resource group** for the private endpoint resource.
72
72
3. Enter a **name** for the private endpoint.
73
-
5. Select a **region** for the private endpoint. Your private endpoint must be in the same region as your virtual network, but can be in a different region from the private link resource that you are connecting to.
74
-
6. Select **Next: Resource >** button at the bottom of the page.
2. If you select **Connect to an Azure resource by resource ID or alias**, follow these steps:
87
-
1. Enter the **resource ID** or **alias**. It can be the resource ID or alias that someone has shared with you. The easiest way to get the resource ID is to navigate to the Service Bus namespace in the Azure portal and copy the portion of URI starting from `/subscriptions/`. See the following image for an example.
88
-
2. For **Target sub-resource**, enter **namespace**. It's the type of the sub-resource that your private endpoint can access.
89
-
3. (optional) Enter a **request message**. The resource owner sees this message while managing private endpoint connection.
90
-
4. Then, select **Next: Configuration >** button at the bottom of the page.
91
-
92
-

93
-
9. On the **Configuration** page, you select the subnet in a virtual network to where you want to deploy the private endpoint.
73
+
1. Enter a **name for the network interface**.
74
+
1. Select a **region** for the private endpoint. Your private endpoint must be in the same region as your virtual network, but can be in a different region from the private link resource that you are connecting to.
75
+
1. Select **Next: Resource >** button at the bottom of the page.
76
+
77
+
:::image type="content" source="./media/private-link-service/create-private-endpoint-basics-page.png" alt-text="Screenshot showing the Basics page of the Create private endpoint wizard.":::
78
+
8. On the **Resource** page, review settings, and select **Next: Virtual Network** at the bottom of the page.
79
+
80
+
:::image type="content" source="./media/private-link-service/create-private-endpoint-resource-page.png" alt-text="Screenshot showing the Resource page of the Create private endpoint wizard.":::
81
+
9. On the **Virtual Network** page, you select the subnet in a virtual network to where you want to deploy the private endpoint.
94
82
1. Select a **virtual network**. Only virtual networks in the currently selected subscription and location are listed in the drop-down list.
95
83
2. Select a **subnet** in the virtual network you selected.
96
-
3. Select **Next: Tags >** button at the bottom of the page.
84
+
1. Notice that the **network policy for private endpoints** is disabled. If you want to enable it, select **edit**, update the setting, and select **Save**.
85
+
1. For **Private IP configuration**, by default, **Dynamically allocate IP address** option is selected. If you want to assign a static IP address, select **Statically allocate IP address***.
86
+
1. For **Application security group**, select an existing application security group or create one that's to be associated with the private endpoint.
87
+
1. Select **Next: DNS >** button at the bottom of the page.
88
+
89
+
:::image type="content" source="./media/private-link-service/create-private-endpoint-configuration-page.png" alt-text="Screenshot showing the Virtual Network page of the Create private endpoint wizard.":::
90
+
10. On the **DNS** page, select whether you want the private endpoint to be integrated with a private DNS zone, and then select **Next: Tags**.
10. On the **Tags** page, create any tags (names and values) that you want to associate with the private endpoint resource. Then, select **Review + create** button at the bottom of the page.
100
-
11. On the **Review + create**, review all the settings, and select **Create** to create the private endpoint.
92
+
:::image type="content" source="./media/private-link-service/create-private-endpoint-dns-page.png" alt-text="Screenshot showing the DNS page of the Create private endpoint wizard.":::
93
+
1. On the **Tags** page, create any tags (names and values) that you want to associate with the private endpoint resource. Then, select **Review + create** button at the bottom of the page.
94
+
1. On the **Review + create**, review all the settings, and select **Create** to create the private endpoint.
101
95
102
-

96
+
:::image type="content" source="./media/private-link-service/create-private-endpoint-review-create-page.png" alt-text="Screenshot showing the Review and Create page of the Create private endpoint wizard.":::
103
97
12. Confirm that the private endpoint is created. If you are the owner of the resource and had selected **Connect to an Azure resource in my directory** option for the **Connection method**, the endpoint connection should be **auto-approved**. If it's in the **pending** state, see the [Manage private endpoints using Azure portal](#manage-private-endpoints-using-azure-portal) section.
0 commit comments