Skip to content

Commit d72deda

Browse files
authored
Update private-link-service.md
Updating UI to represent current UI. Change To allow trusted services to access your namespace, switch to the Firewalls and Virtual networks tab on the Networking page, and select Yes for Allow trusted Microsoft services to bypass this firewall?. to To allow trusted services to access your namespace, switch to the Public Access tab on the Networking page, and select Yes for Allow trusted Microsoft services to bypass this firewall?.
1 parent e556acd commit d72deda

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/event-hubs/private-link-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ If you already have an Event Hubs namespace, you can create a private link conne
8888

8989
[!INCLUDE [event-hubs-trusted-services](./includes/event-hubs-trusted-services.md)]
9090

91-
To allow trusted services to access your namespace, switch to the **Firewalls and Virtual networks** tab on the **Networking** page, and select **Yes** for **Allow trusted Microsoft services to bypass this firewall?**.
91+
To allow trusted services to access your namespace, switch to the **Public Access** tab on the **Networking** page, and select **Yes** for **Allow trusted Microsoft services to bypass this firewall?**.
9292

9393
## Add a private endpoint using PowerShell
9494
The following example shows how to use Azure PowerShell to create a private endpoint connection. It doesn't create a dedicated cluster for you. Follow steps in [this article](event-hubs-dedicated-cluster-create-portal.md) to create a dedicated Event Hubs cluster.

0 commit comments

Comments
 (0)