A Microsoft-centric enterprise asks whether to standardize on AWS or Azure for new workloads. How do you decide?
Short answer
Run a structured evaluation: workload requirements, existing identity and licensing (Entra ID, Windows/SQL licence benefits), team skills, required services and regions, commercial terms, partner ecosystem and exit considerations. Weight criteria with stakeholders, run proofs of concept on representative workloads, and document the decision in an ADR.
Detailed answer
Criteria and typical weights: fit to workload requirements (25%), security/identity integration (15%), cost including licences (20%), skills and hiring (15%), service roadmap and ecosystem (10%), regions/compliance (10%), commercial terms (5%). Microsoft-centric shops often find Azure lower friction (Entra ID, Azure Hybrid Benefit, M365 integration), but specific workload needs or skills may favour AWS. Decide by evidence, not loyalty.
What the interviewer expects
Objective, weighted decision process with PoCs and documentation.
Common mistakes to avoid
Deciding on list prices or personal preference alone.