Opens in a new tab
Compliance audit checklist document on a desk with a magnifying glass highlighting HIPAA requirements, representing Microsoft 365 HIPAA compliance review for medical practices

Your Microsoft 365 Is Probably Not HIPAA Compliant — Here’s How to Fix It

Here’s something most medical practices don’t realize until it’s too late.

The same Microsoft 365 platform your team uses every day — for email, file sharing, Teams calls, and EHR coordination — almost certainly shipped with settings that don’t meet HIPAA requirements. Not because Microsoft made a mistake. Because Microsoft designed M365 for the entire world, not specifically for a 12-person medical practice in Los Angeles handling protected patient information.

That distinction matters more than most practice managers realize.

When you signed up for Microsoft 365, Microsoft offered you a Business Associate Agreement. You may have signed it. That BAA makes Microsoft a compliant business associate — it does not make your configuration HIPAA compliant. The security settings, access controls, audit logging, encryption standards, and data governance policies that actually determine how your patient data is handled? Those are your responsibility to configure. And right now, there’s a good chance several of them aren’t set up the way they need to be.

Here’s what needs to change — and how to verify it’s actually been done.


The Problem With “Good Enough” Default Settings

Think about the last time someone at your practice set up a new Microsoft 365 account. They probably clicked through the setup wizard, accepted the defaults, and got to work within the hour. That experience is exactly how Microsoft intended it to feel.

The problem is that those defaults were built for convenience — not compliance.

Here’s what a standard M365 tenant looks like right out of the box for a medical practice:

  • No enforced multi-factor authentication. A password alone is enough to access any account — including ones receiving patient emails and EHR notifications.
  • Unrestricted external sharing. Staff can forward PHI to personal Gmail accounts, share OneDrive links publicly, or email patient records externally with zero system-level controls stopping them.
  • Audit logging may not be on. HIPAA requires you to track who accessed what patient data and when. In many default configurations, that log simply doesn’t exist.
  • Outbound emails aren’t encrypted. Patient information sent outside your organization travels in plain text unless you’ve specifically configured encryption — which most practices haven’t.
  • No data retention policies. Deleted emails containing PHI may disappear permanently — or stick around forever — with no governance framework in place.

None of this means your practice is careless. It means your M365 setup was never reviewed through a HIPAA lens. The good news is every one of these gaps is fixable — once you know where to look.


The Eight Settings Every HIPAA-Compliant M365 Tenant Needs


1. A Signed BAA with Microsoft

Before anything else, your practice needs a formally executed Business Associate Agreement with Microsoft. This isn’t buried in your subscription terms — it has to be specifically requested and activated.

Where to find it: Microsoft 365 Admin Center → Settings → Org Settings → Security & Privacy.

If your practice has never gone through that process, start here. Everything else builds on this foundation.


2. Multi-Factor Authentication — No Exceptions

This is the single most impactful change most practices can make immediately.

Every user account in your tenant — physicians, nurses, front desk, billing, administrators — needs to require a second factor at login. One stolen password should never be enough to access a system containing patient records.

Microsoft offers two paths: Security Defaults (simple, one-click enforcement for smaller practices) or Conditional Access policies (more control over who, what device, from where, and under what circumstances MFA is required).

What to check:

  • Is MFA enforced for every active account — including rarely used ones?
  • Are legacy authentication protocols that bypass MFA blocked?
  • Has every user completed MFA enrollment?

3. Unified Audit Logging

If you can’t answer “who accessed this patient record and when,” your practice has a HIPAA problem — not a technology problem.

Unified audit logging in the Microsoft Purview compliance portal creates a continuous record of sign-ins, file access, email activity, Teams conversations, and administrator actions. It’s the foundation of HIPAA’s audit control requirements, and it needs to be deliberately enabled and configured.

What to check:

  • Is unified audit logging turned on?
  • Is retention set to at least 90 days — ideally one year?
  • Is someone actually responsible for reviewing those logs?

4. Email Encryption for Outbound PHI

