Azure cost visibility,
reconciled to the bill

Azure organises spend through management groups, subscriptions and resource groups, and that hierarchy is usually a reflection of how the platform was built rather than how the business is organised. A subscription can be a team, an environment, a product or an accident of history. Reporting along that axis produces numbers that are technically correct and organisationally meaningless.

Tagging does not rescue this automatically. Tags applied to a resource group are not inherited by the resources inside it unless a policy enforces it, so a governance model that looks complete at the container level can be substantially incomplete at the level the bill is actually charged.

Commitments add a second layer. Reservations and the savings plan for compute overlap in what they can cover, and a reservation’s scope — single subscription or shared — determines which spend it can absorb. Azure Hybrid Benefit changes the economics again through licensing rather than usage, so the same virtual machine can carry very different costs for reasons that are invisible in the usage data.

Finally, Azure Advisor recommends against a usage lookback. That means it can keep recommending reservations for machines that have already been resized or deleted. Taken at face value, a portal total can exceed the spend it claims to optimise — which is precisely the kind of number that destroys credibility when finance checks it.