Merge pull request #212639 from ArchangelSDY/kv-shrpe

Add accessing private keyvault doc

Author: BCS2022

articles/azure-signalr/TOC.yml

@@ -119,6 +119,8 @@
       href: howto-network-access-control.md
     - name: Secure outbound traffic through Shared Private Endpoints
       href: howto-shared-private-endpoints.md
+    - name: Access Key Vault in private network through Shared Private Endpoints
+      href: howto-shared-private-endpoints-key-vault.md
     - name: Use managed identity
       href: howto-use-managed-identity.md
     - name: Authorize from Azure Application

articles/azure-signalr/howto-custom-domain.md

@@ -176,6 +176,15 @@ $ curl -vvv https://contoso.example.com/api/health
 
 It should return `200` status code without any certificate error.
 
+
+## Key Vault in private network
+
+If you have configured [Private Endpoint](../private-link/private-endpoint-overview.md) to your Key Vault, Azure SignalR Service cannot access the Key Vault via public network. You need to set up a [Shared Private Endpoint](./howto-shared-private-endpoints-key-vault.md) to let Azure SignalR Service access your Key Vault via private network.
+
+After you create a Shared Private Endpoint, you can create a custom certificate as usual. **You don't have to change the domain in Key Vault URI**. For example, if your Key Vault base URI is `https://contoso.vault.azure.net`, you still use this URI to configure custom certificate.
+
+You don't have to explicitly allow Azure SignalR Service IPs in Key Vault firewall settings. For more info, see [Key Vault private link diagnostics](../key-vault/general/private-link-diagnostics.md).
+
 ## Next steps
 
 + [How to enable managed identity for Azure SignalR Service](howto-use-managed-identity.md)

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

