Microsoft Licensing for Telehealth and Digital Health: Complete Guide 2026

Telehealth utilization stabilized at 13–17% of total outpatient visits in 2025, following the COVID-era peak of 32% and subsequent normalization. For health systems and digital health companies, Microsoft's role in the virtual care stack has expanded significantly — Teams is the leading clinical video platform, Azure backs major digital health platforms, and the Healthcare Bot Service and Azure Health Data Services underpin consumer-facing health applications. The licensing complexity has grown proportionally: a health system running a comprehensive telehealth programme can easily encounter 6–8 distinct Microsoft licensing components across its virtual care workflow, each with different pricing models, negotiation dynamics, and cost optimization opportunities.

This guide covers Microsoft licensing across the full telehealth and digital health stack: Teams for virtual visits, HIPAA compliance configuration, Azure digital health services, remote patient monitoring, and digital health company licensing.

1. Microsoft Teams for Telehealth: What's Included and What Isn't

The most important thing to understand about Microsoft Teams for telehealth: the base Teams video functionality used for clinical virtual visits does not require any add-on license. Teams video meetings — including HD video, screen sharing, waiting room management, and session recording — are included in every M365 plan from F1 ($2.25/user/month) upward.

What requires additional licensing is the workflow integration: the ability to launch a Teams visit directly from within an EHR (Epic, Cerner, Meditech), with the appointment pre-populated and the patient automatically admitted from the waiting room. This EHR-integrated workflow requires the Cloud for Healthcare Teams EHR Connector (~$12/provider/month). For standalone telehealth — scheduling via email/patient portal with a Teams meeting link — no add-on is required.

2. HIPAA Compliance for Telehealth: The Configuration Reality

The permanent extension of telehealth HIPAA flexibilities — which allowed providers to use non-BAA-covered platforms during the COVID emergency — ended in 2023. Telehealth platforms must now be covered under a HIPAA BAA. Microsoft Teams is BAA-covered; Zoom (healthcare edition), Doxy.me, and similar platforms have their own BAA arrangements. Using consumer FaceTime, Skype (personal), or WhatsApp for clinical telehealth is not HIPAA-compliant regardless of COVID-era precedent.

For Teams-based telehealth, these specific configurations are required beyond the general HIPAA M365 configuration baseline covered in our HIPAA BAA configuration guide:

Patient waiting room enforcement: Configure Teams meeting settings to enable lobby for all external participants. Providers manually admit patients from the lobby, creating an access control checkpoint that prevents unauthorized access to clinical sessions.

Guest access restrictions: Telehealth patient sessions involve guest users (patients authenticating via the Teams mobile app or web browser). Configure guest access to prevent guests from viewing the organization's full Teams directory, accessing files outside the specific meeting context, or initiating chats with internal staff.

Meeting recording policy: Define explicit policies for telehealth recording: when recording is permitted (patient consent required), where recordings are stored (OneDrive for Business, covered by HIPAA BAA), retention duration (align with medical records retention law), and deletion policy at retention end.

3. Azure Digital Health Services Licensing

Azure Health Data Services for Telehealth

Azure Health Data Services (AHDS) plays a critical role in advanced telehealth and digital health implementations: the FHIR service handles clinical data exchange between telehealth platforms and EHR systems; the MedTech service processes remote patient monitoring device data; and Azure Health Bot provides conversational patient intake experiences.

Telehealth-specific AHDS cost model: a digital health platform serving 10,000 active patients with daily virtual visit scheduling, RPM device data, and asynchronous clinical messaging generates approximately: FHIR API calls (scheduling, clinical summaries) = 500,000 API calls/day × $0.01/1,000 = $5/day ($1,825/year); MedTech service for 2,000 RPM patients with 12 readings/day = 24,000 messages/day × $0.006/1,000 = $0.14/day ($52/year); Healthcare Bot patient intake for 500 sessions/day = $0.50/100 messages × 5 messages/session × 500 = $12.50/day ($4,563/year). Total AHDS for this workload: approximately $6,440/year — a small fraction of the overall telehealth platform cost.

Azure Communication Services for Virtual Visits

Azure Communication Services (ACS) is Microsoft's programmable communication platform — enabling voice, video, SMS, and chat capabilities to be embedded directly in digital health applications without using Teams as the UI. ACS is the licensing model for digital health companies building proprietary patient-facing video visit experiences that use Azure infrastructure but present a custom branded interface.

ACS pricing for video: $0.004/participant/minute for HD video calls. A digital health platform with 1,000 daily video visits averaging 15 minutes: 1,000 × 2 participants × 15 minutes × $0.004 = $120/day ($43,800/year). For a platform with 10,000 daily visits: $438,000/year. ACS video is significantly cheaper than Teams per-user licensing for high-volume patient-facing platforms — but lacks Teams' clinical workflow integration.

4. Remote Patient Monitoring: Licensing Architecture

Remote patient monitoring (RPM) is among the fastest-growing digital health segments, driven by CMS reimbursement codes (CPT 99453–99457) and chronic disease management programs. Microsoft's RPM technology stack involves IoT Hub, AHDS MedTech service, Power BI for clinical dashboards, and Teams for clinical alert workflows.

