Skip to content

Commit aff7781

Browse files
authored
small changes
1 parent e802774 commit aff7781

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In addition to the default domain provided with Azure SignalR Service, you can a
2121
- An Azure resource group.
2222
- An Azure SignalR Service resource.
2323
- 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).
2525
- An Azure DNS zone (optional).
2626

2727
## Add a custom certificate
@@ -82,7 +82,7 @@ If you're using **Vault access policy** as your key vault permission model, foll
8282

8383
#### [Azure role-based access control](#tab/azure-rbac)
8484

85-
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.
8686

8787
:::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" :::
8888

@@ -92,7 +92,7 @@ When you use the Azure role-based access control permission model, follow this p
9292

9393
:::image type="content" alt-text="Screenshot that shows the IAM Add role assignment option." source="media/howto-custom-domain/portal-key-vault-iam.png" :::
9494

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**.
9696

9797
:::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" :::
9898

0 commit comments

Comments
 (0)