AWS Just Told Every Hospital CIO That Microsoft Was Right About Agents
Why Amazon's OpenAI Deal Is the Biggest Admission of Infrastructure Defeat in the AI Wars, And What It Means for Healthcare
On February 27, Amazon CEO Andy Jassy went on CNBC with Sam Altman and announced a "Stateful Runtime Environment" that AWS and OpenAI will co-create. A system where AI agents can maintain context, remember prior work, call tools, and access compute. He described it as the next generation of how developers will build AI applications.
Then he said something remarkable. "There's nothing else like that today."
I've been building healthcare AI systems for over 30 years. I built symbolic AI triage engines in 2001, migrated 50+ HIPAA workloads to Azure, and today I advise health systems on mission-critical AI infrastructure. So when the CEO of Amazon makes a claim like that on national television, I pay attention.
And I can tell you he's wrong.
Microsoft Shipped This Nine Months Ago
Azure AI Foundry Agent Service went generally available in May 2025. Not as a concept. Not as a preview. As a production-ready, enterprise-grade platform that over 10,000 customers have already built on.
Everything Jassy described as groundbreaking is already running in production on Azure. The Foundry runtime automatically manages state across messages, tool calls, agent configurations, and metadata. Conversations persist across sessions. Agents can pick up where they left off without developers manually threading context back in.
But Microsoft went further than what AWS is even promising. Foundry supports multi-agent workflows with a structured orchestration layer that coordinates multiple agents across complex, multi-step processes. It handles context management, error recovery, and long-running durability out of the box. Then at Ignite in November 2025, Microsoft added managed long-term memory to the service. A persistent state layer that automatically extracts, consolidates, and retrieves user context across sessions and devices. Microsoft's own AI Research director called it turning memory from "a demo feature into an enterprise primitive."
And here's the part that should really get your attention. Azure is the only cloud that offers both Anthropic's Claude and OpenAI's GPT models under one governance umbrella. AWS just locked itself into a single-vendor model dependency with this deal. Microsoft gives you choice.
Why This Matters More in Healthcare Than Anywhere Else
If you're a CMIO or CIO at a health system, you already know that infrastructure decisions in healthcare are essentially irreversible. You don't get to run a six-month pilot on one cloud, decide you don't like it, and casually migrate your HIPAA workloads somewhere else. The switching costs are brutal. The compliance burden is real. And the downstream impact on clinical workflows, provider experience, and patient safety is too high to get wrong.
That's why the timing of this announcement matters so much. AWS is telling the market, right now, that it doesn't have competitive agentic infrastructure. And it's asking you to wait "a few months" while it catches up.
Meanwhile, the clinical use cases for AI agents aren't waiting.
Think about a patient discharge workflow. You need agents coordinating across clinical documentation, pharmacy reconciliation, insurance verification, follow-up scheduling, and transport. That's not a single model call. That's a multi-step, multi-agent orchestration problem that requires persistent state, error recovery, and real-time coordination across systems. Foundry handles this today. AWS is announcing the concept.
Or consider prior authorization. An agent that monitors submissions, tracks status, escalates denials, and coordinates between payer and provider systems needs to maintain context across days or weeks of interaction. That requires the kind of managed long-term memory that Microsoft is already shipping. Not the kind that AWS is promising to build.
And then there's governance. In a hospital, an AI agent can't operate in a vacuum. It needs identity management through Entra ID, data governance through Purview, HIPAA-grade audit trails, and role-based access controls. Foundry ships with all of that baked into the runtime. AWS is going to have to build or bolt on that entire trust layer around whatever OpenAI delivers. For a regulated industry, that gap matters enormously.
Most large health systems are also already deep in the Microsoft ecosystem. M365, Teams, SharePoint, Fabric. Foundry agents can natively reach into all of it. An AWS-hosted OpenAI agent trying to access the same data requires integration work that adds months and risk to any deployment.
What AWS Is Really Telling Us
Let's call this what it is. This announcement is not a leap forward for AWS. It's an admission that Bedrock's agent infrastructure wasn't competitive, and that Amazon needed OpenAI to close the gap. The partnership is a fast-follow strategy, not an innovation play.
It also creates a strange dynamic. Amazon is betting its agentic future on a company that is simultaneously deepening its relationship with Microsoft. OpenAI's models already run on Azure. The "co-training on Trainium" angle is interesting from a compute economics perspective, but it doesn't solve the developer experience and enterprise governance problems that actually determine platform adoption in healthcare.
For regulated industries, "coming soon" has never been an acceptable answer.
The Decision Framework for Hospital Leadership
If you're already on Azure, you have access to production-grade agentic infrastructure today. Use it. Start building the clinical agent workflows that will define the next era of care delivery.
If you're evaluating platforms, understand that the gap between Microsoft and AWS on agentic infrastructure is widening, not narrowing. Every month that passes deepens the ecosystem advantage.
If you're on AWS, ask your account team a direct question. When will you have parity with what Azure AI Foundry is shipping today? And what does the migration path look like if the answer isn't satisfying?
If you believe, as I do, that AI agents are the future of clinical operations, then the platform you choose now is the platform your agents will run on for years. Agents are the new cloud lock-in. The cloud wars have shifted from compute and storage to agentic infrastructure, and the governance and compliance layer is what separates a real healthcare platform from a general-purpose cloud with a few AI services bolted on.
Microsoft understood that early. AWS just admitted it.
Paul J. Swider is CEO & Chief AI Officer at RealActivity, a Microsoft Partner specializing in mission-critical AI for healthcare systems. He has 30+ years in healthcare technology, has trained over 3,000 engineers across GE, IDX, and Microsoft, and is the founder of BOSHUG, the Boston Healthcare Cloud & AI Community spanning 50+ countries.