Skip to content

Commit 66e0c78

Browse files
authored
Merge pull request #261389 from bandersmsft/billing-tags
MCM - Adding billing tags article and update cost allocation
2 parents 6301c37 + 5e49ad5 commit 66e0c78

File tree

8 files changed

+98
-17
lines changed

8 files changed

+98
-17
lines changed

articles/cost-management-billing/costs/allocate-costs.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: Allocate Azure costs
33
description: This article explains how create cost allocation rules to distribute costs of subscriptions, resource groups, or tags to others.
44
author: bandersmsft
55
ms.author: banders
6-
ms.date: 08/07/2023
6+
ms.date: 12/15/2023
77
ms.topic: how-to
88
ms.service: cost-management-billing
99
ms.subservice: cost-management
10-
ms.reviewer: benshy
10+
ms.reviewer: sadoulta
1111
---
1212

1313
# Create and manage Azure cost allocation rules
@@ -68,13 +68,18 @@ Once set, the prefilled percentages defined don't change. All ongoing allocation
6868

6969
The allocation rule starts processing. When the rule is active, all the selected source's costs allocate to the specified targets.
7070

71-
> [!NOTE]
72-
> New rule processing can take up to two hours before it completes and is active.
73-
7471
Here's a video that demonstrates how to create a cost allocation rule.
7572

