Epic and Microsoft Integration: Licensing Requirements Guide

Epic Systems is deployed in over 70% of large US hospital systems, serving more than 350 million patient records. For these organizations, the Epic-Microsoft integration landscape defines a significant portion of their Microsoft licensing decisions — and creates specific commercial dynamics that affect every EA negotiation. The relationship between Epic and Microsoft is simultaneously competitive (in patient engagement, clinical documentation, and data analytics), collaborative (Microsoft Cloud for Healthcare, Teams EHR Connector, DAX integration), and increasingly complex. Understanding the licensing implications of each integration point is essential before any commercial commitment to either vendor.

This guide covers the specific Microsoft license requirements for each major Epic-Microsoft integration, the cost implications, and the negotiation tactics that Epic health systems hold — but rarely use effectively.

1. Epic-Microsoft Integration Map and Licensing Requirements

Integration	What It Does	Microsoft License Required	Additional Cost
Teams EHR Connector (Virtual Visits)	Launch Teams video visits from Epic scheduling/encounter workflow	M365 E3/E5 + Cloud for Healthcare Teams EHR Connector	~$12/provider/month (scoped to active telehealth users)
Teams Secure Messaging Integration	Care team communication within Epic using Teams identity	M365 E3 or F3 (Teams included)	No additional cost beyond base M365
Epic Staff Scheduling → Teams Shifts	Epic Optime/staff schedule surfaced in Teams Shifts app	M365 E3 or F3 (Teams Shifts included)	No additional cost; requires custom integration work
Nuance DAX → Epic Note Automation	Ambient AI documentation pushed directly into Epic encounter notes	M365 E3/E5 base; DAX separately licensed	$149–$299/provider/month (DAX Express/Copilot)
Epic on Azure (Cloud Hosting)	Epic Caché/InterSystems IRIS database on Azure VMs	Standard Azure IaaS (VMs, storage, networking)	$800K–$4M/year depending on system size
Epic Caboodle → Azure Synapse/Fabric	Epic clinical data mart feeding Azure analytics environment	Azure Synapse Analytics or Microsoft Fabric (consumption)	$50K–$300K/year depending on data volume and analytics workload
MyChart → Microsoft Identity	Patient portal using Microsoft Entra External ID for consumer authentication	Entra External ID (50K MAU free tier)	Usually free; $0.00325/MAU above 50,000
Epic FHIR API → Azure AHDS	Epic R4 FHIR APIs feeding Azure Health Data Services for interoperability	Azure Health Data Services (AHDS) consumption	$18K–$84K/year depending on API call volume

2. Teams EHR Connector: The Most Important Licensing Decision

The Teams EHR Connector is the highest-profile Microsoft-Epic integration and the one with the most significant commercial consequence. Microsoft launched the connector to enable direct integration of Teams video visits into the Epic scheduling workflow — when a patient has a video visit appointment, the provider clicks a Teams button in Epic and launches the meeting without leaving the clinical workflow.

The connector requires the Microsoft Cloud for Healthcare license at approximately $12/user/month. The critical commercial question is: who gets licensed? Microsoft's default position is to scope to all clinical users in the Epic deployment. The correct position — supported by Epic usage data — is to scope to active telehealth providers: clinicians who conduct virtual visits. The difference is significant.

Example: 5,000-user health system with 1,800 Epic users, 600 active telehealth providers: Microsoft proposal — 1,800 × $12 = $21,600/month ($259,200/year). Correctly scoped — 600 × $12 = $7,200/month ($86,400/year). Annual difference: $172,800 for identical functionality.

To negotiate the correct scope: pull 90-day telehealth visit data from your Epic scheduling system showing actual provider-level virtual visit activity. Present this as your scoping basis. Negotiate a quarterly true-up mechanism to add licenses as telehealth volumes grow, rather than over-licensing at signature.

3. Epic on Azure: Infrastructure Licensing and MACC Strategy

Epic on Azure is Microsoft's flagship healthcare cloud hosting story and one of its most strategically important customer relationships in the healthcare sector. As of 2026, the majority of new Epic installations and many large health system migrations are choosing Azure for hosting. This gives Epic health systems on Azure significant leverage in Microsoft EA negotiations.

Azure Infrastructure Requirements for Epic

An Epic on Azure deployment for a 500-bed hospital system typically requires: 4–8 Azure Virtual Machines (M-series or E-series for high-memory Caché database); 4–8 Azure VMs (D-series) for application servers; Azure Premium SSD v2 managed disks for database performance; Azure Virtual Network with hub-spoke architecture; Azure ExpressRoute (1–10 Gbps) for EHR-to-on-premises connectivity; Azure Backup for daily database snapshots; Azure Site Recovery for DR; and Azure Monitor plus Application Insights for Epic performance monitoring.

Total Azure spend for a 500-bed system: $600,000–$1,200,000/year depending on VM SKU selection, storage configuration, and ExpressRoute circuit size. For a 2,000-bed system: $2,000,000–$4,500,000/year. These are substantial Azure commitments that should drive significant MACC discounts.

MACC Negotiation Strategy for Epic Azure Deployments

