Cost - Do you manage the cost of your Azure resources?

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.

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:

1. Use the Azure calculator - work out the monthly resource $ price
2. Email the Spend Master with $ and a request to create resources in Azure, like the below:

To:	Spend Master
Subject:	Purchase Please - Azure Resource Request for {{product/service}}

Hi Spend Master aka SysAdmins

I would like you to provision a new Azure Resource for xx

• Azure Resource needed: I would like to create a new App Service Plan
• Azure Calculator link: {{add link}}
• Environment: {{add Dev/Staging/Prod}}

Project details:

• Project Name: A new project called {{add project name}}
• Project Description (The SysAdmin will copy this info to the Azure Tag): {{add description}}
• Project URL (e.g. Azure DevOps / Github): {{add URL}}

Total: {{AUD$}} per month

1. Please approve

David

<As per SSW Rule: https://www.ssw.com.au/rules/manage-costs-azure>

3. Add a tag of cost-category to each of your resources. This will allow you to see the daily costs of your Azure resources based on whether they are Core, Value adding or Dev/Test. Then you can quickly turn off resources to save money if you require. It also helps you to see where money is disappearing.