7673
>[!VIDEO https://www.youtube.com/embed/nYzIIs2mx9Q]
7774
75+
## Rules processing
76+
77+
Rules are processed in the order in which they're created and can take up to 24 hours to take effect.
78+
79+
Let's look at an example. Assume that an active rule, *Rule CA-1*, allocates costs from subscription A (the source) to subscription B (the target).
80+
81+
Later, a new rule, *Rule CA-2* gets created. Its source is subscription A and its target is subscription C. So, the rule has no effect because costs for subscription A are zero. The costs are zero because *Rule CA-1* is active. It already allocated all the costs from subscription A to subscription B.
82+
7883
## Verify the cost allocation rule
7984

8085
When the cost allocation rule is active, costs from the selected sources distribute to the specified allocation targets. Use the following information to verify proper cost allocation to targets.
@@ -127,7 +132,7 @@ However, cost allocation data results might be empty if you're using an unsuppor
127132

128133
If you have cost allocation rules enabled, the `UnitPrice` field in your usage details file is 0. We recommend that you use price sheet data to get unit price information until it's available in the usage details file.
129134

130-
Cost allocation to a target won't happen if that target doesn't have any costs associated with it.
135+
Cost allocation to a target doesn't happen if that target doesn't have any costs associated with it.
131136

132137
## Next steps
133138

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: Apply billing tags
3+
titleSuffix: Microsoft Cost Management
4+
description: This article explains what billing tags are how and how to apply them in Cost Management.
5+
author: bandersmsft
6+
ms.author: banders
7+
ms.date: 12/15/2023
8+
ms.topic: conceptual
9+
ms.service: cost-management-billing
10+
ms.subservice: cost-management
11+
ms.reviewer: sadoulta
12+
---
13+
14+
15+
# Apply billing tags
16+
17+
Billing tags are metadata elements that you can apply to Microsoft Customer Agreement MCA billing entities including billing profiles and invoice sections. Just like Azure tags, billing tags are key-value pairs that are used to identify the entities.
18+
19+
For example, to identify an invoice section with subscriptions belonging to the marketing department, you could use the tag with `key` : *Department* and `value` : *Marketing*. The fully formed `key` : *value* pair would be `Department` : *Marketing*.
20+
21+
> [!NOTE]
22+
> The limitations and recommendations that apply to Azure tags also apply to billing tags.
23+
24+
> [!WARNING]
25+
> 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.
26+
27+
## Tag application
28+
29+
**Required permissions**
30+
Billing tags are applied in the Azure portal. The required permissions are:
31+
32+
- Billing profile contributor/owner for billing profile tags
33+
- Invoice section contributor/owner for invoice section tags
34+
35+
**Billing profile tags**
36+
37+
1. Go to [https://portal.azure.com.](https://portal.azure.com.)
38+
1. Search for and select **Cost Management + Billing**.
39+
1. Select the billing profile where you want to set the tags.
40+
1. On the left menu, select **Properties** under **Settings** and then select **Add or Update tags**.
41+
:::image type="content" source="./media/billing-tags/billing-profile-tag.png" alt-text="Screenshot showing tag application to a billing profile." lightbox="./media/billing-tags/billing-profile-tag.png" :::
42+
43+
### Invoice section tags
44+
45+
1. Go to [https://portal.azure.com](https://portal.azure.com).
46+
1. Search for and select **Cost Management + Billing**.
47+
1. Select your billing profile.
48+
1. On the left menu, select **Invoice sections** under **Billing**.
49+
1. Select the invoice section where you want to set the tags.
50+
1. On the left menu, select **Properties** under **Settings** and then select **Add or update Tags**.
51+
:::image type="content" source="./media/billing-tags/invoice-section-tag.png" alt-text="Screenshot showing tag application to an invoice section." lightbox="./media/billing-tags/invoice-section-tag.png" :::
52+
53+
## Tag inheritance and billing tags
54+
55+
When you enable the **Tag inheritance** setting at the billing profile level, tags from billing profile and invoices sections are applied to usage records for all child resources. For more information about tag inheritance, see [Group and allocate costs using tag inheritance](enable-tag-inheritance.md).
56+
57+
## Next steps
58+
59+
- Learn how to [Group and allocate costs using tag inheritance](enable-tag-inheritance.md).

articles/cost-management-billing/costs/enable-tag-inheritance.md

Lines changed: 26 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Cost Management
44
description: This article explains how to group costs using tag inheritance.
55
author: bandersmsft
66
ms.author: banders
7-
ms.date: 08/04/2023
7+
ms.date: 12/15/2023
88
ms.topic: how-to
99
ms.service: cost-management-billing
1010
ms.subservice: cost-management
@@ -13,17 +13,20 @@ ms.reviewer: sadoulta
1313

1414
# Group and allocate costs using tag inheritance
1515

16-
Azure tags are widely used to group costs to align with different business units, engineering environments, and cost departments. Tags provide the visibility needed for businesses to manage and allocate costs across the different groups.
16+
Tags are widely used to group costs to align with different business units, engineering environments, cost departments, and so on. Tags provide the visibility needed for businesses to manage and allocate costs across the different groups.
1717

18-
This article explains how to use the tag inheritance setting in Cost Management. When enabled, tag inheritance applies resource group and subscription tags to child resource usage records. You don't have to tag every resource or rely on resources that emit usage to have their own tags.
18+
This article explains how to use the tag inheritance setting in Cost Management. When enabled, tag inheritance applies billing, resource group, and subscription tags to child resource usage records. You don't have to tag every resource or rely on resources that emit usage to have their own tags.
1919

2020
Tag inheritance is available for the following billing account types:
2121

2222
- Enterprise Agreement (EA)
2323
- Microsoft Customer Agreement (MCA)
2424
- Microsoft Partner Agreement (MPA) with Azure plan subscriptions
2525

26-
Here's an example diagram showing how a tag is inherited. *Note that inherited tags are applied to child resource usage records and not the resources themselves.*
26+
Here's an example diagram showing how a tag is inherited.
27+
28+
>[!NOTE]
29+
> Inherited tags are applied to child resource usage records and not the resources themselves.
2730
2831
:::image type="content" source="./media/enable-tag-inheritance/tag-example-01.svg" alt-text="Example diagram showing how a tag is inherited." border="false" lightbox="./media/enable-tag-inheritance/tag-example-01.svg":::
2932

@@ -41,7 +44,7 @@ Here's an example diagram showing how a tag is inherited. *Note that inherited t
4144

4245
## Enable tag inheritance
4346

44-
You can enable the tag inheritance setting in the Azure portal. You apply the setting at the EA billing account, MCA billing profile, and subscription scopes. After the setting is enabled, all resource group and subscription tags are automatically applied to child resource usage records.
47+
You can enable the tag inheritance setting in the Azure portal. You apply the setting at the EA billing account, MCA billing profile, and subscription scopes.
4548

4649
### To enable tag inheritance in the Azure portal for an EA billing account
4750

@@ -53,16 +56,20 @@ You can enable the tag inheritance setting in the Azure portal. You apply the se
5356
1. In the Tag inheritance window, select **Automatically apply subscription and resource group tags to new data**.
5457
:::image type="content" source="./media/enable-tag-inheritance/automatically-apply-tags-new-usage-data.png" alt-text="Screenshot showing the Automatically apply subscription and resource group tags to new data option for a billing account." lightbox="./media/enable-tag-inheritance/automatically-apply-tags-new-usage-data.png":::
5558

59+
After tag inheritance is enabled, subscription and resource group tags are applied to child resource usage records for the current month within 24 hours.
60+
5661
### To enable tag inheritance in the Azure portal for an MCA billing profile
5762

5863
1. In the Azure portal, search for **Cost Management** and select it (the green hexagon-shaped symbol, *not* Cost Management + Billing).
5964
1. Select a scope.
6065
1. In the left menu under **Settings**, select **Manage billing profile**.
6166
1. Under **Tag inheritance**, select **Edit**.
6267
:::image type="content" source="./media/enable-tag-inheritance/edit-tag-inheritance-billing-profile.png" alt-text="Screenshot showing the Edit option for Tag inheritance for an MCA billing profile." lightbox="./media/enable-tag-inheritance/edit-tag-inheritance-billing-profile.png":::
63-
1. In the Tag inheritance window, select **Automatically apply subscription and resource group tags to new data**.
68+
1. In the Tag inheritance window, select **Automatically apply billing, subscription and resource group tags to new usage data**.
6469
:::image type="content" source="./media/enable-tag-inheritance/automatically-apply-tags-new-usage-data-billing-profile.png" alt-text="Screenshot showing the Automatically apply subscription and resource group tags to new data option for a billing profile." lightbox="./media/enable-tag-inheritance/automatically-apply-tags-new-usage-data-billing-profile.png":::
6570

71+
After tag inheritance is enabled, billing profile, invoice section, subscription, and resource group tags are applied to child resource usage records for the current month within 24 hours.
72+
6673
### To enable tag inheritance in the Azure portal for a subscription
6774

6875
1. In the Azure portal, search for **Cost Management** and select it (the green hexagon-shaped symbol, *not* Cost Management + Billing).
@@ -75,19 +82,27 @@ You can enable the tag inheritance setting in the Azure portal. You apply the se
7582

7683
## Choose between resource and inherited tags
7784

78-
When a resource tag matches the resource group or subscription tag being applied, the resource tag is applied to its usage record by default. You can change the default behavior to have the subscription or resource group tag override the resource tag.
85+
When a resource tag matches the inherited tag being applied, the resource tag is applied to its usage record by default. You can change the default behavior to have the inherited tag override the resource tag.
86+
87+
**For EA customers**:
7988

8089
In the Tag inheritance window, select the **Use the subscription or resource group tag** option.
8190

82-
:::image type="content" source="./media/enable-tag-inheritance/use-subscription-resource-group-tag.png" alt-text="Screenshot showing the override options." :::
91+
:::image type="content" source="./media/enable-tag-inheritance/use-subscription-resource-group-tag.png" alt-text="Screenshot showing the inherited tag option selected for EA customers." :::
92+
93+
**For MCA customers**:
94+
95+
In the tag inheritance window, select the **Use the inherited tag** option.
96+
97+
:::image type="content" source="./media/enable-tag-inheritance/tag-inheritance-use-inherited-tag.png" alt-text="Screenshot showing the inherited tag option selected for MCA customers." lightbox="./media/enable-tag-inheritance/tag-inheritance-use-inherited-tag.png" :::
8398

8499
Let's look at an example of how a resource tag gets applied. In the following diagram, resource 4 and resource group 2 have the same tag: *App*. Because the user chose to keep the resource tag, usage record 4 is updated with the resource tag value *E2E*.
85100

86101
:::image type="content" source="./media/enable-tag-inheritance/tag-example-02.svg" alt-text="Example diagram showing how a resource tag gets applied." border="false" lightbox="./media/enable-tag-inheritance/tag-example-02.svg":::
87102

88103
Let's look at another example where a resource tag gets overridden. In the following diagram, resource 4 and resource group 2 have the same tag: **App**. Because the user chose to use the resource group or subscription tag, usage record 4 is updated with the resource group tag value, which is *backend*¹.
89104

90-
¹ When the subscription and resource group tags are the same as the resource tag and you’ve selected the **Use the subscription or resource group tag** option, the subscription tag is used.
105+
¹ When the subscription and resource group tags are the same as the resource tag and you select the **Use the subscription or resource group tag** option, the subscription tag is used.
91106

92107
:::image type="content" source="./media/enable-tag-inheritance/tag-example-03.svg" alt-text="Example diagram showing how a resource tag gets overridden." border="false" lightbox="./media/enable-tag-inheritance/tag-example-03.svg":::
93108

@@ -97,14 +112,14 @@ After the tag inheritance setting is enabled, it takes about 8-24 hours for the
97112

98113
For example, if the tag inheritance setting is enabled on October 20, child resource usage records are updated from October 1 using the tags that existed on October 20.
99114

100-
Similarly, if the tag inheritance setting is disabled, the inherited tags will be removed from the usage records for the current month.
115+
Similarly, if the tag inheritance setting is disabled, the inherited tags are removed from the usage records for the current month.
101116

102117
> [!NOTE]
103118
> If there are purchases or resources that don’t emit usage at a subscription scope, they will not have the subscription tags applied even if the setting is enabled.
104119
105120
## View costs grouped by tags
106121

107-
You can use cost analysis to view the costs grouped by tags.
122+
You can use Cost analysis to view the costs grouped by tags.
108123

109124
1. In the Azure portal, navigate to **Cost Management**.
110125
1. In the left menu, select **Cost Analysis**.
398 KB
Loading
293 KB
Loading
Loading
22.4 KB
Loading

articles/cost-management-billing/costs/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,6 +171,8 @@
171171
items:
172172
- name: Group and allocate costs using tag inheritance
173173
href: enable-tag-inheritance.md
174+
- name: Apply billing tags
175+
href: billing-tags.md
174176
- name: Split shared costs
175177
href: allocate-costs.md
176178
- name: Reference

0 commit comments

Comments
 (0)