You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-signalr/howto-custom-domain.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ In addition to the default domain provided with Azure SignalR Service, you can a
21
21
- An Azure resource group.
22
22
- An Azure SignalR Service resource.
23
23
- An Azure Key Vault instance.
24
-
- A custom domain TLS/SSL certificate stored in your Key Vault instance. For more information, see [Get started with Key Vault certificates](/azure/key-vault/certificates/certificate-scenarios)
24
+
- A custom domain TLS/SSL certificate stored in your Key Vault instance. For more information, see [Get started with Key Vault certificates](/azure/key-vault/certificates/certificate-scenarios).
25
25
- An Azure DNS zone (optional).
26
26
27
27
## Add a custom certificate
@@ -82,7 +82,7 @@ If you're using **Vault access policy** as your key vault permission model, foll
When you use the Azure role-based access control permission model, follow this procedure to assign a role to the Azure SignalR Service managed identity. To complete this procedure, you must be a member of the [Azure built-in Owner](~/articles/role-based-access-control/built-in-roles.md#owner) role.
85
+
When you use Azure role-based access control as your permission model, follow this procedure to assign a role to the Azure SignalR Service managed identity. To complete this procedure, you must be a member of the [Azure built-in Owner](~/articles/role-based-access-control/built-in-roles.md#owner) role.
86
86
87
87
:::image type="content" alt-text="Screenshot that shows Azure role-based access control selected as the vault permission model." source="media/howto-custom-domain/portal-key-vault-perm-model-rbac.png" :::
88
88
@@ -92,7 +92,7 @@ When you use the Azure role-based access control permission model, follow this p
92
92
93
93
:::image type="content" alt-text="Screenshot that shows the IAM Add role assignment option." source="media/howto-custom-domain/portal-key-vault-iam.png" :::
94
94
95
-
1. On the **Role** tab, select **Key Vault Secrets User** and select **Next**.
95
+
1. On the **Role** tab, select **Key Vault Secrets User** and then select **Next**.
96
96
97
97
:::image type="content" alt-text="Screenshot that shows the Role tab when you add a role assignment to Key Vault." source="media/howto-custom-domain/portal-key-vault-role.png" :::
0 commit comments