Skip to content

Commit 5c7e14a

Browse files
committed
Web PubSub: Add key vault RBAC content
1 parent 7640cbc commit 5c7e14a

File tree

7 files changed

+33
-1
lines changed

7 files changed

+33
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ If you're using Azure role-based access control as Key Vault permission model:
6161
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-perm-model-rbac.png" :::
6262

6363
1. Go to your Key Vault resource.
64-
1. In the menu pane, select **Access control (IAM) **.
64+
1. In the menu pane, select **Access control (IAM)**.
6565
1. Click **Add**. Select **Add role assignment**.
6666

6767
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-iam.png" :::

articles/azure-web-pubsub/howto-custom-domain.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,14 @@ Azure Web PubSub Service uses Managed Identity to access your Key Vault. In orde
3232

3333
:::image type="content" alt-text="Screenshot of enabling managed identity." source="media\howto-custom-domain\portal-identity.png" :::
3434

35+
Depending on how you configure your Key Vault permission model, you may need to grant permissions at different places.
36+
37+
#### [Vault access policy](#tab/vault-access-policy)
38+
39+
If you're using Key Vault built-in access policy as Key Vault permission model as follows:
40+
41+
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-perm-model-access-policy.png" :::
42+
3543
1. Go to your Key Vault resource.
3644
1. In the menu pane, select **Access configuration**. Click **Go to access policies**.
3745
1. Click **Create**. Select **Secret Get** permission and **Certificate Get** permission. Click **Next**.
@@ -45,6 +53,30 @@ Azure Web PubSub Service uses Managed Identity to access your Key Vault. In orde
4553
1. Skip **Application (optional)**. Click **Next**.
4654
1. In **Review + create**, click **Create**.
4755

56+
#### [Azure role-based access control](#tab/azure-rbac)
57+
58+
If you're using Azure role-based access control as Key Vault permission model:
59+
60+
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-perm-model-rbac.png" :::
61+
62+
1. Go to your Key Vault resource.
63+
1. In the menu pane, select **Access control (IAM)**.
64+
1. Click **Add**. Select **Add role assignment**.
65+
66+
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-iam.png" :::
67+
68+
1. Under the **Role** tab, select **Key Vault Secrets User**. Click **Next**.
69+
70+
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-role.png" :::
71+
72+
1. Under the **Members** tab, select **Managed identity**. 1. Search for the Azure Web PubSub Service resource name or the user assigned identity name. Click **Next**.
73+
74+
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-members.png" :::
75+
76+
1. Click **Review + assign**.
77+
78+
-----
79+
4880
### Step 2: Create a custom certificate
4981

5082
1. In the Azure portal, go to your Azure Web PubSub Service resource.
85.2 KB
Loading
35.6 KB
Loading
35.2 KB
Loading
41.6 KB
Loading
53.2 KB
Loading

0 commit comments

Comments
 (0)