Skip to content

Commit bbf6202

Browse files
authored
Fix some more links and metadata
1 parent 0d60eb1 commit bbf6202

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/automation/automation-secure-asset-encryption.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Encryption of secure assets in automation
33
description: Azure automation protects secure assets using multiple levels of encryption. By default, the encryption is done using Microsoft-managed keys. Customers can configure their automation accounts to use customer managed keys for encryption. This article describes the details of both modes of encryption and how you can switch between the two.
44
services: automation
55
ms.service: automation
6-
ms.component: automation
6+
ms.subservice: process-automation
77
author: snehithm
88
ms.author: snmuvva
99
ms.date: 01/11/2020
@@ -53,7 +53,7 @@ Before enabling customer-managed keys for an Automation account, you must ensure
5353

5454
### Assign an identity to the automation account
5555

56-
To use customer-managed keys with an automation account, your automation account needs to authenticate against the keyvault storing customer-managed keys. Azure Automation uses system assigned managed identities to authenticate the account with Key Vault. For more information about managed identities, see [What is managed identities for Azure resources?](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview)
56+
To use customer-managed keys with an automation account, your automation account needs to authenticate against the keyvault storing customer-managed keys. Azure Automation uses system assigned managed identities to authenticate the account with Key Vault. For more information about managed identities, see [What is managed identities for Azure resources?](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview)
5757

5858
Configure a system assigned managed identity to the automation account using the following REST API call
5959

@@ -180,7 +180,7 @@ Rotating the key does not trigger re-encryption of data in the storage account.
180180

181181
## Revoke access to customer-managed keys
182182

183-
To revoke access to customer-managed keys, use PowerShell or Azure CLI. For more information, see [Azure Key Vault PowerShell](https://docs.microsoft.com/en-us/powershell/module/az.keyvault/) or [Azure Key Vault CLI](https://docs.microsoft.com/en-us/cli/azure/keyvault). Revoking access effectively blocks access to all data in the storage account, as the encryption key is inaccessible by Azure Storage.
183+
To revoke access to customer-managed keys, use PowerShell or Azure CLI. For more information, see [Azure Key Vault PowerShell](https://docs.microsoft.com/powershell/module/az.keyvault/) or [Azure Key Vault CLI](https://docs.microsoft.com/cli/azure/keyvault). Revoking access effectively blocks access to all data in the storage account, as the encryption key is inaccessible by Azure Storage.
184184

185185
## Next steps
186186

0 commit comments

Comments
 (0)