Managing the monthly spend on cloud resources (e.g. Azure) is hard. It gets harder for the Spend Master (e.g. SysAdmins) when developers add services without sending an email to aid in reconciliation.
Azure has a nice tool for managing its own costs, called the Cost Analysis. You can break down costs per resource group, resource type and many other aspects in Azure.
Note: If your subscription is a Microsoft Sponsored account, you can't use the Cost Analysis tool to break down your costs, unfortunately. Microsoft has this planned for the future, but it's not here yet.
Even with Cost Analysis, Developers with enough permissions (e.g. Contributor permissions to a Resource Group) are able to create resources without the Spend Master knowing, and this will lead to budget and spending problems at the end of the billing cycle.
For everyone to be on the same page, the process a developer should follow is:
I would like you to provision a new Azure Resource for xx
Project details:
Total: {{AUD$}} per month

David
<As per SSW Rule: https://www.ssw.com.au/rules/manage-costs-azure>
Figure: Daily costs by category