Skip to content

Commit df815b3

Browse files
authored
Merge pull request #196374 from tfitzmac/0427secure
change securestring syntax
2 parents 39af12e + f2b3f1a commit df815b3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/azure-resource-manager/templates/data-types.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Describes the data types that are available in Azure Resource Manag
44
ms.topic: conceptual
55
ms.author: tomfitz
66
author: tfitzmac
7-
ms.date: 06/24/2021
7+
ms.date: 04/27/2022
88
---
99

1010
# Data types in ARM templates
@@ -20,7 +20,7 @@ Within an ARM template, you can use these data types:
2020
* int
2121
* object
2222
* secureObject
23-
* secureString
23+
* securestring
2424
* string
2525

2626
## Arrays
@@ -143,15 +143,15 @@ The following example shows two secure parameters.
143143
```json
144144
"parameters": {
145145
"password": {
146-
"type": "secureString"
146+
"type": "securestring"
147147
},
148148
"configValues": {
149149
"type": "secureObject"
150150
}
151151
}
152152
```
153-
> [!NOTE]
154-
> Secure strings and objects aren't recommended to be used as an output type because they're not stored in the deployment history.
153+
> [!NOTE]
154+
> Don't use secure strings or objects as output values. If you include a secure value as an output value, the value isn't displayed in the deployment history and can't be retrieved from another template. Instead, save the secure value in a key vault, and [pass as a parameter from the key vault](key-vault-parameter.md).
155155
156156
## Next steps
157157

0 commit comments

Comments
 (0)