{"id":43487,"date":"2020-11-24T15:00:47","date_gmt":"2020-11-24T14:00:47","guid":{"rendered":""},"modified":"2021-11-26T17:53:36","modified_gmt":"2021-11-26T16:53:36","slug":"managing-bulk-azure-reserved-instances","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-gb\/industry\/blog\/technetuk\/2020\/11\/24\/managing-bulk-azure-reserved-instances\/","title":{"rendered":"Managing bulk Azure Reserved Instances"},"content":{"rendered":"

\"The<\/p>\n

Azure is great for workloads where you want to pay for what you use, as you can save money by switching services off or down-sizing them when you can.<\/p>\n

Over time, as you become a more mature public cloud consumer and more workloads move to production, there may be workloads that need to run constantly. How should you manage these costs?<\/p>\n

 <\/p>\n

Enter Reserved Instances<\/h2>\n

Azure has a feature called Reserved Instances (or RI). RI allow you to commit to a usage pattern over a certain time period, a year or 3 years for example. In this article we will cover Virtual Machine RIs, but RIs can be purchased for many different Azure services.<\/p>\n

So how would you go about creating a Reserved Instance?<\/p>\n

 <\/p>\n

Azure Portal Reservations<\/h2>\n

The Azure Portal has support for RIs. From here, you can browse, create and modify RIs.<\/p>\n

 <\/p>\n

This is a great way to get started, as the visual aspects of the Azure Portal will help you understand the basic concepts, as well as walk you through the purchase process using a shopping cart approach.<\/p>\n

But what if you need to create a lot of RIs? Or create RIs across a number of different subscriptions? The chance of user error clicking through the Portal steps multiple times may be too high.<\/p>\n

For these scenarios, I created the Reserved Instance Helper<\/a>.<\/p>\n

 <\/p>\n

Reserved Instance Helper<\/h2>\n

Within an enterprise, the person responsible for the RIs is probably part of a financial operations team, or FinOps. They may not have programming skills, and unfortunately for them, the only way to access RIs right now is through the Portal, PowerShell, Azure CLI or REST APIs.<\/p>\n

The FinOps team are most likely more comfortable working with Excel sheets than the command line, which is why the Reserved Instance Helper is designed for this kind of team.\u00a0The idea is to use an Excel spreadsheet as the source, making it easy to capture the details of each Virtual Machine RI in a worksheet row.<\/p>\n

I created a PowerShell script to read each row and make the necessary calls to create the RI. To create an RI there are two calls: one to calculate the RI, which creates an Order ID, then purchase the RI referring to the Order ID from the previous step.<\/p>\n

 <\/p>\n

The small print<\/h2>\n

There are a few implementation details to be aware of when working with RIs. Firstly, the name of the RI is free text – there is nothing to prevent you from creating two RIs with the same name. Azure knows they are different because they have unique Reservation IDs, but we poor humans may find it harder to work with multiple RIs with the same name.<\/p>\n

My spreadsheet has an Excel formula to create a name for each RI based on the row in the worksheet. There are also lookups for each of the RI attributes that is based on static values.<\/p>\n

Because the RI name isn\u2019t unique, it would be all too easy to run the spreadsheet multiple times and thereby create multiple copies of the same RI. To prevent this, I added a Purchased copy and set this to Yes after the RI has been created from the row.<\/p>\n

 <\/p>\n

Wait, there\u2019s more!<\/h2>\n

There is something to be aware of when using the command line tools to create RIs, and it’s that the command to purchase the RI actually triggers a workflow. As well as creating the RI, the workflow assigns access rights so that the creator can access the RI. Creating this access right is an asynchronous task, sometimes it completes before the purchase command returns and you don\u2019t notice. Other times it takes longer to complete and hasn\u2019t completed yet when the purchase command returns. In this situation, an error message is returned.<\/p>\n

This might be unsettling as a user, but fear not – when you go to the Azure Portal you will see that the RI has been purchased. In this situation, I considered waiting for the asynchronous access rights assignment to complete by getting the newly purchased RI, but in testing this sometimes took as long as 30 minutes. I figured that a user creating 50 RIs wouldn\u2019t want to wait 25 hours for the script to complete, so right now just accept the errors in the feedback and check the output in the Azure Portal when you are done.<\/p>\n

If you want to see the utility in action, I made a short video:<\/p>\n