Skip to content

Commit d99581b

Browse files
authored
Merge pull request #174391 from nikitapitliya/patch-10
Updating broken link
2 parents 314d2b3 + ed6088f commit d99581b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-video-analyzer/video-analyzer-docs/customer-managed-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Bring Your Own Key (BYOK) is an Azure wide initiative to help customers move the
1515

1616
An account key is created for all Video Analyzer accounts. By default this account key is encrypted by a system key owned by Video Analyzer (i.e. system-managed key). Instead, you can use your own key with Azure Video Analyzer. In that case, your account key is encrypted with your key. Access policies and video resource metadata get encrypted using the account key.
1717

18-
Video Analyzer uses a User Assigned Managed Identity to read your key from a Key Vault owned by you. You must provide the User Assigned Managed Identity when creating or updating the Video Analyzer account and assign appropriate [Azure role-based access control]../../role-based-access-control/overview.md) to the Key Vault. Video Analyzer requires that the Key Vault is in the same region as the account, and that it has soft-delete and purge protection enabled.
18+
Video Analyzer uses a User Assigned Managed Identity to read your key from a Key Vault owned by you. You must provide the User Assigned Managed Identity when creating or updating the Video Analyzer account and assign appropriate [Azure role-based access control](../../role-based-access-control/overview.md) to the Key Vault. Video Analyzer requires that the Key Vault is in the same region as the account, and that it has soft-delete and purge protection enabled.
1919

2020
Your key can be a 2048, 3072, or a 4096 RSA key, and both HSM and software keys are supported.
2121

0 commit comments

Comments
 (0)