Skip to content

Commit 40f042f

Browse files
authored
Merge pull request #293420 from tfitzmac/0122copyedit1
copy edit
2 parents de54c84 + 6b570eb commit 40f042f

File tree

5 files changed

+28
-28
lines changed

5 files changed

+28
-28
lines changed

articles/azure-resource-manager/management/create-private-link-access-portal.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.date: 09/26/2024
77

88
# Use portal to create private link for managing Azure resources
99

10-
This article explains how you can use [Azure Private Link](../../private-link/index.yml) to restrict access for managing resources in your subscriptions. It shows using the Azure portal for setting up management of resources through private access.
10+
This article explains how to use [Azure Private Link](../../private-link/index.yml) to restrict access for managing resources in your subscriptions. It shows how to use the Azure portal for setting up management of resources through private access.
1111

1212
[!INCLUDE [Create content](../../../includes/resource-manager-create-rmpl.md)]
1313

@@ -19,7 +19,7 @@ When you create a resource management private link, the private link association
1919

2020
:::image type="content" source="./media/create-private-link-access-portal/search.png" alt-text="Screenshot of Azure portal search bar with 'Resource management' entered.":::
2121

22-
1. If your subscription doesn't already have resource management private links, you'll see a blank page. Select **Create resource management private link**.
22+
1. If your subscription doesn't already have resource management private links, you see a blank page. Select **Create resource management private link**.
2323

2424
:::image type="content" source="./media/create-private-link-access-portal/start-create.png" alt-text="Screenshot of Azure portal showing the 'Create resource management private link' button.":::
2525

@@ -31,7 +31,7 @@ When you create a resource management private link, the private link association
3131

3232
## Create private endpoint
3333

34-
Now, create a private endpoint that references the resource management private link.
34+
Next, create a private endpoint that references the resource management private link.
3535

3636
1. Navigate to the **Private Link Center**. Select **Create private endpoint**.
3737

@@ -61,4 +61,4 @@ To make sure your environment is properly configured, check the local IP address
6161

6262
## Next steps
6363

64-
To learn more about private links, see [Azure Private Link](../../private-link/index.yml).
64+
To learn more about private links, see [Azure Private Link](../../private-link/index.yml).
Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: Azure Resource Graph sample queries for Azure Resource Manager
33
description: Sample Azure Resource Graph queries for Azure Resource Manager showing use of resource types and tables to access Azure Resource Manager related resources and properties.
4-
ms.date: 09/26/2024
4+
ms.date: 01/22/2025
55
ms.topic: sample
66
ms.custom: subject-resourcegraph-sample, devx-track-azurepowershell, devx-track-arm-template, devx-track-azurecli
77
---
88

99
# Azure Resource Graph sample queries for Azure Resource Manager
1010

11-
This page is a collection of [Azure Resource Graph](../../governance/resource-graph/overview.md) sample queries for Azure Resource Manager.
11+
This page contains a collection of [Azure Resource Graph](../../governance/resource-graph/overview.md) sample queries for Azure Resource Manager.
1212

1313
## Sample queries for tags
1414

