Guide · October 27, 2026

Does Microsoft 365 Make Us HIPAA Compliant?

Microsoft signs a Business Associate Agreement and the tenant can meet the Security Rule's technical safeguards, but compliance is the organization's own risk analysis, policies, and records. What the tenant can prove, what it cannot, and where to start.

The short answer

No. HIPAA compliance belongs to the covered entity or business associate, not to its software. Microsoft 365 can be configured to meet the Security Rule's technical safeguards, and Microsoft will sign a Business Associate Agreement, but the risk analysis, the policies, the workforce training, and the records that prove it are the organization's own, and no tenant setting produces them.

The useful question is narrower: which parts of the Security Rule can the tenant prove, which parts cannot, and is ours configured the way it should be?

What HIPAA actually requires

The HIPAA Security Rule, 45 CFR Part 164, Subpart C, protects electronic protected health information (ePHI) with three families of safeguards.

  • Administrative safeguards: a risk analysis and risk management process, a named security official, workforce training and sanctions, access authorization procedures, contingency planning, and periodic evaluation. The risk analysis is the foundation; it is the first thing an investigator asks for.
  • Physical safeguards: facility access, workstation use and security, and device and media controls.
  • Technical safeguards: access control, including unique user identification and emergency access; audit controls; integrity controls; person or entity authentication; and transmission security.

The rule also requires a Business Associate Agreement with any vendor that creates, receives, maintains, or transmits ePHI on the organization's behalf. Microsoft is such a vendor, and its agreement for Microsoft 365 is included in its product terms for business and enterprise plans.

An overhaul of the Security Rule was proposed in January 2025. It would make multifactor authentication, encryption, asset inventories, and annual compliance audits explicit requirements. The final rule has been pushed to 2027 at the earliest, so the current rule stands, but the proposal is a clear signal of what the agency expects to see.

What the tenant can prove

The technical safeguards are where Microsoft 365 does its best work, and where an assessment can collect evidence setting by setting.

  • Access control. Every user has a unique identity, access is granted by role, and standing administrator access is limited. Conditional access policies decide who can sign in, from where, and on what.
  • Authentication. Multifactor authentication reaches every account, including administrators and shared mailboxes, with legacy sign-in methods that bypass it turned off.
  • Audit controls. Unified audit logging is on, retained long enough to answer an investigation, and someone receives the alerts.
  • Integrity and transmission security. Data is encrypted at rest and in transit by default; sensitivity labels and data loss prevention policies keep ePHI from leaving by email or share link.
  • Device controls. Managed devices are required for access to ePHI, encrypted, and wiped when lost.

Each of those is a configuration, and each can be shown to an auditor, an insurer, or an investigator as evidence rather than asserted.

What the tenant cannot prove

In practice, about half of what the Security Rule expects rests on records and practices no tenant can show. The emergency access procedure and the proof it was tested. Who receives security alerts and what they did with the last one. How a departing employee's access was removed, and when. Which administrators hold which duties. The review records: who looked at the logs, when, and what they found. The recovery procedure, and the last time a restore was practiced.

Those are policies, registers, and records. An organization that has configured the tenant well and has none of them is not compliant, and an investigator will find the gap in the first hour. The reverse is also true: a binder of policies for a tenant where multifactor authentication reaches only some accounts is a binder.

Where to start

  1. Confirm the Business Associate Agreement. Know which Microsoft 365 plan you hold and that the agreement covers it. Do the same for every other vendor that touches ePHI.
  2. Get the technical safeguards evidenced. An assessment of the tenant's identity, access, audit, and data controls, setting by setting, with evidence for every finding and a plan for the gaps, sequenced so recovery lands before any change that could lock anyone out.
  3. Write the risk analysis from the evidence. The tenant findings become the technical half of the analysis; the interview about records and practices becomes the rest.
  4. Close the gaps and keep the records. Fix the configuration, assign the registers an owner, and schedule the reviews, so the next look finds records rather than intentions.

Common questions

Does Microsoft sign a Business Associate Agreement for Microsoft 365?

Yes. Microsoft's Business Associate Agreement is included in its product terms for Microsoft 365 business and enterprise plans, so no separate signature is usually required. Confirm that the plan you hold is covered, and keep the terms with your other vendor agreements.

Is Microsoft 365 HIPAA certified?

There is no HIPAA certification for any product or organization. The Department of Health and Human Services does not certify compliance. Microsoft describes its platform as able to support a customer's compliance, which is accurate and also the limit of what any vendor can say.

Can an assessment make us HIPAA compliant?

No single engagement can. What an assessment does is evidence the technical safeguards in the tenant, setting by setting, and give you a fix plan and a scorecard that feed directly into your risk analysis. Mount Xion scopes the interview about records and practices alongside it, because that is where most organizations have gaps the tenant cannot show.

We are not a medical practice. Does HIPAA apply to us?

It applies to covered entities, which are providers, health plans, and clearinghouses, and to their business associates: any vendor that handles ePHI for them, including billing firms, IT providers, and many consultants. If a client sends you patient information, you are likely a business associate and the Security Rule applies to you.

What is changing in the Security Rule?

A proposed rule published in January 2025 would make multifactor authentication, encryption, asset inventories, network segmentation, and annual compliance audits explicit requirements and remove the distinction between required and addressable specifications. The final rule has been deferred to 2027 at the earliest. Until then the current rule applies, and the proposal is the clearest statement of where enforcement is heading.

Where Mount Xion fits. Mount Xion's Microsoft 365 identity security assessment reviews the same identity, access, audit, and data controls the HIPAA Security Rule's technical safeguards call for, with evidence for every finding written so it can be reused in your risk analysis, and the records the tenant cannot show are covered in a scoped interview. Fixed fee, quoted on a discovery call.

See the service · Book a free 30-minute discovery call

Let's talk about your technology.

A free 30-minute intro call. No pitch, no obligation, a straight answer either way.