Cost governance is a structure, then a cadence
Azure spend becomes a problem the month after a migration, when the first full invoice arrives and nobody can say which team, product or environment produced which line. Microsoft Cost Management is the native tool for the answer: Cost analysis for ad hoc exploration, Power BI for deeper reporting, and exports and the Cost Details API for feeding cost data into external systems (Microsoft Learn, What is Microsoft Cost Management, accessed 2026-10-20). The tool only reports what the environment is organized to reveal, so EPC Group builds cost governance in a fixed order: a management group and subscription hierarchy that matches who pays, a tagging standard that Azure Policy enforces, budgets and alerts at each scope, commitment purchases only after right-sizing, and a monthly review with the people who own the workloads. EPC Group's Azure cloud services practice sets this up as part of the landing zone, before the first production workload moves.
Management groups and subscriptions shape visibility
Cost Management works on scopes. Azure RBAC scopes are management groups, subscriptions, resource groups and resources; billing scopes are the agreement-level containers such as an Enterprise Agreement enrollment or a Microsoft Customer Agreement billing profile; and a role assigned at a scope applies to its child scopes (Microsoft Learn, Understand and work with scopes, accessed 2026-10-20). Management groups sit above subscriptions: a directory supports 10,000 of them, a tree supports up to six levels of depth below the root, and each management group or subscription has only one parent (Microsoft Learn, What are Azure management groups?, accessed 2026-10-20).
Two behaviors matter for reporting. Management group costs are returned for the subscriptions currently in the hierarchy, so when a subscription moves, all of its historical cost moves with it, and management groups are not included in cost details (Microsoft Learn, What is Microsoft Cost Management, accessed 2026-10-20). Microsoft also notes that management groups are not currently supported in Cost Management features for Microsoft Customer Agreement subscriptions (Microsoft Learn, Understand and work with scopes, accessed 2026-10-20), so for those clients EPC Group reports through billing profiles and invoice sections instead. In both cases the design rule is the same: one subscription per workload and environment, grouped under management groups for each business unit, so that cost visibility follows accountability.
A tagging standard that makes chargeback possible
Microsoft's Cloud Adoption Framework organizes tags into functional, classification, accounting, purpose and ownership categories, and names accounting tags such as department, program and region as the basis for chargeback, showback and budget management (Microsoft Learn, Define your tagging strategy, accessed 2026-10-20). Its cost-tracking guidance lists the tags companies most often need: business unit, department, billing code, geography, environment, project, and workload or application (Microsoft Learn, Track costs across business units, environments, or projects, accessed 2026-10-20). EPC Group makes four of these mandatory, owner, cost center, environment and application, and leaves the rest optional, because a short standard that is always applied beats a long one that is not.
Enforcement closes the gap. Built-in Azure Policy definitions include Require a tag and its value on resource groups, with a deny effect, and Inherit a tag from the resource group, with a modify effect that also supports remediation tasks for existing resources (Microsoft Learn, Assign policy definitions for tag compliance, accessed 2026-10-20). Cost data has its own constraints: tags must be applied directly to resources, some resources do not include tags in usage data, and tags are not applied to historical data (Microsoft Learn, Understand Cost Management data, accessed 2026-10-20). Tag inheritance in Cost Management solves most of this by applying subscription and resource group tags to child usage records, and cost allocation rules split shared-service costs across subscriptions, resource groups or tags (Microsoft Learn, Introduction to cost allocation, accessed 2026-10-20).
Budgets, forecast alerts and anomaly alerts
Budgets in Cost Management notify; they never stop resources or consumption. A budget needs at least one threshold, expressed as a percentage of the budget, and one email address, and can include up to five thresholds and five addresses. Alerts can be based on actual or forecasted cost, cost data typically arrives within 8 to 24 hours, budgets are evaluated every 24 hours, and a budget resets monthly, quarterly or annually until its expiration date. At subscription and resource group scope a budget can also call an Azure Monitor action group (Microsoft Learn, Tutorial: Create and manage budgets, accessed 2026-10-20), which Microsoft shows driving automation such as stopping virtual machines in a noncritical resource group (Microsoft Learn, Manage costs with budgets, accessed 2026-10-20).
Anomaly detection adds the alert that a fixed threshold cannot give. Cost anomalies are evaluated daily for each subscription against a forecast built from the previous 60 days, detection runs 36 hours after the end of the day, and anomaly alert rules are created at subscription scope with a limit of five per subscription (Microsoft Learn, Identify anomalies and unexpected changes in cost, accessed 2026-10-20). EPC Group's pattern is a budget per subscription with a forecast alert set below the first actual-cost alert, an anomaly alert routed to a shared mailbox that the operations team watches, and an action group only where the workload owner has agreed what automation may do.
Reservations or savings plans
Microsoft offers two commitment mechanisms, each for one or three years. A reservation commits to a specific compute instance type or family in a specific region and suits workloads that run continuously with no expected change in instance type, family or region. A savings plan commits to an hourly spend on eligible compute services across all regions and suits workloads that are dynamic or shifting between instance families, services or regions. Microsoft's recommended sequence is to right-size first, then exchange underused reservations, trade in underused reservations for savings plans where usage is variable, buy new reservations only for stable workloads, and add savings plans last, sized to the cleaned baseline (Microsoft Learn, Decide between a savings plan and a reservation, accessed 2026-10-20).
Two further rules shape the purchase. When both apply to the same usage, Azure applies reservation benefits first (Microsoft Learn, How a savings plan discount is applied, accessed 2026-10-20). And after buying either one, Microsoft advises allowing at least 7 days for recommendations to reflect the purchase before considering the other, and avoiding buying both at the same time (Microsoft Learn, Savings plan recommendations, accessed 2026-10-20). EPC Group buys commitments in that order and records the scope of each one, since a scope that is too narrow is a common cause of low utilization.
The monthly cost review
The structure above produces data; the monthly review turns it into decisions. Microsoft's anomaly guidance describes the habit: review costs periodically with detailed breakdowns and Cost analysis smart views, save custom views for specific workloads, and review each anomaly with the engineers who manage the resources, since some detected anomalies are planned changes (Microsoft Learn, Identify anomalies and unexpected changes in cost, accessed 2026-10-20). Scheduled exports to Azure Storage feed the same data into Power BI or a finance system without manual downloads (Microsoft Learn, How to optimize your cloud investment with Cost Management, accessed 2026-10-20). EPC Group runs the review as a standing agenda: spend by management group and accounting tag against budget, the untagged bucket and who owns it, every anomaly and its cause, reservation and savings plan utilization, open right-sizing recommendations, and a dated action list per workload owner that opens the following month's meeting.
Documented work
ANON-CASES: EPC Group engagement data for Azure cost governance covers mid-size and large organizations in healthcare, financial services and manufacturing that moved workloads to Azure and needed management group hierarchies, Azure Policy tag enforcement, budget and anomaly alerting, and a monthly review with finance, delivered by the firm's cloud migration and managed Microsoft services practices. Client names are not published here. Engagements are described by industry and organization size only, and no outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.
Primary sources
- What is Microsoft Cost Management — Microsoft Learn, accessed 2026-10-20
- Understand and work with scopes — Microsoft Learn, accessed 2026-10-20
- What are Azure management groups? — Microsoft Learn, accessed 2026-10-20
- Define your tagging strategy — Microsoft Learn, accessed 2026-10-20
- Track costs across business units, environments, or projects — Microsoft Learn, accessed 2026-10-20
- Assign policy definitions for tag compliance — Microsoft Learn, accessed 2026-10-20
- Understand Cost Management data — Microsoft Learn, accessed 2026-10-20
- Group and allocate costs using tag inheritance — Microsoft Learn, accessed 2026-10-20
- Introduction to cost allocation — Microsoft Learn, accessed 2026-10-20
- Tutorial: Create and manage budgets — Microsoft Learn, accessed 2026-10-20
- Manage costs with budgets — Microsoft Learn, accessed 2026-10-20
- Identify anomalies and unexpected changes in cost — Microsoft Learn, accessed 2026-10-20
- Decide between a savings plan and a reservation — Microsoft Learn, accessed 2026-10-20
- How a savings plan discount is applied — Microsoft Learn, accessed 2026-10-20
- Savings plan recommendations — Microsoft Learn, accessed 2026-10-20
- How to optimize your cloud investment with Cost Management — Microsoft Learn, accessed 2026-10-20
Frequently Asked Questions
How do management groups and subscriptions shape cost visibility?
Cost Management shows costs at any scope a user can access, and roles assigned at a scope apply to its child scopes; management groups organize subscriptions into a tree of up to six levels below the root (Microsoft Learn, Understand and work with scopes, accessed 2026-10-20). Management group costs are returned for the subscriptions currently in the hierarchy, so moving a subscription moves its historical cost, and management groups are not included in cost details (Microsoft Learn, What is Microsoft Cost Management, accessed 2026-10-20). Microsoft notes that management groups are not currently supported in Cost Management for Microsoft Customer Agreement subscriptions. EPC Group designs the hierarchy around who pays.
What tagging standard makes chargeback possible?
Microsoft recommends accounting tags such as department, program and region, plus ownership tags such as business unit and operations team, and functional tags such as application, environment and tier (Microsoft Learn, Define your tagging strategy, accessed 2026-10-20). Tags must be applied directly to resources to appear in usage data, and some resources do not emit tags (Microsoft Learn, Understand Cost Management data, accessed 2026-10-20), so tag inheritance in Cost Management applies subscription and resource group tags to child usage records (Microsoft Learn, Group and allocate costs using tag inheritance, accessed 2026-10-20). EPC Group enforces four mandatory tags with Azure Policy and leaves the rest optional.
How are budgets and alerts configured?
A budget needs at least one threshold as a percentage of the budget and an email address, and can hold up to five thresholds and five addresses; alerts can be based on actual or forecasted cost, and budgets reset monthly, quarterly or annually (Microsoft Learn, Tutorial: Create and manage budgets, accessed 2026-10-20). Budgets notify but never stop resources, and action groups at subscription and resource group scope can trigger automation. Anomaly alerts are created per subscription and compare each day to a forecast built from the previous 60 days (Microsoft Learn, Identify anomalies and unexpected changes in cost, accessed 2026-10-20). EPC Group sets a forecast alert below every actual-cost alert.
Reservations or savings plans: how to choose (Microsoft, attributed)?
Microsoft describes a reservation as a commitment to a specific instance type or family in a specific region for one or three years, suited to stable workloads that run continuously, and a savings plan as an hourly spend commitment across eligible compute services in all regions, suited to dynamic or evolving workloads. Its recommended sequence is to right-size first, exchange or trade in underused reservations, then buy new reservations and savings plans sized to a clean baseline (Microsoft Learn, Decide between a savings plan and a reservation, accessed 2026-10-20). When both apply, Azure applies reservation benefits first (Microsoft Learn, How a savings plan discount is applied, accessed 2026-10-20).
What does a monthly cost review cover?
Microsoft recommends reviewing costs periodically with cost breakdowns and Cost analysis smart views, saving views for key workloads and reviewing anomalies with the engineers who own the resources (Microsoft Learn, Identify anomalies and unexpected changes in cost, accessed 2026-10-20). Exports to Azure Storage feed external reporting such as Power BI (Microsoft Learn, How to optimize your cloud investment with Cost Management, accessed 2026-10-20). EPC Group reviews spend by management group and tag against budget, the untagged bucket, anomalies and their causes, reservation and savings plan utilization, Azure Advisor recommendations, and the actions owed by each workload owner before next month.
Talk to a senior architect
If your Azure invoice arrives before anyone can explain it, a 30-minute discovery call with a senior EPC Group architect covers the hierarchy, the tag standard, the budget and alert design, and the order in which to consider commitments. See the Azure cloud services service hub for engagement structures.
Email contact@epcgroup.net or call 888-381-9725.
a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.