Organize Azure resources using tags, which are name-value pairs. ![](https://learn.microsoft.com/en-us/training/wwl-azure/design-governance/media/resource-tags.png) - **Characteristics:** - Tags can be added, modified, and deleted using various tools (PowerShell, Azure CLI, ARM templates, REST API, Azure portal). - Tags applied to a resource group are not inherited by the resources within the group. - **Design Considerations:** - Align tags with organizational taxonomy for easier understanding. - Use IT-aligned or business-aligned tagging strategies, or a combination of both. - Categories of tags include functional, classification, accounting, partnership, and purpose. - Start with a few tags and scale out based on effectiveness. - Use [[Azure Policy]] to enforce tagging rules and conventions. - Determine which resources require tagging, focusing on mission-critical ones. | Tag type | Description | Example name-value pairs | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- | | **Functional** | Functional tags categorize resources according to their purpose within a workload. This tag shows the deployed environment for a resource, or other functionality and operational details. | - `app = catalogsearch1` <br>- `tier = web` <br>- `webserver = apache` <br>- `env = production, dev, staging` | | **Classification** | Classification tags identify a resource by how it's used and what policies apply to it. | - `confidentiality = private` <br>- `SLA = 24hours` | | **Accounting** | Accounting tags allow a resource to be associated with specific groups within an organization for billing purposes. | - `department = finance` <br>- `program = business-initiative` <br>- `region = northamerica` | | **Partnership** | Partnership tags provide information about the people (other than IT members) who are associated with a resource, or otherwise affected by the resource. | - `owner = jsmith` <br>- `contactalias = catsearchowners` <br>- `stakeholders = user1;user2;user3` | | **Purpose** | Purpose tags align resources to business functions to better support investment decisions. | - `businessprocess = support` <br>- `businessimpact = moderate` <br>- `revenueimpact = high` |