[Root] Access is an advice column for IT professionals.
AWS or Azure? My Team Can’t Decide
Learn how to mediate a team’s cloud debate by evaluating business needs, exploring multi-cloud options, and applying structured decision-making.
[Root] Access is an advice column for questions about IT issues, career moves, and workplace concerns.
Want advice? Submit your questions anonymously with this form.
Dear [Root] Access,
My team is torn between sticking with AWS or switching to Azure. How do I mediate this technical standoff? For context, we're a midsize company in the financial services space .
—Cloud Conflicted
Dear Cloud Conflicted,
Knowing which cloud provider is best for your workload is not always easy, but here are a few thoughts to help you.
1. Find Out What's Motivating the Azure Push
Start by asking why some team members advocate switching to Microsoft Azure . Do specific business or technical requirements drive the push, or could they have a personal preference or bias toward Microsoft products?
2. Explore Multi-Cloud Options
Also, remember you don't have to go all in on a single cloud provider. While you mentioned working for a mid-sized company, it's worth noting that most larger organizations have adopted a multi-cloud strategy . In this model, workloads are distributed based on criteria such as cost-effectiveness or which provider offers the best services for a given workload's specific needs.
3. Establish Clear Decision-Making Criteria
If you truly must decide between Microsoft Azure or AWS, the first step is to define key decision-making criteria. For example, since your organization operates in the financial services space, a significant factor should be which cloud platform will better support your regulatory compliance obligations .
Related:Our Cloud Storage Provider Went Down. Now I’m Rethinking Our Strategy.
In addition to compliance and industry needs, other important criteria might include:
Integration capabilities: How well will the platforms integrate with your current systems?
Cost: What are the upfront or ongoing expenses?
Resiliency and disaster recovery : Which provider offers stronger options for business continuity?
Support: What are the cost and availability of technical support?
Internal expertise: Does your team have more experience with Microsoft technologies or AWS?
4. Perform a Cost-Benefit Analysis
Since you work in the financial services industry, consider approaching this cloud decision similarly to how you would approach other decisions. For example, your organization could perform a cost-benefit analysis to weigh the pros and cons of both Microsoft Azure and AWS.
Remember, no rule says you must limit yourself to just one cloud. You could perform a cost-benefit analysis for each individual workload. This would allow you to compare the costs and benefits of running specific workloads across multiple cloud providers and select the most efficient option for each case.
Related:Harness the Cloud: Critical Benefits of Cloud Computing
5. Use Trial Deployments as Proof of Concept
Another way to build consensus is to conduct trial deployments in Microsoft Azure and AWS. Treat these trials as proof-of-concept projects to assess how well each platform handles specific workloads.
For example, if your organization uses a mission-critical database application, you could deploy it in isolated lab environments within both clouds. After a few weeks, gather data on costs , performance metrics, and other key indicators.
While there is no substitute for real-world testing, you may uncover certain patterns. Microsoft-based workloads (such as those that depend on Active Directory or SQL Server) tend to run better in Azure, as the platform is optimized for Microsoft technologies. Conversely, AWS often excels with workloads that require extreme scalability or heavy third-party integrations.
6. Use a Structured Decision-Making Approach
If the previous methods don't lead to a clear decision, consider adopting a structured approach. Many organizations use a decision matrix when faced with significant choices. A decision matrix is a table that outlines key criteria and assigns weights to each based on their importance. The table produces an overall score to help determine the better option.
Related:We're Swamped With Unused Servers. How Do We Stop the Sprawl?
Another approach is to conduct a SWOT analysis. SWOT stands for Strengths, Weaknesses, Opportunities, and Threats. This analysis involves evaluating both clouds based on these four categories, helping to highlight the pros and cons of each.
Alternatively, take a risk-based approach to decision-making. Identify potential areas of concern for your organization, then assess each cloud platform based on how well it addresses these issues. While many of these concerns will relate to IT security, factors like data sovereignty , the financial health of the cloud provider, and the risk of vendor lock-in should also be considered.
7. Plan for Future Needs
As you evaluate which cloud will best meet your needs, don't focus solely on your current needs. Consider your future needs, as well. The last thing you want is to put yourself in a position where you must undergo another cloud migration in just a year's time.
8. Consider Hiring an Expert Consultant
If your organization still cannot make a decision, consider hiring an outside consultant to help. However, choose someone with an IT and financial services background to ensure they understand your unique challenges and requirements.
Choosing the Right Cloud Provider.png
Read more cloud computing advice:
About the Author
Technology Analyst
Brien Posey is a bestselling technology author, a speaker, and a 20X Microsoft MVP. In addition to his ongoing work in IT, Posey has spent the last several years training as a commercial astronaut candidate in preparation to fly on a mission to study polar mesospheric clouds from space.
You May Also Like