Estimated Reading Time: 6 minutes As an Azure Pre Sales or Delivery Architect, there must be lots of pressure on you to find various ways to save/reduce the cost/spend in the cloud. Your KPI and KRA may be also integrated with the cost savings which you can show at the end of the year. How to save the operational cost in Azure, this question is going to be one of the main headache of the CIO organisation going forward, since for the last couple of years we have seen many organizations has moved a significant number of their on-premises workload to Azure/AWS without much planning on the cost saving part. It may be because of the well-known joke in the Azure world where someone had asked the CIO why you are moving to the public cloud and CIO answered, since everyone is moving so we are. Since the original estimates were failing and spend on the azure budget is overshooting month by month, most of the public cloud architect jobs will need this important skill, as a top demanding skill in their role. With the introduction of Azure Advisor and Cost Management, you can get some insight definitely, but there are many things you should plan well in advance before your next deal which can provide a significant lead against your competitors. There are many cost savings measures which you can take and the top 12 initiative I have listed below. And all of them can be planned well in advance during the planning stage of the deal. Once you win the deal and project is in the delivery stage there will be ongoing initiatives to bring the down the Azure spend as well.
- RI’s (Reserved Instances), Pre-pay, on demand, Dedicated Hosts, BYOL etc.
- Usage duration of the Azure Resources. (For Example, if you pause the azure analysis services, you will not be billed)
- Selecting the right storage and using the Storage Pool and Stripped Volumes (IOPS calculation plays a big role here, also selection of storage policy like when data will move to cold and archive storage is important)
- Right Instance types (B Series VM’s etc.)
- Estimation of data volumes for the client proposal (Network capacity planning, ExpressRoute or Site to Site VPN etc.)
- Turn on / Off (Deallocating the VM when not in use.)
- Resize instances/change instance types.
- Scale Up/ Scale Down
- Conversion to PaaS services.
- Public cloud Waste management. (By right tagging the resources with the department which introduces responsibilities against over spending. )
- Low priority VM’s (Already I have explained this in detail in my older blog post.)
- HA planning with a single instance with limited allowed downtime.
You are committing for a longer period of time.
- Capacity planning will become easier for MS because they know that this many numbers of VM’s will be available for a longer commitment.