Skip to content

Commit 25f8327

Browse files
authored
Update howto-shared-private-endpoints-key-vault.md
1 parent dcea415 commit 25f8327

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/azure-signalr/howto-shared-private-endpoints-key-vault.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ The examples show how the *contoso-signalr* service can be configured so that it
4343

4444
:::image type="content" alt-text="Screenshot of adding a shared private endpoint." source="media\howto-shared-private-endpoints-key-vault\portal-shared-private-endpoints-add.png" :::
4545

46-
The shared private endpoint resource is now in a **Succeeded** provisioning state. The connection state is **Pending** approval at the target resource side.
46+
1. Confirm that the shared private endpoint resource is now in a **Succeeded** provisioning state. The connection state is **Pending** at the target resource side.
4747

4848
:::image type="content" alt-text="Screenshot of an added shared private endpoint." source="media\howto-shared-private-endpoints-key-vault\portal-shared-private-endpoints-added.png" lightbox="media\howto-shared-private-endpoints-key-vault\portal-shared-private-endpoints-added.png" :::
4949

@@ -90,13 +90,13 @@ Wait until the status changes to **Succeeded** before you proceed to the next st
9090

9191
### [Azure portal](#tab/azure-portal)
9292

93-
1. In the Azure portal, select the **Networking** tab for your key vault and go to **Private endpoint connections**. After the asynchronous operation has succeeded, there should be a request for a private endpoint connection with the request message from the previous API call.
94-
95-
:::image type="content" alt-text="Screenshot of the Azure portal that shows the pane for private endpoint connections." source="media\howto-shared-private-endpoints-key-vault\portal-key-vault-approve-private-endpoint.png" :::
93+
1. In the Azure portal, select the **Networking** tab for your key vault and go to **Private endpoint connections**. After the asynchronous operation has succeeded, there should be a request for a private endpoint connection with the request message from the previous API call.
9694

9795
1. Select the private endpoint that Azure SignalR Service created. Then select **Approve**.
9896

99-
Make sure that the private endpoint connection appears, as shown in the following screenshot. It could take one to two minutes for the status to be updated in the portal.
97+
:::image type="content" alt-text="Screenshot of the Azure portal that shows the pane for private endpoint connections." source="media\howto-shared-private-endpoints-key-vault\portal-key-vault-approve-private-endpoint.png" :::
98+
99+
1. Make sure that the private endpoint connection appears, as shown in the following screenshot. It could take one to two minutes for the status to be updated in the portal.
100100

101101
:::image type="content" alt-text="Screenshot of the Azure portal that shows an Approved status on the pane for private endpoint connections." source="media\howto-shared-private-endpoints-key-vault\portal-key-vault-approved-private-endpoint.png" :::
102102

@@ -127,7 +127,7 @@ Wait until the status changes to **Succeeded** before you proceed to the next st
127127
]
128128
```
129129
130-
1. Approve the private endpoint connection.
130+
1. Approve the private endpoint connection:
131131
132132
```dotnetcli
133133
az network private-endpoint-connection approve --id <private-endpoint-connection-id>

0 commit comments

Comments
 (0)