Skip to content

Commit aa93136

Browse files
authored
Merge pull request #101485 from KrishnaG-MSFT/patch-50
(AzureCXP) MicrosoftDocs/azure-docs#46035
2 parents efb5ec1 + 5e7456e commit aa93136

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/automation/shared-resources/variables.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Variable assets are values that are available to all runbooks and DSC configurat
2222

2323
Since Automation variables are persisted, they are available even if the runbook or DSC configuration fails. This behavior allows a value to be set by one runbook that is then used by another, or is used by the same runbook or DSC configuration the next time that it's run.
2424

25-
When a variable is created, you can specify that it is stored encrypted. Encrypted variables are stored securely in Azure Automation, and its value can't be retrieved from the [Get-AzureRmAutomationVariable](/powershell/module/AzureRM.Automation/Get-AzureRmAutomationVariable) cmdlet that ships as part of the Azure PowerShell module. The only way that an encrypted value can be retrieved is from the **Get-AutomationVariable** activity in a runbook or DSC configuration. If you want to change an encrypted variable to un-encrypted, you can must delete and re-create the variable as un-encrypted.
25+
When a variable is created, you can specify that it is stored encrypted. Encrypted variables are stored securely in Azure Automation, and its value can't be retrieved from the [Get-AzureRmAutomationVariable](/powershell/module/AzureRM.Automation/Get-AzureRmAutomationVariable) cmdlet that ships as part of the Azure PowerShell module. The only way that an encrypted value can be retrieved is from the **Get-AutomationVariable** activity in a runbook or DSC configuration. If you want to change an encrypted variable to un-encrypted, you must delete and re-create the variable as un-encrypted.
2626

2727
>[!NOTE]
2828
>Secure assets in Azure Automation include credentials, certificates, connections, and encrypted variables. These assets are encrypted and stored in Azure Automation using a unique key that is generated for each automation account. This key is stored in a system managed Key Vault. Before storing a secure asset, the key is loaded from Key Vault and then used to encrypt the asset. This process is managed by Azure Automation.

0 commit comments

Comments
 (0)