Blog Post

4 Things Health IT Leaders Should Know from Microsoft Ignite 2025

by Charles Knight on November 24, 2025

Microsoft Ignite Recap - 4 Things Health IT Leaders Should Know

Microsoft Ignite 2025 delivered a set of updates that directly affect how health systems think about Epic performance, AI adoption, and their cloud strategy. The themes were clear: Azure is advancing fast, AVD adoption is becoming more flexible, and Epic’s partnership with Microsoft is more visible and mature than ever. 

Below are the takeaways that matter most if you’re responsible for the reliability, scalability, and future direction of your Epic environment. 

1. Hybrid AVD expands how hospitals can approach clinical desktops 

One of the most meaningful announcements this year was Hybrid Azure Virtual Desktop (AVD). 

In previous models, VDI was largely an “either/or” choice – either you ran desktops locally, or you moved them fully to Azure. Hybrid AVD changes that. It offers a phased, blended approach that lets hospitals run sessions locally during planned transitions, or when a network disruption impacts cloud connectivity. 

Microsoft demonstrated a four-phase pathway: 

Why this matters for Epic environments: 

Ignite also made B2B external identities for AVD generally available – a win for health systems supporting affiliates and partner practices. 

EHC is already working with multiple Epic customers evaluating AVD today, and these new hybrid and guest-access controls add even more flexibility for health IT leaders planning their next-generation workspace strategy. 

2. Epic’s visibility in the keynote signals deeper alignment with Microsoft 

Epic’s inclusion in the Microsoft keynote highlighted the continued momentum behind their collaboration on AI and cloud performance. 

Microsoft showcased live front-end Epic workflows, including Hyperdrive and AI-enabled features. Epic typically reserves this content for its own conferences, so seeing it at Ignite reflects how closely the two organizations are working together. 

Technical updates worth noting: 

These improvements reinforce what we’ve seen across our Epic on Azure customers: Azure continues to close the operational gaps that previously made some health IT leaders hesitant. 

3. AI dominated Ignite but CIOs / CTOs should balance excitement with readiness 

AI was the centerpiece of Ignite – from Agentic AI to healthcare-specific model catalogs to new tools like Microsoft Dragon Copilot. Microsoft announced: 

Microsoft also highlighted early adopters evaluating these tools. 

Charles Wagner, CTO at Franciscan Health, described how their move to Azure enabled them to begin evaluating Dragon Copilot and Azure Data Lakehouse capabilities: 

“With this foundation in Azure, we can now take advantage of the Dragon Copilot for ambient listening. And by building our data Lakehouse in Azure, that integration allows the physicians to give even better care for patients.” 

Charles Wagner, CTO, Franciscan health

Ignite included several AI demos that showed what’s possible, but like any emerging capability, real-world adoption will depend on operational readiness, workflow fit, and clinician confidence. CIOs should treat these tools as promising but still evolving, with an eye toward evaluating them thoughtfully as they mature. 

4. The partner ecosystem around Epic on Azure keeps maturing 

Microsoft highlighted Nerdio as a key launch partner for Hybrid AVD. Their early support for hybrid configurations aligns with what we’re seeing across our own customer evaluations – particularly for organizations exploring ways to modernize VDI while maintaining strong clinical performance and resiliency. Nerdio’s tooling continues to make AVD easier to manage at scale, which is valuable for health systems looking to balance cost, simplicity, and operational control during transition phases. 

TL;DR: (or in summary…) 

Ignite reinforced that Microsoft’s investments in Azure, AI, and virtual desktop modernization are directly benefiting Epic customers. For health systems still evaluating cloud options, the conversation is shifting. The question isn’t whether Azure can run Epic at enterprise scale – that’s already proven. 

The real question is: when do you want access to the operational improvements and AI capabilities that are only available once you’re there? 

Recent Posts

Epic on Azure: What You Need to Know.
This is default text for notification bar