Skip to main content


Align your managed disk to Microsoft standard tiering to optimise your spending

“Managed” disk has been around in Azure for a few years now and is the standard for deploying with VMs. I started deploying VMs when “unmanaged” disk was the standard and you had to plan carefully how many disk/s, IOPS you needed and strategically place those disks in the right storage account to ensure that it can deliver those performances. We were using spreadsheets to help us track which disk was in which storage account and making sure we weren’t hitting the max IOPS limits that the storage account could delivery. Over time it just got very very messy and complex to manage.  With the introduction of “managed” disk it took all those pains away and Azure was dealing with them in the backend. We could change from SSD to HDD and vice versa easily, snapshots were just a few clicks, we didn’t need to search in storage accounts for orphaned disk where we were paying for because we forgot to decommission them as part of the VM. With managed disk we just had to work out how much disk space
Recent posts

Using Windows Terminal and customising it

As a system administrator, you will most likely have multiple command line terminal tools that you use to help manage your systems. By the end of the day, you will end up with a screen full of terminals like the one below  You can see that there are multiple windows for PowerShell, putty, cmd. It gets messy and can you get lost over time which window is for which especially if you work in multiple environments i.e., production, pre-production etc. Here comes……. Windows Terminal from Microsoft which is an open-source project and you can contribute to it too if you fancy. It’s an application where you are able to open multi shells and keep them as tabs instead of multiple windows. You can think of it like your web browser where you have multi tabs and each tab is at a different location/page. You can download this application from Microsoft store and the system requirements are simple - Windows 10 version 18362.0 or higher Once installed upon your first launch you will see that it defaul

Reporting on an Azure IaaS VM cost – have I included everything?

We had arranged our Azure subscriptions to have each resource group representing an application so that all resources that belonged to an application are deployed within a resource group. This enabled us make it easier to grant management access rights to resources on per application basis. We were able to do costing reporting easier for each application as we just needed to report at the resource group level which would then include all the resources for the application. Then when we wanted to decommission the application we could just delete the resource group which would delete all the resources related to the application. Over time, application owners wanted to drill down further with costing and to know the actual cost on a per server basis within the application. By using Azure cost management, you can filter down to the resource level which you can see that I have selected for my resource “dc001 (Microsoft.compute/virtualmachines)” and the cost is around 32p for January 2021. No

PowerBi Azure Cost Management exposing Tag values to be used

I wrote an article about exposing tags to be used in PowerBi using the connector “Microsoft Azure Consumption Insights (Beta)” ( Using Azure tags in your powerbi reporting ). If you recall there is a warning message when you use the connector which states that it is still under development. It seems like there is no development for this connector as it has been in “beta” for a long time. I noticed that there is a new connector called “Azure Cost Management” which I will walk through which seems easier to configure. I googled around and decided to combine all my findings in to one document. First as we are connecting via our Enterprise agreement, we need to ensure at minimum that we have “Enterprise Administrator (read only)” permissions within the EA portal. Once we have that we should be able login to and see our enrollment number on the top left of the portal which we will need to note down. When you start up PowerBi desktop if you get the start-up screen then se

Going further back for Azure Consumption in PowerBi

When you connect PowerBi via Microsoft Azure Consumption Insights (Beta) connector you will get the last month of consumption data and you may want to report further back. There is a way to do it where you can report back up to a maximum of 36 months. If you follow my article up to step "On the menu bar select "Transform data > Transform data" first. On the menu bar select "Transform data > Transform data"     Under the "Home" ribbon locate and select "Advanced Editor" You should see the query that has been applied which is currently based on this format let     Source = MicrosoftAzureConsumptionInsights.Tables(EnrollmentNumber, []),     usagedetails = Source{[Key="usagedetails"]}[Data] in     usagedetails We would need to change it to let     enrollmentNumber = "EnrollmentNumber",     optionalParameters = [ numberOfMonth = 3, dataType = "De

Changing Service Admin Account in your Azure Subscription

By default, when you deploy your new Azure subscription the "Service administrator" is the same as "Account administrator" which means that this account has permissions to both the EA portal and the Azure portal. For us we had to change this as Azure Account team didn't need access to the Azure portal. To change this, it was a simple process as both the Service administrator and Account administrator is the same user.    First go to with the account that you used to sign up for the subscription then head to subscriptions and locate your subscription. If we want to check to make sure you are logged in as the "Service Administrator" then click "subscriptions" then go to "Access control (IAM)" then "Classic administrators" tab and you should see the your account there with the role of "Service administrator". As we are still in the subscription blade click on "properties" and clic