Episode Details

We’re promised six clean stages in Azure’s Cloud Adoption Framework: Strategy, Plan, Ready, Adopt, Govern, Manage. Sounds simple, right? Microsoft technically frames CAF as foundational phases plus ongoing operational disciplines, but let’s be honest — everyone just wants to know what breaks in the real world. I’ll focus on the two that trip people fastest: Strategy and Plan. In practice, Strategy turns into wish lists, Ready turns into turf wars over networking, and Governance usually appears only after an auditor throws a fit. Subscribe at m365 dot show for templates that don’t rot in SharePoint. So let’s start where it all falls apart: that first Strategy doc.The 'Strategy' Stage Nobody Reads TwiceThe so‑called Strategy phase is where most cloud journeys wobble before they even get going. On paper, Microsoft says this step is about documenting your motivations and outcomes. That’s fair. In reality, the “strategy doc” usually reads like someone stuffed a bingo card full of buzzwords—digital transformation, future‑proofing, innovation at scale—and called it a plan. It might look slick on a slide, but it doesn’t tell anyone what to actually build. The problem is simple: teams keep it too high‑level. Without measurable outcomes and a real link to workloads, the document is just poetry. A CIO can say, “move faster with AI,” but without naming the application or service, admins are left shrugging. Should they buy GPUs, rewrite a legacy app, or just glue a chatbot into Outlook signatures? If the words can mean anything, they end up meaning nothing. Finance spots the emptiness right away. They’re staring at fluffy phrases like “greater agility” and thinking, “where are the numbers?” And they’re right. CAF guidance and every piece of industry research says the same thing: strategies stall when leaders don’t pin outcomes to actual workloads and measurable business impact. If your only goal is “be more agile,” you won’t get far—because no one funds or builds around vibes. This is why real strategy should sound less like a vision statement and more like a to‑do list with metrics attached. One strong example: “Migrate identified SQL workloads onto Azure SQL Managed Instance to cut on‑prem licensing costs and simplify operations.” That sentence gives leadership something to measure, tells admins what Azure service to prepare, and gives finance a stake in the outcome. Compare that to “future‑proof our data layer” and tell me which one actually survives past the kickoff call. The CAF makes this easier if you actually pick up its own tools. There’s a strategy and plan template, plus the Cloud Adoption Strategy Evaluator, both of which are designed to help turn “motivations” into measurable business outcomes. Not fun to fill out, sure, but those worksheets force clarity. They ask questions like: What’s the business result? What motivates this migration? What’s the cost pattern? Suddenly, your strategy ties to metrics finance can understand and guardrails engineering can build against. When teams skip that, the fallout spreads fast. The landing zone design becomes a mess because nobody knows which workloads will use it. Subscription and networking debates drag on endlessly because no one agreed what success looks like. Security baselines stay abstract until something breaks in production. Everything downstream suffers from the fact that Strategy was written as copy‑paste marketing instead of a real playbook. I’ve watched organizations crash CAF this way over and over. And every time, the pattern is the same: endless governance fights, firefighting in adoption, endless meetings where each group argues, “well I thought…” None of this is because Azure doesn’t work. It’s because the business strategy wasn’t grounded in what to migrate, why it mattered, and what to measure. Building a tighter strategy doesn’t mean writing a 50‑page appendix of jargon. It means translating leadership’s slogans into bite‑sized commitments. Instead of “we’ll innovate