The Safe Bet Isn't Safe Anymore

Microsoft is reportedly training its salespeople to pitch against OpenAI and Anthropic. The same OpenAI it invested $13 billion in. About-face? Not quite...

For 18 months I've told clients that the Microsoft ecosystem was the lowest-risk enterprise AI play. Azure, Copilot, native integrations, a compliance posture that most enterprise procurement teams could actually approve. That guidance wasn't wrong and made sense given they were already a customer. But the landscape around it has shifted in ways that matter. Microsoft is developing competing models and swapping out OpenAI and Anthropic from Word and Excel. Meanwhile, Google, Salesforce, Snowflake, and ServiceNow are building a counter-protocol to Anthropic and OpenAI's model layer. The platform war that everyone thought was mostly settled is entering a second, noisier chapter.

The clients I'm most worried about are the ones who heard "Microsoft is safe" and stopped thinking. They built on a single proprietary stack, deeply integrated, and assumed the vendor relationship was stable. It probably still is, relatively speaking. But "relatively stable" is doing a lot of work in that sentence now. I've seen this pattern before in enterprise software: the moment a dominant vendor starts competing with its own partners, the integration tax goes up, and the flexibility goes down. We're early in that dynamic here, and the organizations that recognized it early are the ones quietly making sure their architecture has options. Flexibility is key (especially given how old I am now...).

The safe bet was never about picking a vendor. It was about picking an architectural approach that survives vendor consolidation and model commoditization. Open standards, API-first integration, workloads that aren't locked to a single model or platform. My guidance hasn't changed. The urgency behind it just got easier to explain.

If your AI strategy is "we use X," that's a starting point. What happens to your roadmap when the vendor replaces the model underneath your workflow, or starts competing with the partner ecosystem you built on? Map the dependency. It's a short exercise and a clarifying one.