The Epic on Azure infrastructure spend creates a natural MACC anchor. A 3-year MACC of $3M–$10M (depending on system size) unlocks blended Azure discounts of 18–28%. The MACC structure also improves M365 commercial terms — Microsoft's sales team values Azure MACC as a demonstration of platform commitment and will apply M365 discount improvements alongside Azure MACC commitments.

Important: negotiate the MACC before Epic go-live, not after. Once Epic is on Azure and your environment is stable, Microsoft knows migration risk is high and your leverage decreases. The highest leverage moment for Azure MACC negotiation is during the Epic cloud migration planning phase, when your Azure spend trajectory is attractive to Microsoft but before any contractual commitment.

4. Nuance DAX and Epic: Commercial Considerations

Nuance DAX's deep integration with Epic makes it the ambient documentation solution of choice for Epic health systems. The technical workflow is compelling: DAX listens to the patient encounter, generates a clinical note draft, and pushes it directly into the relevant Epic note type — H&P, progress note, procedure note — without physician involvement until the review step. For physicians documenting 30–40 encounters daily, this represents a genuine productivity transformation.

The commercial reality: DAX is separately negotiated with Nuance (now Microsoft Healthcare). Epic's go-live team may recommend DAX during implementation, but there is no commercial bundling between Epic licensing and DAX. Treat DAX as a separate procurement decision.

DAX Pricing and Negotiation

DAX Express: $149/provider/month. DAX Copilot: $299/provider/month. Volume tiers reduce per-provider cost at 250 and 500+ provider thresholds. A 500-physician health system deploying DAX Copilot at list price: 500 × $299 × 12 = $1,794,000/year. Negotiated price at 500+ physician volume: $240–$260/provider/month = $1,440,000–$1,560,000/year. Negotiation saves $234,000–$354,000/year at this scale.

Competitive alternatives to use as pricing anchors: Suki AI ($199/provider/month, growing Epic integration), Abridge (Google-backed, competitive pricing at scale), Augmedix (AWS-backed ambient documentation). DAX's advantage is the depth of Epic workflow integration — but this advantage is narrowing as competitors develop their own Epic App Orchard integrations. Document your evaluation of alternatives before any DAX commitment.

5. Epic Caboodle and Azure Analytics

Epic's Caboodle clinical data warehouse feeds downstream analytics through Epic's Reporting Workbench and Cogito suite. For health systems moving beyond Epic's native analytics capabilities, Caboodle data feeds into Azure-hosted analytics environments — Azure Synapse Analytics, Microsoft Fabric, or third-party platforms (Databricks, Snowflake on Azure).

The Caboodle-to-Azure pipeline creates two licensing considerations: (1) Azure data services for the analytics environment (Synapse, Fabric, Azure Data Lake Storage) are consumption-priced and should be included in your MACC model; (2) Microsoft Fabric, if chosen as the analytics platform, has its own F-SKU capacity pricing that should be evaluated against the Epic Cogito Advanced Analytics license cost.

In several health system engagements, we have found that replacing Epic Cogito Advanced Analytics (typically $150,000–$500,000/year depending on module and user count) with Microsoft Fabric (F64 capacity at $7,214/month = $86,568/year) reduces analytics licensing cost by 40–70% while enabling broader data access, cross-system analytics, and AI/ML capabilities not available in Cogito. This analysis should be part of any combined Epic-Microsoft strategic review.

6. Frequently Asked Questions

What Microsoft license is required for Epic Teams EHR Connector?

The Teams EHR Connector requires the Microsoft Cloud for Healthcare Teams EHR Connector license (~$12/user/month) plus an M365 E3 or E5 base plan. Scope to active telehealth providers only — not all Epic users. Use 90-day telehealth visit data to justify your scope.

Does Epic on Azure require special Microsoft licensing?

No special licensing SKUs are required. Epic on Azure uses standard Azure IaaS services. However, the scale of Azure infrastructure creates a strong MACC negotiation anchor for 18–28% blended Azure discount. Negotiate the MACC during Epic migration planning — before go-live when leverage is highest.

Is Nuance DAX included in the Epic integration?

No. DAX integrates with Epic technically but is commercially separate, licensed at $149–$299/provider/month. Negotiate DAX pricing independently from your Microsoft EA, using Suki AI, Abridge, and other competitors as pricing anchors.

What Azure services does Epic require?

M-series or E-series VMs for database, D-series for application servers, Premium SSD v2 storage, Virtual Network with ExpressRoute, Azure Backup, Site Recovery, and Azure Monitor. Total cost ranges from $600K–$4.5M/year depending on system size.

How should Epic health systems negotiate their Microsoft EA?

Four levers: (1) Epic on Azure MACC for 18–25% Azure discount; (2) Teams EHR Connector active-user scoping; (3) DAX competitive evaluation (Suki, Abridge, Augmedix) for pricing pressure; (4) reference account value — large Epic systems are Microsoft's most wanted healthcare showcase customers worth $200K–$500K in commercial concessions. Engage an independent adviser before any commercial discussion with Microsoft's healthcare team.