Skip to content

Commit 12f169c

Browse files
Update concept-trusted-signing-resources-roles.md
1 parent ff6ab3a commit 12f169c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/trusted-signing/concept-trusted-signing-resources-roles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ In the below example structure, notice that an Azure Subscription has a Resource
3131
This ability to have multiple Code Signing Accounts and Certificate Profiles is useful as the service supports Public Trust, Private Trust, CI Policy, VBS Enclave, and Test signing types. For more information on the Certificate Profile types and how they're used, review [Trusted Signing certificate types and management](./concept-trusted-signing-cert-management.md).
3232

3333

34-
[!NOTE]
34+
>[!NOTE]
3535
>Identity Validations and Certificate Profiles align with either Public or Private Trust. Meaning that a Public Trust Identity Validation is only used for Certificate Profiles that are used for the Public Trust model. For more information, review [Trusted Signing trust models](./concept-trusted-signing-trust-models.md).
3636
3737
### Trusted Signing account

0 commit comments

Comments
 (0)