We consulted Randall Crippen, Azure Cloud Architect at COMPAREX, to gain a better understanding of what challenges exist for organizations that are in the early stages of Azure adoption, or those looking to see if Azure is the right fit for them.
What do you feel is the biggest concern organizations utilizing Azure have in regard to their investment?
Typically, the largest concern customers face when utilizing Azure’s portfolio of over 200 services is whether or not they are using the correct service and doing so in accordance with Microsoft best practices. Anyone is able to spin up a virtual machine or cloud service but making sure that service remains available, doesn’t incur data loss, and makes the most of each euro or dollar spent is the larger challenge.
In your experience, where do organizations using Azure need support and/or guidance?
Support is by far the number one need companies face. Customers want a single place to call not only when there are issues with their environment, but even when they are in the planning and architectural phases to be sure that they are doing things correctly. The ability to work through the various considerations and challenges is paramount to their successful adoption of cloud services.
Are there any “gotchas” that you run across frequently when helping organizations optimize their Azure investment?
There are many considerations to take into account when determining the Azure services to use, how to use them, and how to configure them. Some of the common ones are as follows.
Virtual Networks: What kinds of firewalls does the customer use and what limitations does that impose on our connectivity?
Virtual Machines: What considerations do we need to take into account for availability and resiliency and how does that impact our costs?
SQL Server: When it comes to VMs, there are multiple technologies to consider when thinking about availability, replication, and disaster recovery. Selecting a technology can have implications on both the performance of the application, RTOs and RPOs, as well as costs of licensing that SQL instance. In addition, there are considerations on what type of Azure service to use (IaaS or PaaS), which will change how easily these things are accomplished and what the associated costs are.
Monitoring and Analytics: Customers can deploy a workload or application relatively easily on Azure services, but commonly need tools to monitor those applications – whether its performance, availability, or logging errors. Customers need an easy way to troubleshoot issues and it isn’t always obvious how to accomplish this, but there are services within the Azure platform specifically designed for this purpose such as Visual Studio Application Insights.
Service Selection: Many of the factors listed above along with something as simple as choosing an A Series VM vs a D Series VM can have a big impact on the overall cost, performance, and, at the end of the day, customer experience when using the Azure platform so having an advisory resource to lean on for these types of questions is important to the customer’s success both technically speaking and monetarily.
Thanks very much, Randall, for your insight!