One of the most common concerns raised when any organization is planning a move to the Cloud is Cost. Unlike Microsoft 365 where you have set costs based on license consumption, there are a number of variables to be considered when moving to any Cloud Provider (be that Azure, AWS or others).
For example, let’s say we want to put a Virtual Machine in the Cloud. Its sounds easy — if this was on-premise, you would provision storage on your SAN, assign CPU and Memory, assign an IP Address, and if required purchase a license for the OS and other additional software that will be running on the Virtual Machine.
All of the above still holds true when creating a Virtual Machine in the Cloud, but there are also other considerations, such as:
- What Storage Tier will the VM run on (Standard HDD, Standard SSD, Premium SSD)
- How HA do we need the VM to be (Locally Redundant, Geographically Redundant)
- Does the VM need to be scalable based on demand/local (Auto Scaling/Scale Sets)
In an on-premise environment, there needs to be an up-front investment (CAPEX) to make that feasible. When running with a Cloud Provider such as Azure, this uses an on-demand model (OPEX). This is where costs can mount.
There are a number of ways to tackle this. The Azure TCO (Total Cost of Ownership) Calculator gives an estimate of costs of moving infrastructure to the cloud. The important word there is “estimate”.
So you’ve created your VM with all of the settings you need, and the TCO has given you the estimate for what total “should” be on your monthly invoice. Azure Cost Management and Budgets can provide you with forecasting and alerts with real-time analysis of your projected monthly spend. That way, there are no nasty surprises when the invoice arrives!
Firstly, lets create our Azure Account. Browse the Azure Portal to sign up. You get:
- 12 months of free services
- $200 credit for 30 days
- 25 always free services
Azure Portal Method
When your account is set up, go to https://portal.azure.com to sign in:
Once you’ve signed in, you can search for “Cost Management and Billing”
From the “Cost Management + Billing” page, select “Cost Management” from the menu:
This brings us into the Cost Management Page for our Azure Subscription:
One important thing to note here before we go any further. We can see at the top of the screen that the “Scope” for the Cost Management is the Azure Subscription. In Azure, Budgets can be applied to the following:
- Management Group — these allow you to manage multiple subscriptions
- Subscriptions — Default
- Resource Groups — Logical groups of related resources that are deployed together. These can be assigned to Departments or Geographical Locations
Also, we can create monthly, quarterly or annual budgets. For the purposes of this demo (and the entire 100 Days), I’ll be using Subscriptions with a monthly budget.
Click on the “Budgets” menu option, and then click “Add”:
This brings us into the “Create Budget” menu. Fill in the required details and set a Budget Amount — I’m going to set €50 as my monthly budget:
Next, we need to set up Alert Conditions and email recipients. In Alert Conditions, we can see from the “Type” field that we can choose either Actual or Forecasted:
- Actual Alerts are generated when the monthly spend reaches the alert condition.
- Forecasted Alerts are generated in advance when Azure calculates that you are likely to exceed the alert condition based on the services you are using
Once you have your Alert Conditions configured, add one or more Alert Recipients who will receive alerts based on your conditions. Then click “Create”:
And now we see our budget was created successfully!
So, that’s the Azure Portal way to do it. There are 2 other ways, the first is using Azure PowerShell.
Azure PowerShell Method
Firstly, we need open Windows PowerShell, and install the Azure Module. To do this, run:
install-module -name Az
This will install all packages and modules we require to manage Azure from PowerShell.
We can then run the following commands to create our Budget:
will prompt us to log on to our subscription:
Once we are logged in, this will return details of our Subscription:
to check what level we are at in the subscription:
Now, we can run the following command to create a new budget:
New-AzConsumptionBudget -Amount 100 -Name TestPSBudget -Category Cost -StartDate 2021–09–17 -TimeGrain Monthly -EndDate 2023–09–17 -ContactEmail email@example.com -NotificationKey Key1 -NotificationThreshold 0.8 -NotificationEnabled
But it throws an error! Why?
It turns out that after a bit of digging, you can only set a budget using PowerShell if your subscription is part of an Enterprise Agreement. So I’m afraid because I’m using a free account here, its not going to work ☹.
Full documentation can be found at this link:
OK so lets move on to option 3, which is using Azure Resource Manager (ARM) Templates.
Azure Resource Manager (ARM) Templates Method
To do this, go to the following site:
And click on the “Deploy to Azure” button:
This will re-direct us into the Azure Portal and allow us to fill in the fields required to create our Budget:
And that is how we create a Budget (3 ways) in Azure. See you on Day 3!!
Hope you enjoyed this post, until next time!!