Medical practices using Microsoft 365 are increasingly looking at Teams Phone. Here's what works for healthcare — and what to watch out for around HIPAA and PHI.
If your practice already pays for Microsoft 365 — and most NYC practices do — you've probably wondered whether Microsoft Teams Phone could replace your separate phone system. Less software to manage, one bill, your team already uses Teams for everything else.
For most medical practices, the answer is yes. Teams Phone can work well for healthcare — but only if you set it up correctly. Get HIPAA, PHI handling, and integration wrong, and you'll create compliance problems that didn't exist before.
Here's what to know.
Microsoft signs HIPAA Business Associate Agreements (BAAs) for its enterprise services including Microsoft 365 (E3, E5, Business Premium) and Teams. With a BAA in place, Microsoft is treated as a Business Associate under HIPAA — which means they're contractually obligated to protect PHI handled within their services.
This applies to Teams Phone too. Voicemails left for medical staff, call recordings (if you enable them), and call logs all qualify as PHI when they contain patient information. Microsoft commits to protecting that data per HIPAA requirements when you have a signed BAA.
To get the BAA, ask your Microsoft account manager or check the Microsoft Trust Center. It's a standard agreement — Microsoft signs it for any eligible commercial customer.
Important: HIPAA compliance isn't a feature you turn on. It's the combination of Microsoft's BAA, your operator's BAA, your configuration choices, and your practice's HIPAA policies. Talk to your compliance officer or attorney before assuming any technology stack is HIPAA-compliant for your specific use case.
Teams Phone handles patient call routing naturally. Auto-attendants greet callers, route appointments to scheduling, prescription refills to the appropriate staff, and urgent calls to the on-call provider. After-hours routing can send urgent calls to a covering physician's mobile app (with the practice's caller ID).
If your practice has multiple offices (NYC and Long Island, or Manhattan and Brooklyn), Teams Phone handles all locations as one system. Staff at one office can see availability of staff at another, transfer calls between offices, and share auto-attendants and queues.
Front office staff working from home one day a week can answer the practice line through the Teams mobile app — with the practice's number showing on caller ID. No personal cell numbers exposed, no calls missed because someone wasn't at the desk.
Voicemails arrive as audio attachments with transcription in the recipient's email. For after-hours patient calls, this means staff can review every message at the start of the day with full context — caller's name and number, what they said, when they called.
Some medical practices want to record calls for quality assurance or documentation. Microsoft Teams supports call recording, but for medical practices there are considerations:
Teams call recording is workable for these use cases but requires careful configuration. Some practices choose to keep their call recording on a separate, purpose-built system rather than Teams.
Teams Phone doesn't do fax. For most medical practices, fax is non-negotiable — labs, insurance carriers, specialists, pharmacies, attorneys, and other practices all communicate via fax constantly.
Pair Teams Phone with a HIPAA-compliant cloud fax service like CalliFax. Faxes come and go from your existing fax number, delivered to email with HIPAA-compliant handling. Your fax number doesn't change; your fax machine just goes away.
If your EHR has built-in click-to-dial and call logging, you'll need to configure it to work with Teams Phone. This usually works — Teams supports tel: URI handlers and click-to-call from most modern applications — but verify with your specific EHR before deployment.
SMS texting from Teams using Operator Connect is available in some configurations, but HIPAA compliance for texting requires careful attention. Patient texts must be encrypted in transit and at rest, accessed only by authorized personnel, and stored with appropriate retention controls.
For most medical practices, a purpose-built HIPAA-compliant texting service like CalliText is safer and easier than relying on native Teams SMS for patient communications.
Typical deployment for a 15-person medical practice in NYC:
For a 15-person practice, monthly costs typically work out to:
The answering service savings are often the most significant. Many medical practices pay $300-800/month for an after-hours answering service. With Teams Phone after-hours routing — urgent calls to the on-call provider's mobile app, non-urgent to voicemail-to-email — the answering service becomes unnecessary.
We deliver Microsoft Teams Phone through Operator Connect with HIPAA-aware configuration, signed BAA, and integration with CalliFax for clinical faxing. We've deployed Teams Phone for medical practices across NYC, Long Island, and Westchester.
If you're already a Microsoft 365 customer and you're paying separately for a phone system and an answering service, you're probably overpaying. See our medical offices page, call (212) 423-1234, or schedule a free assessment.