Skip to content

Commit 65b9c3c

Browse files
committed
Update the sensitive data part in parameters files
1 parent f179b55 commit 65b9c3c

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

articles/azure-resource-manager/bicep/parameter-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Create parameter file for passing in values during deployment of a
44
author: mumian
55
ms.author: jgao
66
ms.topic: conceptual
7-
ms.date: 07/18/2022
7+
ms.date: 11/14/2022
88
---
99

1010
# Create Bicep parameter file
@@ -30,7 +30,7 @@ A parameter file uses the following format:
3030
}
3131
```
3232

33-
Notice that the parameter file stores parameter values as plain text. This approach works for values that aren't sensitive, such as a resource SKU. Plain text doesn't work for sensitive values, such as passwords. If you need to pass a parameter that contains a sensitive value, store the value in a key vault. Instead of adding the sensitive value to your parameter file, retrieve it with the [getSecret function](bicep-functions-resource.md#getsecret). For more information, see [Use Azure Key Vault to pass secure parameter value during Bicep deployment](key-vault-parameter.md).
33+
It's worth noting that the parameter file saves parameter values as plain text. For security reasons, this approach is not recommended for sensitive values such as passwords. If you must pass a parameter with a sensitive value, keep the value in a key vault. Instead of adding the sensitive value to your parameter file, use the [getSecret function](bicep-functions-resource.md#getsecret) to retrieve it. For more information, see [Use Azure Key Vault to pass secure parameter value during Bicep deployment](key-vault-parameter.md).
3434

3535
## Define parameter values
3636

articles/azure-resource-manager/templates/deployment-tutorial-pipeline.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Continuous integration with Azure Pipelines
33
description: Learn how to continuously build, test, and deploy Azure Resource Manager templates (ARM templates).
4-
ms.date: 03/02/2021
4+
ms.date: 11/11/2021
55
ms.topic: tutorial
66
ms.author: jgao
77
---
@@ -43,7 +43,7 @@ GitHub is used to store your project source code including Resource Manager temp
4343

4444
### Create a GitHub repository
4545

46-
If you don't have a GitHub account, see [Prerequisites](#prerequisites).
46+
If you don't have a GitHub account, see [Prerequisites](#prerequisites). If you don't have a repository, use the following
4747

4848
1. Sign in to [GitHub](https://github.com).
4949
1. Select your account image on the upper right corner, and then select **Your repositories**.

articles/azure-resource-manager/templates/parameter-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create parameter file
33
description: Create parameter file for passing in values during deployment of an Azure Resource Manager template
44
ms.topic: conceptual
5-
ms.date: 05/11/2021
5+
ms.date: 11/14/2022
66
ms.custom: devx-track-azurepowershell
77
---
88

@@ -32,7 +32,7 @@ A parameter file uses the following format:
3232
}
3333
```
3434

35-
Notice that the parameter file stores parameter values as plain text. This approach works for values that aren't sensitive, such as a resource SKU. Plain text doesn't work for sensitive values, such as passwords. If you need to pass a parameter that contains a sensitive value, store the value in a key vault. Then reference the key vault in your parameter file. The sensitive value is securely retrieved during deployment.
35+
It's worth noting that the parameter file saves parameter values as plain text. For security reasons, this approach is not recommended for sensitive values such as passwords. If you must pass a parameter with a sensitive value, keep the value in a key vault. Then, in your parameter file, include a reference to the key vault. During deployment, the sensitive value is securely retrieved. For more information, see [Use Azure Key Vault to pass secure parameter value during deployment](./key-vault-parameter.md).
3636

3737
The following parameter file includes a plain text value and a sensitive value that's stored in a key vault.
3838

0 commit comments

Comments
 (0)