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/cost-management-billing/costs/cost-allocation-introduction.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,8 +45,8 @@ Subscriptions are a way of grouping Azure resources that might or might not shar
45
45
46
46
You can view and manage your subscriptions in the Azure portal, PowerShell, CLI, or REST API. In the Azure portal, you can also use tools like Cost Management and Advisor to monitor and optimize your subscription costs.
@@ -86,7 +86,7 @@ For more information, watch the [Cost Management setup, organization, and taggin
86
86
87
87
## Tags
88
88
89
-
Tags are key-value pairs that you can apply to Azure resources to group and allocate costs based on business needs. They're a great way to augment the resources and usage data with business context. You can create [Azure policies](../governance/policy/tutorials/create-and-manage.md) to ensure that all your resources are tagged in a certain way to comply with your tagging strategy.
89
+
Tags are key-value pairs that you can apply to Azure resources to group and allocate costs based on business needs. They're a great way to augment the resources and usage data with business context. You can create [Azure policies](../../governance/policy/tutorials/create-and-manage.md) to ensure that all your resources are tagged in a certain way to comply with your tagging strategy.
90
90
91
91
However, even with a comprehensive tagging mechanism in place, you might find that some usage records are missing tags because not all Azure resources emit tags in their usage. To ensure all usage records are tagged, enable tag inheritance in Cost Management to apply subscription and resource group tags to underlying child resources. You don't need to rely on resources emitting tags in their usage or tag every resource for your cost allocation needs.
92
92
@@ -104,8 +104,8 @@ For more information about how to manage and allocate shared costs, see [Allocat
104
104
105
105
To learn more about defining your tagging strategy, read the following articles:
106
106
107
-
-[Define your tagging strategy](/cloud-adoption-framework/ready/azure-best-practices/resource-tagging)
108
-
-[Develop your naming and tagging strategy for Azure resources](/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging)
107
+
-[Define your tagging strategy](/azure/cloud-adoption-framework/ready/azure-best-practices/resource-tagging)
108
+
-[Develop your naming and tagging strategy for Azure resources](/azure/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging)
0 commit comments