Skip to content

Commit 66dd005

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

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Azure SignalR Service can access your Azure Key Vault instance in a private netw
1616

1717
:::image type="content" alt-text="Diagram that shows the architecture of a shared private endpoint." source="media\howto-shared-private-endpoints-key-vault\shared-private-endpoint-overview.png" :::
1818

19-
## Resource management through a shared private link
19+
## Management of shared private link resources
2020

2121
Private endpoints of secured resources that are created through Azure SignalR Service APIs are called *shared private link resources*. This is because you're "sharing" access to a resource, such a key vault, that has been integrated with the [Azure Private Link service](https://azure.microsoft.com/services/private-link/). These private endpoints are created inside an Azure SignalR Service execution environment and aren't directly visible to you.
2222

0 commit comments

Comments
 (0)