You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/tag-resources.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
title: Tag resources, resource groups, and subscriptions for logical organization
3
3
description: Shows how to apply tags to organize Azure resources for billing and managing.
4
4
ms.topic: conceptual
5
-
ms.date: 03/19/2020
5
+
ms.date: 03/20/2020
6
6
---
7
-
# Use tags to organize your Azure resources, resource groups and subscriptions
7
+
# Use tags to organize your Azure resources, resource groups, and subscriptions
8
8
9
9
You apply tags to your Azure resources, resource groups, and subscriptions to logically organize them into a taxonomy. Each tag consists of a name and a value pair. For example, you can apply the name "Environment" and the value "Production" to all the resources in production.
10
10
@@ -317,9 +317,9 @@ done
317
317
IFS=$origIFS
318
318
```
319
319
320
-
## ARM templates
320
+
## Templates
321
321
322
-
You can tag resources, resource groups, and subscriptions during deployment with an ARM template.
322
+
You can tag resources, resource groups, and subscriptions during deployment with a Resource Manager template.
323
323
324
324
### Apply values
325
325
@@ -556,7 +556,12 @@ The following template adds the tags from an object to either a resource group o
556
556
557
557
## REST API
558
558
559
-
The Azure portal and PowerShell both use the [Resource Manager REST API](/rest/api/resources/) behind the scenes. If you need to integrate tagging into another environment, you can get tags by using **GET** on the resource ID and update the set of tags by using a **PATCH** call.
559
+
To work with tags through the Azure REST API, use:
560
+
561
+
*[Tags - Create Or Update At Scope](/rest/api/resources/tags/createorupdateatscope) (PUT operation)
562
+
*[Tags - Update At Scope](/rest/api/resources/tags/updateatscope) (PATCH operation)
563
+
*[Tags - Get At Scope](/rest/api/resources/tags/getatscope) (GET operation)
564
+
*[Tags - Delete At Scope](/rest/api/resources/tags/deleteatscope) (DELETE operation)
560
565
561
566
## Tags and billing
562
567
@@ -571,7 +576,7 @@ For REST API operations, see [Azure Billing REST API Reference](/rest/api/billin
571
576
The following limitations apply to tags:
572
577
573
578
* Not all resource types support tags. To determine if you can apply a tag to a resource type, see [Tag support for Azure resources](tag-support.md).
574
-
* Each resource or resource groupcan have a maximum of 50 tag name/value pairs. If you need to apply more tags than the maximum allowed number, use a JSON string for the tag value. The JSON string can contain many values that are applied to a single tag name. A resource group can contain many resources that each have 50 tag name/value pairs.
579
+
* Each resource, resource group, and subscription can have a maximum of 50 tag name/value pairs. If you need to apply more tags than the maximum allowed number, use a JSON string for the tag value. The JSON string can contain many values that are applied to a single tag name. A resource group or subscription can contain many resources that each have 50 tag name/value pairs.
575
580
* The tag name is limited to 512 characters, and the tag value is limited to 256 characters. For storage accounts, the tag name is limited to 128 characters, and the tag value is limited to 256 characters.
576
581
* Generalized VMs don't support tags.
577
582
* Tags can't be applied to classic resources such as Cloud Services.
0 commit comments