As organisations mature their FinOps practice on Azure, cost visibility alone is no longer sufficient. Finance teams need to allocate cloud costs to the correct business units, and engineering teams need to understand the financial impact of their architectural decisions. This is where chargeback and showback models become essential.
This post covers the difference between the two models and provides a practical approach to implementing cost allocation in Azure.
1. Showback vs Chargeback
Both models serve the same purpose of attributing cloud costs to the teams or business units that generate them, but they differ in consequence:
- Showback: teams are shown their costs for awareness and accountability, but the costs are not transferred to their budget. This is the appropriate starting point for most organisations.
- Chargeback: costs are formally allocated and transferred to the consuming team's budget. This requires financial systems integration and strong tagging discipline before it is viable.
I recommend starting with showback for at least one full quarter before introducing chargeback. Showback surfaces tagging gaps and data quality issues that would cause chargeback disputes if unaddressed.
2. Prerequisites: Tagging Strategy
A cost allocation model is only as accurate as the tagging on the resources being measured. Before building any reports, confirm the following tag coverage:
Navigate to Azure Policy > Compliance and filter for any tag-related policy assignments. Look for non-compliant resources and remediate them before proceeding.
The minimum required tags for a cost allocation model are:
| Tag | Purpose |
|---|---|
cost-center | Finance reference code for the owning business unit |
team | Engineering team responsible for the resource |
environment | Separates operational (prod) from non-operational (staging, dev) costs |
workload | The product or service the resource supports |
3. Using Azure Cost Allocation Rules
Azure Cost Management supports Cost Allocation Rules, which allow shared costs (such as a shared networking subscription, a centralised Log Analytics workspace, or a shared API Management instance) to be split and attributed to consuming subscriptions or resource groups.
- Navigate to Cost Management + Billing > Cost Management > Cost allocation (preview)
- Select + Add
- Under Source, select the subscription or resource group containing the shared cost
- Under Targets, define the allocation split, either by fixed percentage or proportional to each target's existing spend
- Select Save
Following is an example allocation scenario:
| Shared Resource | Total Monthly Cost | Allocated To | Split |
|---|---|---|---|
| Hub VNet + Firewall | $1,200 | Production (70%), Non-Prod (30%) | Fixed |
| Centralised Log Analytics | $800 | By each team's ingestion volume | Proportional |
4. Exporting Chargeback Data for Finance Systems
Once allocation rules are configured, the resulting cost data can be exported for integration with finance systems.
Navigate to Cost Management > Exports with the subscription or management group as scope. Create a monthly scheduled export that includes the allocated cost data. The exported CSV includes the allocation split fields, enabling downstream processing to attribute costs to the correct cost centre.
For organisations using Power BI, the Azure Cost Management connector in Power BI Desktop connects directly to the Cost Management API and reflects cost allocation rules in real time.
5. Communicating Results to Stakeholders
The final step is delivering the showback or chargeback report to the relevant teams. Following is a practical distribution approach:
- Engineering teams: monthly cost summary by resource group, shared via a Power BI report or a Teams message generated by a Logic App triggered on export delivery
- Finance: monthly CSV export delivered to a shared storage account, consumed by the existing financial reporting process
- Leadership: a quarterly Workbook summary at management group scope showing total cloud spend by business unit and trend over time
Summary
A robust cost allocation model on Azure requires clean tagging, cost allocation rules for shared resources, and a consistent export and distribution process. Starting with showback builds the data quality and organisational habits needed to make chargeback viable, ensuring there are no disputes when costs are formally transferred to business unit budgets.
