Skip to content

Commit 36b5174

Browse files
committed
Edited the first para
1 parent e7dd05b commit 36b5174

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,19 @@ ms.subservice: process-automation
77
ms.custom: devx-track-azurepowershell
88
author: snehithm
99
ms.author: snmuvva
10-
ms.date: 07/27/2021
10+
ms.date: 04/20/2023
1111
ms.topic: conceptual
1212
manager: kmadnani
1313
---
1414

1515
# Encryption of secure assets in Azure Automation
1616

17-
Secure assets in Azure Automation include credentials, certificates, connections, and encrypted variables. These assets are protected in Azure Automation using multiple levels of encryption. Based on the top-level key used for the encryption, there are two models for encryption:
17+
Azure Automation secures assets such as credentials, certificates, connections, and encrypted variables are using various levels of encryption. This helps enhance the security of these assets. Additionally, to ensure greater security and privacy for the customer code, runbooks, and DSC scripts are also encrypted. Encryption in Azure Automation follows two models, depending on the top-level key used for encryption:
1818

1919
- Using Microsoft-managed keys
2020
- Using keys that you manage
2121

22+
2223
## Microsoft-managed Keys
2324

2425
By default, your Azure Automation account uses Microsoft-managed keys.

0 commit comments

Comments
 (0)