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
description: Understand how to label missioncritical workloads in Azure for Microsoft workload assessments
2
+
title: Label mission-critical workloads
3
+
description: Learn how to label mission-critical workloads in Azure to assess Microsoft workloads.
4
4
ms.topic: conceptual
5
-
ms.date: 03/20/2025
5
+
ms.date: 04/14/2025
6
6
---
7
-
# Mission critical workload labeling
8
7
9
-
Azure provides a robust, scalable cloud platform with various tools and services to help you manage and optimize your resources. This document outlines how to tag resources in an Azure tenant for identifying mission-critical workloads and determining potential resiliency improvements. Tagging your resources streamlines the onboarding of your workload definition for Microsoft assessments, providing a more concisely targeted review.
8
+
# Label mission-critical workloads
10
9
11
-
## Understanding Azure tags
10
+
Azure provides a robust, scalable cloud platform with various tools and services to help you manage and optimize your resources. This document outlines how to tag resources in an Azure tenant to identify mission-critical workloads and determine potential resiliency improvements. Tagging your resources streamlines how your workload definitions are onboarded for Microsoft assessments, providing a more concisely targeted review.
12
11
13
-
For an introduction to tagging of Azure resources and to learn about requirements and limitations refer to the following article.
12
+
## Understand Azure tags
14
13
15
-
[Use tags to organize your Azure resources and management hierarchy - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources)
14
+
For an introduction about tagging Azure resources and to learn about requirements and limitations, refer to [Use tags to organize your Azure resources and management hierarchy](/azure/azure-resource-manager/management/tag-resources).
16
15
17
-
## Why identify missioncritical workloads?
16
+
## Why identify mission-critical workloads?
18
17
19
-
Identifying mission critical related resources brings numerous benefits including resource management, cost management and optimization, security, automation and workload optimization. By tagging these resources, you can group them as part of a mission critical workload. These tags help in accurately identifying and managing these essential workloads. You can read more about tagging usage here [Resource naming and tagging decision guide - Cloud Adoption Framework | Microsoft Learn](/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming-and-tagging-decision-guide).
18
+
The term _workload_ refers to a collection of application resources that support a common business goal or the execution of a common business process with multiple services, such as APIs and data stores, that work together to deliver specific end-to-end functionality.
20
19
21
-
This article aligns with workload optimization, where tagging can help inform of opportunities to improve resiliency and further enhance your Service Level Objectives.
20
+
Mission-critical workload resources are often spread across multiple resource groups and subscriptions. Regardless of the resource location, each resource within a mission-critical workload should be included in the workload definition and tagged appropriately.
22
21
23
-
*This documentation supports a Microsoft assessment of your environment using the tagging approach described. Your Microsoft contact reviews this tagging approach with you at the beginning of the assessment. If you don't have an engagement with Microsoft, you can still follow the guidance to realize the benefits outlined earlier.*
22
+
Identifying related mission-critical resources has benefits that include resource management, cost management and optimization, security, automation, and workload optimization. By tagging resources, you to group them into a mission-critical workload where tags accurately identify and manage these essential workloads.
24
23
25
-
The term workload refers to a collection of application resources that support a common business goal or the execution of a common business process, with multiple services, such as APIs and data stores, working together to deliver specific end-to-end functionality.
24
+
In a scenario where a mission-critical workload depends on a service that's shared across multiple workloads, such as an Azure ExpressRoute gateway or an Azure Firewall, the shared resources should also be included in the workload definition and tagged appropriately. See the examples in the following section for how to tag values on shared services.
26
25
27
-
Mission critical workload resources are often spread across multiple resource groups and subscriptions. Regardless of the resource location, each resource within the mission critical workload should be included in the workload definition and tagged appropriately.
26
+
This article aligns with workload optimization, and tagging can identify opportunities to improve resiliency and further enhance your Service Level Objectives.
28
27
29
-
In a scenario where a mission critical workload depends on a service that is shared across multiple workloads, such as an ExpressRoute gateway or an Azure Firewall, the shared resources should also be included in the workload definition and tagged appropriately. See the example in the previous section for tag values to be used on shared services.
28
+
*This documentation recommends the tagging approach described to support a Microsoft assessment of your environment. Your Microsoft contact reviews this tagging approach with you at the beginning of the assessment. If you don't have an engagement with Microsoft, you can still follow the guidance to realize the benefits outlined earlier.*
30
29
31
-
For further insights into defining a workload, refer to the following article.
30
+
## Mission-critical predefined tags
32
31
33
-
[Azure Well-Architected Framework workloads - Microsoft Azure Well-Architected Framework | Microsoft Learn](/azure/well-architected/workloads)
34
-
35
-
## Mission critical predefined tags
36
-
37
-
To enable use by Microsoft in a workload assessment, the tags used for mission critical workloads must use the following tag name and adhere to the value format.
32
+
To enable use by Microsoft in a workload assessment, the tags used for mission-critical workloads must use the following tag name and adhere to the value format:
38
33
39
34
> [!Important]
40
35
> Tag values must **NOT** contain numeric or non-English characters.
@@ -47,14 +42,14 @@ To enable use by Microsoft in a workload assessment, the tags used for mission c
@@ -64,11 +59,16 @@ To enable use by Microsoft in a workload assessment, the tags used for mission c
64
59
65
60
## How to apply Azure tags
66
61
67
-
Tagging of mission critical workloads requires that tags be applied to each of the individual Azure resources that make up the workload. Tags can be applied to resources in the Azure portal, with Azure Policy, or via automation tools. Review the following guidance to determine the approach that works best for your organization.
62
+
Tagging mission-critical workloads requires that tags be applied to each Azure resource that makes up a workload. Tags can be applied to resources in the Azure portal, with Azure Policy, or via automation tools. Review the following guidance to determine the approach that works best for your organization:
63
+
64
+
- Azure portal: [Apply tags with Azure portal](/azure/azure-resource-manager/management/tag-resources-portal)
65
+
- Azure Policy: [Assign policy definitions for tag compliance](/azure/azure-resource-manager/management/tag-policies)
66
+
- Azure PowerShell: [Apply tags with Azure PowerShell](/azure/azure-resource-manager/management/tag-resources-powershell)
67
+
- Azure CLI: [Apply tags with Azure CLI](/azure/azure-resource-manager/management/tag-resources-cli)
68
+
- Bicep: [Apply tags with Bicep](/azure/azure-resource-manager/management/tag-resources-bicep)
- Azure portal: [Tag resources, resource groups, and subscriptions with Azure portal - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-portal)
70
-
- Azure Policy: [Policy definitions for tagging resources - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-policies)
71
-
- Azure PowerShell: [Tag resources, resource groups, and subscriptions with Azure PowerShell - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-powershell)
72
-
- Azure CLI: [Tag resources, resource groups, and subscriptions with Azure CLI - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-cli)
73
-
- Bicep: [Tag resources, resource groups, and subscriptions with Bicep - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-bicep)
74
-
- Terraform: [Microsoft.Resources/tags - Bicep, ARM template & Terraform AzAPI reference | Microsoft Learn](/azure/templates/microsoft.resources/tags)
73
+
- For more information about defining workloads, see [Azure Well-Architected Framework workloads](/azure/well-architected/workloads).
74
+
- To learn more about using tags, see the Azure Cloud Adoption Framework [Resource naming and tagging decision guide](/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming-and-tagging-decision-guide).
Copy file name to clipboardExpand all lines: articles/digital-twins/concepts-cli.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure Digital Twins
4
4
description: Learn about the Azure Digital Twins CLI command set.
5
5
author: baanders
6
6
ms.author: baanders
7
-
ms.date: 03/31/2022
7
+
ms.date: 04/09/2025
8
8
ms.topic: conceptual
9
9
ms.service: azure-digital-twins
10
10
---
@@ -38,18 +38,18 @@ The Azure Digital Twins commands are part of the [Azure IoT extension for Azure
38
38
39
39
### CLI version requirements
40
40
41
-
If you're using the Azure CLI with PowerShell, your Azure CLI version should be 2.3.1 or above as a requirement of the extension package.
41
+
If you're using the Azure CLI with PowerShell, your Azure CLI version should be 2.3.1 or greater as a requirement of the extension package.
42
42
43
43
You can check the version of your Azure CLI with this CLI command:
44
44
```azurecli
45
45
az --version
46
46
```
47
47
48
-
For instructions on how to install or update the Azure CLI to a newer version, see [Install the Azure CLI](/cli/azure/install-azure-cli).
48
+
For instructions on how to install or update the Azure CLI to a newer version, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
49
49
50
50
### Get the extension
51
51
52
-
The Azure CLI will automatically prompt you to install the extension on the first use of a command that requires it.
52
+
The Azure CLI automatically prompts you to install the extension on the first use of a command that requires it.
53
53
54
54
Otherwise, you can use the following command to install the extension yourself at any time (or update it if it turns out that you already have an older version). The command can be run in either the [Azure Cloud Shell](../cloud-shell/overview.md) or a [local Azure CLI](/cli/azure/install-azure-cli).
55
55
@@ -59,7 +59,7 @@ az extension add --upgrade --name azure-iot
59
59
60
60
## Use special characters in different shells
61
61
62
-
Some `az dt` commands use special characters that may have to be escaped for proper parsing in certain shell environments. Use the tips in this section to help you know when to do this in your shell of choice.
62
+
Some `az dt` commands use special characters that might have to be escaped for proper parsing in certain shell environments. Use the tips in this section to help you know when to escape special characters in your shell of choice.
63
63
64
64
### Bash
65
65
@@ -69,7 +69,7 @@ Use these special character tips for Bash environments.
69
69
70
70
In many twin queries, the `$` character is used to reference the `$dtId` property of a twin. When using the [az dt twin query](/cli/azure/dt/twin#az-dt-twin-query) command to query in the Cloud Shell Bash environment, escape the `$` character with a backslash (`\`).
71
71
72
-
Here is an example of querying for a twin with a CLI command in the Cloud Shell Bash environment:
72
+
Here's an example of querying for a twin with a CLI command in the Cloud Shell Bash environment:
73
73
74
74
```azurecli
75
75
az dt twin query --dt-name <instance-hostname-or-name> --query-command "SELECT * FROM DigitalTwins T Where T.\$dtId = 'room0'"
@@ -83,7 +83,7 @@ Use these special character tips for PowerShell environments.
83
83
84
84
Some commands, like [az dt twin create](/cli/azure/dt/twin#az-dt-twin-create), allow you to enter twin information in the form of inline JSON. When entering inline JSON in the PowerShell environment, escape double quote characters (`"`) inside the JSON with a backslash (`\`).
85
85
86
-
Here is an example of creating a twin with a CLI command in PowerShell:
86
+
Here's an example of creating a twin with a CLI command in PowerShell:
In many twin queries, the `$` character is used to reference the `$dtId` property of a twin. When using the [az dt twin query](/cli/azure/dt/twin#az-dt-twin-query) command to query in a PowerShell environment, escape the `$` character with a backtick character.
98
98
99
-
Here is an example of querying for a twin with a CLI command in PowerShell:
99
+
Here's an example of querying for a twin with a CLI command in PowerShell:
100
+
100
101
```azurecli
101
102
az dt twin query --dt-name <instance-hostname-or-name> --query-command "SELECT * FROM DigitalTwins T Where T.`$dtId = 'room0'"
102
103
```
@@ -109,7 +110,7 @@ Use these special character tips for the local Windows CMD.
109
110
110
111
Some commands, like [az dt twin create](/cli/azure/dt/twin#az-dt-twin-create), allow you to enter twin information in the form of inline JSON. When entering inline JSON in a local Windows CMD window, enclose the parameter value with double quotes (`"`) instead of single quotes (`'`), and escape double quote characters inside the JSON with a backslash (`\`).
111
112
112
-
Here is an example of creating a twin with a CLI command in the local Windows CMD:
113
+
Here's an example of creating a twin with a CLI command in the local Windows CMD:
Copy file name to clipboardExpand all lines: articles/digital-twins/troubleshoot-error-cli-parse.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.service: azure-digital-twins
6
6
author: baanders
7
7
ms.author: baanders
8
8
ms.topic: troubleshooting
9
-
ms.date: 03/31/2022
9
+
ms.date: 04/11/2025
10
10
---
11
11
12
12
# Troubleshoot parsing failures with Azure Digital Twins CLI commands
@@ -17,13 +17,13 @@ This article describes causes and resolution steps for various "parse failed" er
17
17
18
18
## Symptoms
19
19
20
-
While attempting to run select `az dt` commands in an Azure CLI environment, you receive an error indicating that the command wasn't parsed correctly. The error message might include the words *parse failed* or *failed to parse*, or partial text from your command may be marked as *unrecognized arguments.*
20
+
While attempting to run select `az dt` commands in an Azure CLI environment, you receive an error indicating that the command wasn't parsed correctly. The error message might include the words *parse failed* or *failed to parse*, or partial text from your command might be marked as *unrecognized arguments.*
21
21
22
22
## Causes
23
23
24
24
### Cause #1
25
25
26
-
Some `az dt` commands use special characters that have to be escaped for proper parsing in certain shell environments. It is possible that some special character in your CLI command needs to be escaped for it to be parsed in the shell that you're using.
26
+
Some `az dt` commands use special characters that have to be escaped for proper parsing in certain shell environments. It's possible that some special character in your CLI command needs to be escaped for the command to be parsed in the shell that you're using.
27
27
28
28
## Solutions
29
29
@@ -37,7 +37,7 @@ If you're encountering the parsing issue while passing inline JSON into a comman
37
37
38
38
### Solution #3
39
39
40
-
Not all shells have the same special character requirements, so you can try running the command in a different shell type (some options are the [Cloud Shell](https://shell.azure.com) Bash environment, [Cloud Shell](https://shell.azure.com) PowerShell environment, local Windows CMD, local Bash window, or local PowerShell window).
40
+
Not all shells have the same special character requirements, so you can try running the command in a different shell option. Some options include the [Cloud Shell](https://shell.azure.com) Bash environment, [Cloud Shell](https://shell.azure.com) PowerShell environment, local Windows CMD, local Bash window, or local PowerShell window.
0 commit comments