Skip to content

Commit 7640833

Browse files
committed
Address issues
1 parent 5c7e14a commit 7640833

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,9 @@ Depending on how you configure your Key Vault permission model, you may need to
3737

3838
#### [Vault access policy](#tab/vault-access-policy)
3939

40-
If you're using Key Vault built-in access policy as Key Vault permission model as follows:
40+
If you're using Key Vault built-in access policy as Key Vault permission model:
4141

42-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-perm-model-access-policy.png" :::
42+
:::image type="content" alt-text="Screenshot of built-in access policy selected as Key Vault permission model." source="media\howto-custom-domain\portal-key-vault-perm-model-access-policy.png" :::
4343

4444
1. Go to your Key Vault resource.
4545
1. In the menu pane, select **Access configuration**. Click **Go to access policies**.
@@ -58,7 +58,7 @@ If you're using Key Vault built-in access policy as Key Vault permission model a
5858

5959
If you're using Azure role-based access control as Key Vault permission model:
6060

61-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-perm-model-rbac.png" :::
61+
:::image type="content" alt-text="Screenshot of Azure RBAC selected as Key Vault permission model." source="media\howto-custom-domain\portal-key-vault-perm-model-rbac.png" :::
6262

6363
1. Go to your Key Vault resource.
6464
1. In the menu pane, select **Access control (IAM)**.
@@ -68,11 +68,11 @@ If you're using Azure role-based access control as Key Vault permission model:
6868

6969
1. Under the **Role** tab, select **Key Vault Secrets User**. Click **Next**.
7070

71-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-role.png" :::
71+
:::image type="content" alt-text="Screenshot of role tab when adding role assignment to Key Vault." source="media\howto-custom-domain\portal-key-vault-role.png" :::
7272

7373
1. Under the **Members** tab, select **Managed identity**. 1. Search for the Azure SignalR Service resource name or the user assigned identity name. Click **Next**.
7474

75-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-members.png" :::
75+
:::image type="content" alt-text="Screenshot of members tab when adding role assignment to Key Vault." source="media\howto-custom-domain\portal-key-vault-members.png" :::
7676

7777
1. Click **Review + assign**.
7878

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,9 @@ Depending on how you configure your Key Vault permission model, you may need to
3636

3737
#### [Vault access policy](#tab/vault-access-policy)
3838

39-
If you're using Key Vault built-in access policy as Key Vault permission model as follows:
39+
If you're using Key Vault built-in access policy as Key Vault permission model:
4040

41-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-perm-model-access-policy.png" :::
41+
:::image type="content" alt-text="Screenshot of built-in access policy selected as Key Vault permission model." source="media\howto-custom-domain\portal-key-vault-perm-model-access-policy.png" :::
4242

4343
1. Go to your Key Vault resource.
4444
1. In the menu pane, select **Access configuration**. Click **Go to access policies**.
@@ -57,7 +57,7 @@ If you're using Key Vault built-in access policy as Key Vault permission model a
5757

5858
If you're using Azure role-based access control as Key Vault permission model:
5959

60-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-perm-model-rbac.png" :::
60+
:::image type="content" alt-text="Screenshot of Azure RBAC selected as Key Vault permission model." source="media\howto-custom-domain\portal-key-vault-perm-model-rbac.png" :::
6161

6262
1. Go to your Key Vault resource.
6363
1. In the menu pane, select **Access control (IAM)**.
@@ -67,11 +67,11 @@ If you're using Azure role-based access control as Key Vault permission model:
6767

6868
1. Under the **Role** tab, select **Key Vault Secrets User**. Click **Next**.
6969

70-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-role.png" :::
70+
:::image type="content" alt-text="Screenshot of role tab when adding role assignment to Key Vault." source="media\howto-custom-domain\portal-key-vault-role.png" :::
7171

7272
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**.
7373

74-
:::image type="content" alt-text="Screenshot of Key Vault IAM." source="media\howto-custom-domain\portal-key-vault-members.png" :::
74+
:::image type="content" alt-text="Screenshot of members tab when adding role assignment to Key Vault." source="media\howto-custom-domain\portal-key-vault-members.png" :::
7575

7676
1. Click **Review + assign**.
7777

0 commit comments

Comments
 (0)