Azure’s consumption-based model requires attention to detail and continued focus on utilisation and cost. A subtle difference that was not a daily discipline in the more traditional datacentre setting of the past. While this paradigm shift in the way in which organisations utilise compute services is hardly new. . Fun fact “Azure was first introduced at the Professional Developers Conference (PDC) in October 2008 under the codename “Project Red Dog.” It was officially launched as Windows Azure in February 2010 and later renamed Microsoft Azure on March 25, 2014″ It still trips organisations up. When I ask customers if they are happy with their Azure services the common answer is no. When I ask why, the answer nearly always isn’t a level of dissatisfaction with the quality of Azure’s services, it’s a consistent upward spend trend that they aren’t exactly happy with.
Cost savings can be achieved via better deployment, but it’s never as easy as set and forget, requiring reactive measures to curb the current overspend and proactive policy and procedural reform initiatives to ensure future operational activities are not unnecessarily cost incurring.
If you’re feeling like this is resonating, here are some thought provoking hot spots I consistently uncover when helping customers with Azure Cost Optimisation:
- Challenge vendor compute specifications
- Assisted thinking for cost effective compute scenario determination
- Behavioural change
- Acceptable cost control behaviours
- There are no discounts without commitment
Need help or want to learn more? Contact Sales@appcentric.com.au for a free one hour consultation where we can talk specifically about cost control in Azure for your organisation.