@@ -17,4 +17,4 @@ This page is a collection of [Azure Resource Graph](../../governance/resource-gr
1717
## Next steps
1818

1919
- Learn more about the [query language](../../governance/resource-graph/concepts/query-language.md).
20-
- Learn more about how to [explore resources](../../governance/resource-graph/concepts/explore-resources.md).
20+
- Learn more about how to [explore resources](../../governance/resource-graph/concepts/explore-resources.md).

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@
22
title: Policy definitions for tagging resources
33
description: Describes the Azure Policy definitions that you can assign to ensure tag compliance.
44
ms.topic: conceptual
5-
ms.date: 09/26/2024
5+
ms.date: 01/22/2025
66
---
77

88
# Assign policy definitions for tag compliance
99

10-
You use [Azure Policy](../../governance/policy/overview.md) to enforce tagging rules and conventions. By creating a policy, you avoid the scenario of resources being deployed to your subscription that don't have the expected tags for your organization. Instead of manually applying tags or searching for resources that aren't compliant, you create a policy that automatically applies the needed tags during deployment. Tags can also now be applied to existing resources with the new [Modify](../../governance/policy/concepts/effects.md#modify) effect and a [remediation task](../../governance/policy/how-to/remediate-resources.md). The following section shows example policy definitions for tags.
10+
Use [Azure Policy](../../governance/policy/overview.md) to enforce tagging rules and conventions. By creating a policy, you avoid the scenario of resources being deployed to your subscription that don't have the expected tags for your organization. Instead of manually applying tags or searching for resources that aren't compliant, create a policy that automatically applies the needed tags during deployment. With the new [Modify](../../governance/policy/concepts/effects.md#modify) effect and a [remediation task](../../governance/policy/how-to/remediate-resources.md), you can also apply tags to existing resources. The following section shows example policy definitions for tags.
1111

1212
## Policy definitions
1313

@@ -16,4 +16,4 @@ You use [Azure Policy](../../governance/policy/overview.md) to enforce tagging r
1616
## Next steps
1717

1818
* To learn about tagging resources, see [Use tags to organize your Azure resources](tag-resources.md).
19-
* 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).
19+
* 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).

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Tag resources, resource groups, and subscriptions with Azure portal
33
description: Shows how to use Azure portal to apply tags to Azure resources.
44
ms.topic: conceptual
5-
ms.date: 09/26/2024
5+
ms.date: 01/22/2025
66
---
77

88
# Apply tags with Azure portal
@@ -11,13 +11,13 @@ This article describes how to use the Azure portal to tag resources. For tag rec
1111

1212
## Add tags
1313

14-
If a user doesn't have the required access for adding tags, you can assign the **Tag Contributor** role to the user. For more information, see [Tutorial: Grant a user access to Azure resources using RBAC and the Azure portal](../../role-based-access-control/quickstart-assign-role-user-portal.md).
14+
If a user doesn't have the required access for adding tags, assign the **Tag Contributor** role to the user. For more information, see [Tutorial: Grant a user access to Azure resources using RBAC and the Azure portal](../../role-based-access-control/quickstart-assign-role-user-portal.md).
1515

16-
1. To view the tags for a resource or a resource group, look for existing tags in the overview. If you have not previously applied tags, the list is empty.
16+
1. To view the tags for a resource or a resource group, look for existing tags in the overview. If you didn't previously apply tags, the list is empty.
1717

1818
:::image type="content" source="./media/tag-resources-portal/view-tags.png" alt-text="Screenshot of Azure portal showing tags for a resource group.":::
1919

20-
1. To add a tag, select **Click here to add tags**.
20+
1. To add a tag, select **Add tags**.
2121

2222
1. Provide a name and value.
2323

@@ -63,7 +63,7 @@ To view all resources with a tag:
6363

6464
:::image type="content" source="./media/tag-resources-portal/select-tag.png" alt-text="Screenshot of Azure portal displaying a list of tags with one selected for viewing resources.":::
6565

66-
1. All resources with that tag are displayed.
66+
1. The portal displays all resources with that tag.
6767

6868
:::image type="content" source="./media/tag-resources-portal/view-resources-by-tag.png" alt-text="Screenshot of Azure portal showing a list of resources filtered by the selected tag.":::
6969

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

Lines changed: 13 additions & 13 deletions
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: Describes the conditions and limitations for using tags with Azure resources.
44
ms.topic: conceptual
5-
ms.date: 09/26/2024
5+
ms.date: 01/22/2025
66
---
77

88
# Use tags to organize your Azure resources and management hierarchy
@@ -30,10 +30,10 @@ Resource tags support all cost-accruing services. To ensure that cost-accruing s
3030
> Tags are stored as plain text. Never add sensitive values to tags. Sensitive values could be exposed through many methods, including cost reports, commands that return existing tag definitions, deployment histories, exported templates, and monitoring logs.
3131
3232
> [!WARNING]
33-
> Please be careful while using non-English language in your tags. It can cause decoding progress failure while loading your VM's metadata from IMDS (Instance Metadata Service).
33+
> Be careful when using non-English language in your tags. It can cause decoding progress failure while loading your VM's metadata from IMDS (Instance Metadata Service).
3434
3535
> [!IMPORTANT]
36-
> Tag names are case-insensitive for operations. A tag with a tag name, regardless of the 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.
36+
> Tag names are case-insensitive for operations. An operation updates or retrieves a tag with a tag name, regardless of the casing. However, the resource provider might keep the casing you provide for the tag name. You see that casing in cost reports.
3737
>
3838
> Tag values are case-sensitive.
3939
@@ -51,38 +51,38 @@ There are two ways to get the required access to tag resources.
5151

5252
Resources don't inherit the tags you apply to a resource group or a subscription. To apply tags from a subscription or resource group to the resources, see [Azure Policies - tags](tag-policies.md).
5353

54-
You can group costs for an Azure resource by using the **cm-resource-parent** tag. This tag lets you review tagged costs in Microsoft Cost Management without having to use filters. The key for this tag is cm-resource-parent and its value is the resource ID of the Azure resource you want to group costs by. For example, to group costs by an Azure Virtual Desktop host pool, provide the resource ID of the host pool. For more information, see [Group related resources in the cost analysis](../../cost-management-billing/costs/group-filter.md#group-related-resources-in-the-resources-view).
54+
You can group costs for an Azure resource by using the **cm-resource-parent** tag. This tag lets you review tagged costs in Microsoft Cost Management without having to use filters. The key for this tag is `cm-resource-parent` and its value is the resource ID of the Azure resource you want to group costs by. For example, to group costs by an Azure Virtual Desktop host pool, provide the resource ID of the host pool. For more information, see [Group related resources in the cost analysis](../../cost-management-billing/costs/group-filter.md#group-related-resources-in-the-resources-view).
5555

5656
## Tags and billing
5757

58-
You can use tags to group your billing data. If you're running multiple VMs for different organizations, for example, use the tags to group usage by cost center. You can also use tags to categorize costs by runtime environment, such as the billing usage for VMs running in the production environment.
58+
Use tags to group your billing data. For example, if you're running multiple VMs for different organizations, use the tags to group usage by cost center. You can also use tags to categorize costs by runtime environment, such as the billing usage for VMs running in the production environment.
5959

60-
You can retrieve information about tags by downloading the usage file available from the Azure portal. For more information, see [Download or view your Azure billing invoice and daily usage data](../../cost-management-billing/manage/download-azure-invoice-daily-usage-date.md). For services that support tags with billing, the tags appear in the **Tags** column.
60+
To retrieve information about tags, download the usage file from the Azure portal. For more information, see [Download or view your Azure billing invoice and daily usage data](../../cost-management-billing/manage/download-azure-invoice-daily-usage-date.md). For services that support tags with billing, the tags appear in the **Tags** column.
6161

6262
For REST API operations, see [Azure Billing REST API Reference](/rest/api/billing/).
6363

6464
## Unique tags pagination
6565

66-
When calling the [Unique Tags API](/rest/api/resources/tags/list) there's a limit to the size of each API response page that is returned. A tag that has a large set of unique values will require the API to fetch the next page to retrieve the remaining set of values. When this happens the tag key is shown again to indicate that the values are still under this key.
66+
When you call the [Unique Tags API](/rest/api/resources/tags/list), there's a limit to the size of each API response page. A tag that has a large set of unique values requires the API to fetch the next page to retrieve the remaining set of values. When the results are divided over multiple pages, the API response shows the tag key again to indicate that the values are still under this key.
6767

68-
This can result in some tools, like the Azure portal, to show the tag key twice.
68+
This behavior can result in some tools, like the Azure portal, showing the tag key twice.
6969

7070
## Limitations
7171

7272
The following limitations apply to tags:
7373

7474
* 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).
75-
* Each resource type might have specific requirements when working with tags. For example, tags on virtual machine (VM) extensions can only be updated when the VM is running. If you receive an error message while trying to update a tag, follow the instructions in the message.
75+
* Each resource type might have specific requirements when working with tags. For example, you can only update tags on virtual machine (VM) extensions when the VM is running. If you receive an error message while trying to update a tag, follow the instructions in the message.
7676
* 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 of the values that you apply to a single tag name. A resource group or subscription can contain many resources that each have 50 tag name-value pairs.
7777
* The tag name has a limit of 512 characters and the tag value has a limit of 256 characters. For storage accounts, the tag name has a limit of 128 characters and the tag value has a limit of 256 characters.
7878
* Classic resources such as Cloud Services don't support tags.
79-
* Azure IP Groups and Azure Firewall Policies don't support PATCH operations. PATCH API method operations, therefore, can't update tags through the portal. Instead, you can use the update commands for those resources. You can update tags for an IP group, for example, with the [az network ip-group update](/cli/azure/network/ip-group#az-network-ip-group-update) command.
79+
* Azure IP Groups and Azure Firewall Policies don't support PATCH operations. PATCH API method operations, therefore, can't update tags through the portal. Instead, use the update commands for those resources. For example, you can update tags for an IP group with the [az network ip-group update](/cli/azure/network/ip-group#az-network-ip-group-update) command.
8080
* Tag names can't contain these characters: `<`, `>`, `%`, `&`, `\`, `?`, `/`
8181

8282
> [!NOTE]
83-
> * Azure Domain Name System (DNS) zones don't support the use of spaces or parentheses in the tag or a tag that starts with a number. Azure DNS tag names don't support special and unicode characters. The value can contain all characters.
83+
> * Azure Domain Name System (DNS) zones don't support the use of spaces or parentheses in the tag or a tag that starts with a number. Azure DNS tag names don't support special and Unicode characters. The value can contain all characters.
8484
>
85-
> * Traffic Manager doesn't support the use of spaces, `#` or `:` in the tag name. The tag name can't start with a number.
85+
> * Traffic Manager doesn't support the use of spaces, `#`, or `:` in the tag name. The tag name can't start with a number.
8686
>
8787
> * Azure Front Door doesn't support the use of `#` or `:` in the tag name.
8888
>
@@ -103,4 +103,4 @@ The following limitations apply to tags:
103103
* [Azure PowerShell](tag-resources-powershell.md)
104104
* [Python](tag-resources-python.md)
105105
* [ARM templates](tag-resources-templates.md)
106-
* [Bicep](tag-resources-bicep.md)
106+
* [Bicep](tag-resources-bicep.md)

0 commit comments

Comments
 (0)