Skip to content

Commit 3880235

Browse files
authored
Merge pull request #191771 from tfitzmac/0315tagsecure
add warning for sensitive values
2 parents c89518f + 3cef237 commit 3880235

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/azure-resource-manager/management/tag-resources.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Tag resources, resource groups, and subscriptions for logical organization
33
description: Shows how to apply tags to organize Azure resources for billing and managing.
44
ms.topic: conceptual
5-
ms.date: 01/28/2022
5+
ms.date: 03/15/2022
66
ms.custom: devx-track-azurecli, devx-track-azurepowershell
77
---
88

@@ -12,6 +12,9 @@ You apply tags to your Azure resources, resource groups, and subscriptions to lo
1212

1313
For recommendations on how to implement a tagging strategy, see [Resource naming and tagging decision guide](/azure/cloud-adoption-framework/decision-guides/resource-tagging/?toc=/azure/azure-resource-manager/management/toc.json).
1414

15+
> [!WARNING]
16+
> Tags are stored as plain text. Never add sensitive values to tags. Sensitive values could be exposed through many methods, including cost reports, tag taxonomies, deployment histories, exported templates, and monitoring logs.
17+
1518
> [!IMPORTANT]
1619
> Tag names are case-insensitive for operations. A tag with a tag name, regardless of casing, is updated or retrieved. However, the resource provider might keep the casing you provide for the tag name. You'll see that casing in cost reports.
1720
>

0 commit comments

Comments
 (0)