@@ -0,0 +1,181 @@
+---
+title: Access Key Vault in private network through Shared Private Endpoints
+titleSuffix: Azure SignalR Service
+description: How to access key vault in private network through Shared Private Endpoints
+services: signalr
+author: ArchangelSDY
+ms.service: signalr
+ms.topic: article
+ms.date: 09/23/2022
+ms.author: dayshen
+---
+
+# Access Key Vault in private network through Shared Private Endpoints
+
+Azure SignalR Service can access your Key Vault in private network through Shared Private Endpoints. In this way you don't have to expose your Key Vault on public network.
+
+   :::image type="content" alt-text="Diagram showing architecture of shared private endpoint." source="media\howto-shared-private-endpoints-key-vault\shared-private-endpoint-overview.png" :::
+
+## Shared Private Link Resources Management
+
+Private endpoints of secured resources that are created through Azure SignalR Service APIs are referred to as *shared private link resources*. This is because you're "sharing" access to a resource, such as an Azure 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 Azure SignalR Service execution environment and aren't directly visible to you.
+
+> [!NOTE]
+> The examples in this article are based on the following assumptions:
+> * The resource ID of this Azure SignalR Service is _/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.SignalRService/signalr/contoso-signalr_.
+> * The resource ID of Azure Key Vault is _/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.KeyVault/vaults/contoso-kv_.
+
+The rest of the examples show how the *contoso-signalr* service can be configured so that its outbound calls to Key Vault go through a private endpoint rather than public network.
+
+### Step 1: Create a shared private link resource to the Key Vault
+
+#### [Azure portal](#tab/azure-portal)
+
+1. In the Azure portal, go to your Azure SignalR Service resource.
+1. In the menu pane, select **Networking**. Switch to **Private access** tab.
+1. Click **Add shared private endpoint**.
+
+   :::image type="content" alt-text="Screenshot of shared private endpoints management." source="media\howto-shared-private-endpoints-key-vault\portal-shared-private-endpoints-management.png" lightbox="media\howto-shared-private-endpoints-key-vault\portal-shared-private-endpoints-management.png" :::
+
+1. Fill in a name for the shared private endpoint.
+1. Select the target linked resource either by selecting from your owned resources or by filling a resource ID.
+1. Click **Add**.
+
+   :::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" :::
+
+1. The shared private endpoint resource will be in **Succeeded** provisioning state. The connection state is **Pending** approval at target resource side.
+
+   :::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" :::
+
+#### [Azure CLI](#tab/azure-cli)
+
+You can make the following API call with the [Azure CLI](/cli/azure/) to create a shared private link resource:
+
+```dotnetcli
+az rest --method put --uri https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.SignalRService/signalr/contoso-signalr/sharedPrivateLinkResources/kv-pe?api-version=2021-06-01-preview --body @create-pe.json
+```
+
+The contents of the *create-pe.json* file, which represent the request body to the API, are as follows:
+
+```json
+{
+      "name": "contoso-kv",
+      "properties": {
+        "privateLinkResourceId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.KeyVault/vaults/contoso-kv",
+        "groupId": "vault",
+        "requestMessage": "please approve"
+      }
+}
+```
+
+The process of creating an outbound private endpoint is a long-running (asynchronous) operation. As in all asynchronous Azure operations, the `PUT` call returns an `Azure-AsyncOperation` header value that looks like the following:
+
+```plaintext
+"Azure-AsyncOperation": "https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.SignalRService/signalr/contoso-signalr/operationStatuses/c0786383-8d5f-4554-8d17-f16fcf482fb2?api-version=2021-06-01-preview"
+```
+
+You can poll this URI periodically to obtain the status of the operation.
+
+If you're using the CLI, you can poll for the status by manually querying the `Azure-AsyncOperationHeader` value,
+
+```dotnetcli
+az rest --method get --uri https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.SignalRService/signalr/contoso-signalr/operationStatuses/c0786383-8d5f-4554-8d17-f16fcf482fb2?api-version=2021-06-01-preview
+```
+
+Wait until the status changes to "Succeeded" before proceeding to the next steps.
+
+-----
+
+### Step 2a: Approve the private endpoint connection for the Key Vault
+
+#### [Azure portal](#tab/azure-portal)
+
+1. In the Azure portal, select the **Networking** tab of your Key Vault and navigate 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.
+
+   :::image type="content" alt-text="Screenshot of the Azure portal, showing the Private endpoint connections pane." source="media\howto-shared-private-endpoints-key-vault\portal-key-vault-approve-private-endpoint.png" :::
+
+1. Select the private endpoint that Azure SignalR Service created. Click **Approve**.
+
+   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.
+
+   :::image type="content" alt-text="Screenshot of the Azure portal, showing an Approved status on the Private endpoint connections pane." source="media\howto-shared-private-endpoints-key-vault\portal-key-vault-approved-private-endpoint.png" :::
+
+#### [Azure CLI](#tab/azure-cli)
+
+1. List private endpoint connections.
+
+    ```dotnetcli
+    az network private-endpoint-connection list -n <key-vault-resource-name>  -g <key-vault-resource-group-name> --type 'Microsoft.KeyVault/vaults'
+    ```
+
+    There should be a pending private endpoint connection. Note down its ID.
+
+    ```json
+    [
+        {
+            "id": "<id>",
+            "location": "",
+            "name": "",
+            "properties": {
+                "privateLinkServiceConnectionState": {
+                    "actionRequired": "None",
+                    "description": "Please approve",
+                    "status": "Pending"
+               }
+            }
+        }
+    ]
+    ```
+
+1. Approve the private endpoint connection.
+
+    ```dotnetcli
+    az network private-endpoint-connection approve --id <private-endpoint-connection-id>
+    ```
+
+-----
+
+### Step 2b: Query the status of the shared private link resource
+
+It takes minutes for the approval to be propagated to Azure SignalR Service. You can check the state using either Azure portal or Azure CLI.
+
+#### [Azure portal](#tab/azure-portal)
+
+   :::image type="content" alt-text="Screenshot of an approved shared private endpoint." source="media\howto-shared-private-endpoints-key-vault\portal-shared-private-endpoints-approved.png" lightbox="media\howto-shared-private-endpoints-key-vault\portal-shared-private-endpoints-approved.png" :::
+
+#### [Azure CLI](#tab/azure-cli)
+
+```dotnetcli
+az rest --method get --uri https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.SignalRService/signalr/contoso-signalr/sharedPrivateLinkResources/func-pe?api-version=2021-06-01-preview
+```
+
+This would return a JSON, where the connection state would show up as "status" under the "properties" section.
+
+```json
+{
+      "name": "contoso-kv",
+      "properties": {
+        "privateLinkResourceId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.KeyVault/vaults/contoso-kv",
+        "groupId": "vaults",
+        "requestMessage": "please approve",
+        "status": "Approved",
+        "provisioningState": "Succeeded"
+      }
+}
+
+```
+
+If the "Provisioning State" (`properties.provisioningState`) of the resource is `Succeeded` and "Connection State" (`properties.status`) is `Approved`, it means that the shared private link resource is functional and Azure SignalR Service can communicate over the private endpoint.
+
+-----
+
+At this point, the private endpoint between Azure SignalR Service and Azure Key Vault is established.
+
+Now you can configure features like custom domain as usual. **You don't have to use a special domain for Key Vault**. DNS resolution is automatically handled by Azure SignalR Service.
+
+## Next steps
+
+Learn more:
+
++ [What are private endpoints?](../private-link/private-endpoint-overview.md)
++ [Configure custom domain](howto-custom-domain.md)

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

@@ -32,7 +32,7 @@ Private endpoints of secured resources that are created through Azure SignalR Se
 > [!NOTE]
 > The examples in this article are based on the following assumptions:
 > * The resource ID of this Azure SignalR Service is _/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.SignalRService/signalr/contoso-signalr_.
-> * The resource ID of upstream Azure Function is _/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.Web/sites/contoso-func.
+> * The resource ID of upstream Azure Function is _/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/contoso/providers/Microsoft.Web/sites/contoso-func_.
 
 The rest of the examples show how the *contoso-signalr* service can be configured so that its upstream calls to function go through a private endpoint rather than public network.