The RPM Azure cost at this scale is relatively modest — the significant costs in RPM programmes are the connected device hardware ($50–$300/patient for cuffs, scales, glucometers), the CMS reimbursement coding workflow (billing system), and the clinical staff time for alert review. Microsoft's technology layer is not the primary cost driver in RPM.

5. Digital Health Company Licensing Considerations

Digital health companies — telehealth platforms, health technology vendors, and digital therapeutics companies — have distinct Microsoft licensing needs from the health systems they serve. They use Microsoft's infrastructure to build products, not just deploy it internally.

Azure for Digital Health Platforms

Digital health companies building on Azure for their platform infrastructure have access to the Microsoft for Startups (Founders Hub) program for early-stage companies — providing $150,000 in Azure credits plus M365 access. Established digital health companies with $5M+ in Azure annual spend qualify for Azure MACC structures with meaningful discounts.

The key licensing decision for digital health companies: build on Azure Communication Services (ACS) for programmable video/voice at consumption pricing, or resell/integrate Microsoft Teams via the Teams platform. For patient-facing consumer applications, ACS provides more design flexibility and lower per-session cost. For clinical workflow integration with hospital EHR systems, Teams integration through the Cloud for Healthcare connector is the correct path.

HIPAA for Digital Health Vendors as Business Associates

Digital health companies handling PHI on behalf of covered entity health system customers are themselves Business Associates under HIPAA. They must have a BAA in place with Microsoft for the Azure services they use to process PHI. Microsoft's standard Azure DPA includes BAA terms — the same as the M365 BAA. Digital health companies should ensure their Azure account is associated with an active commercial agreement (not pay-as-you-go, which has different contractual terms) to ensure BAA coverage is in effect.

6. Telehealth Licensing Cost Optimization

Right-Size Teams EHR Connector Scope

The most significant telehealth cost optimization is scoping the Teams EHR Connector to active telehealth providers. Pull 90-day virtual visit data by provider from your scheduling system. The result typically shows 20–40% of EHR-credentialed providers conducted zero virtual visits in the period. License only active virtual visit providers and implement a quarterly true-up to add licenses as telehealth utilization grows.

Use ACS for High-Volume Patient-Facing Scenarios

For high-volume patient-facing interactions (patient intake, triage, post-visit follow-up) where a consumer-grade experience is more appropriate than a clinical Teams meeting, Azure Communication Services at $0.004/participant/minute is cheaper than Teams. For 50,000 short patient interactions (5 minutes average): ACS cost = 50,000 × 2 × 5 × $0.004 = $2,000. Teams equivalent license cost for 50,000 patient interactions would require guest sessions — technically free under Teams guest access, but supported by underlying M365 infrastructure cost. The architectural choice between Teams and ACS depends on workflow requirements, not just cost.

Healthcare Bot for Patient Intake Automation

Microsoft Healthcare Bot can automate telehealth patient intake workflows — symptom collection, consent confirmation, appointment reminders, and post-visit satisfaction surveys. At $0.50/100 messages, a bot handling 20 messages per intake × 500 intakes/day costs $50/day ($18,250/year). Compare to clinical staff intake at 10 minutes × $0.42/minute × 500 = $2,100/day ($766,500/year). The automation ROI is obvious; the licensing cost is marginal.

7. Frequently Asked Questions

Is Microsoft Teams HIPAA-compliant for telehealth visits?

Teams is covered under Microsoft's HIPAA BAA when properly configured. Required configurations include MFA enforcement, guest access restrictions, waiting room policies, retention policies for clinical communications, and DLP for PHI. Standard M365 E3 Teams with correct configurations supports HIPAA-compliant telehealth — no special HIPAA mode required.

What is the Microsoft Teams HIPAA BAA for telehealth?

Microsoft's HIPAA BAA is automatically included in all M365 commercial agreements. No separate telehealth BAA is required. The BAA covers Teams video meetings, chat, and file sharing. Patient consent and state telehealth practice law compliance remain the healthcare organization's responsibility.

What is Azure Remote Patient Monitoring licensing?

RPM uses Azure IoT Hub (per device/month), AHDS MedTech service (per message), FHIR service (storage + API calls), and Power BI for dashboards. Total Azure cost for a 500-patient RPM programme is approximately $4,800–$11,400/year — modest relative to device hardware and clinical staff costs.

Can a small practice use Teams for telehealth without an EA?

Yes. Microsoft 365 Business Premium ($22/user/month) or Business Standard ($12.50/user/month) for organizations under 300 users includes Teams, is covered by the HIPAA BAA, and provides a compliant telehealth platform. Business Premium includes Intune for device management — recommended for HIPAA compliance.

What are the bandwidth requirements for Teams telehealth?

Minimum 1.5 Mbps; 1080p HD recommended at 3–4 Mbps per active video participant. Providers should have 10 Mbps minimum dedicated uplink. Configure QoS to prioritize Teams media traffic (UDP 3478–3481) during peak clinical hours. Azure ExpressRoute for Teams is available but typically not required for telehealth deployments.