Every time a staff member emails a patient result, a referral summary, or a treatment note to an external address — that message needs to be encrypted. Without Office Message Encryption (OME) configured, it isn’t.

OME policies can automate this entirely: mail flow rules can detect PHI patterns and apply encryption automatically, without requiring staff to remember to do anything differently.

What to check:

  • Is OME licensed and activated (requires Microsoft 365 Business Premium or equivalent)?
  • Are mail flow rules configured and tested?
  • Can external recipients actually open encrypted messages without friction?

5. Data Loss Prevention Policies

What happens when a staff member accidentally attaches the wrong patient file to an email? Or pastes a full medical record into a Teams message to a vendor?

Data Loss Prevention (DLP) policies in Microsoft Purview can automatically detect when PHI patterns — Social Security numbers, medical record numbers, clinical terminology — are about to leave your organization through email, Teams, SharePoint, or OneDrive. And they can stop it, flag it, or require a justification before it goes.

What to check:

  • Are DLP policies active across Exchange, Teams, SharePoint, and OneDrive?
  • Do policies include healthcare-specific sensitive information types?
  • Are alerts going to someone who can actually act on them?

6. Device Compliance and Conditional Access

Who is accessing your M365 environment — and from what devices?

Conditional Access policies can require that every device accessing practice data be enrolled in Microsoft Intune and meet minimum security standards: current OS, active antivirus, disk encryption enabled. A personal phone that’s never been secured should not be able to pull up patient emails with a single tap.

What to check:

  • Do Conditional Access policies enforce device compliance for M365 access?
  • Is Intune enrollment configured for practice-owned devices?
  • Is there a defined policy for personal device access — restrict, enroll, or block?

7. Retention Policies That Match State Law

California requires medical records to be retained for a minimum of seven years from the date of service, or until a minor patient turns 19 — whichever is longer. Your M365 retention settings need to reflect that.

Without configured retention policies, your practice is either losing records it’s legally required to keep — or keeping everything forever with no governance. Neither is a defensible compliance position.

What to check:

  • Are retention policies configured for Exchange, Teams, SharePoint, and OneDrive?
  • Do retention periods align with California’s medical records requirements?
  • Are Legal Hold procedures documented and tested?

8. Privileged Access Controls for Administrators

The accounts with global administrator access to your M365 tenant can read anyone’s email, access any file, and change any security setting. They are the highest-risk accounts in your entire organization and need to be treated accordingly.

What to check:

  • Do admin accounts require phishing-resistant MFA — not just standard authenticator app approval?
  • Are Global Admin accounts completely separate from day-to-day user accounts?
  • Is Privileged Identity Management (PIM) configured so admin access requires just-in-time activation?
  • Is all admin activity logged and periodically reviewed?

The Partial Configuration Problem Nobody Talks About

Here’s what we find most often when we audit a practice’s M365 environment for the first time:

It’s not completely unconfigured. It’s partially configured — in ways that look like compliance from the outside but leave real gaps underneath.

MFA is enabled for most users but not enforced through Conditional Access, so legacy authentication still works as a bypass. DLP policies cover email but not Teams. Audit logging is on but set to 90-day retention when state law requires seven years. OME is licensed but no one ever set up the mail flow rules, so encryption never actually happens.

Each of these partial configurations creates the appearance of a compliant M365 environment — while leaving specific, exploitable vulnerabilities in place. And because no one has done a systematic review, the gaps are invisible until an incident forces them into view.

A written findings report changes that. It tells you exactly where you stand — before anything goes wrong.


Take the Guesswork Out of HIPAA & M365 Security

Discovering that your Microsoft 365 setup has gaps doesn’t mean you have to overhaul everything overnight—it just means you need a clear starting point.

Our team offers a Free Cybersecurity Assessment designed to give medical practices a realistic, jargon-free look at their current vulnerabilities and security posture. Whether your concern is M365 configuration, access controls, or overall HIPAA readiness, we’ll show you what needs attention first. Book Your Free Cybersecurity Assessment.

Call 310-444-4343

Let's discuss how we can protect your business from these common cybersecurity mistakes.
Call 310-444-4343