Is SharePoint HIPAA Compliant? BAA Coverage and Setup Steps
Quick answer: Is SharePoint HIPAA compliant? SharePoint Online can be used in a HIPAA compliant way because Microsoft lists it as an in scope service under its HIPAA Business Associate Agreement (BAA). That BAA comes built into Microsoft’s commercial Data Protection Addendum, so eligible healthcare customers do not sign a separate contract. Compliance itself, however, depends on how your organization configures permissions, sharing, encryption and monitoring, and on your own HIPAA policies.
Key points
- HHS does not certify any software as HIPAA compliant, so a vendor badge proves nothing on its own.
- Teams, OneDrive, Exchange Online, Power BI, Power Automate and Microsoft Copilot Chat sit on the same in scope list as SharePoint Online.
- Default SharePoint sharing settings are built for collaboration, not for protected health information (PHI), so they need tightening.
- Microsoft 365 keeps standard audit logs for 180 days, which surprises many practices during an investigation.
- The proposed HIPAA Security Rule update that would make MFA and encryption mandatory was still not final as of 2027.
Is SharePoint HIPAA compliant on its own?
Not by itself, and the version you run changes the answer. SharePoint Online in a commercial Microsoft 365 tenant can hold PHI under Microsoft’s BAA, while other versions shift every safeguard back to you.
Three versions of “SharePoint” often get mixed up:
- SharePoint Online in a commercial or GCC Microsoft 365 tenant is in scope for Microsoft’s BAA.
- SharePoint Server installed on your own hardware is software, not a cloud service, so there is no Microsoft BAA involved and every safeguard is yours to build.
- Consumer plans such as Microsoft 365 Personal or Family run outside Microsoft’s commercial terms, so they are the wrong home for PHI.
If you are unsure whether HIPAA even applies to your business, start with our guide to what counts as a HIPAA covered entity.
How Microsoft’s BAA works for SharePoint
Microsoft makes its HIPAA BAA available by default to every customer that is a covered entity or business associate, through the Microsoft Online Services Data Protection Addendum. You accept it with your licensing agreement, and you can download a copy from the Microsoft Service Trust Portal.
Two details matter in practice. First, Microsoft will not sign your own BAA template. It runs one standardized multitenant service for everyone, so it uses a single agreement it built with academic medical centers and other healthcare organizations. Second, the BAA covers only services named on Microsoft’s in scope list. Use something outside that list for PHI and you have no business associate protection for that data.
Behind the BAA, Microsoft’s covered services are audited for ISO/IEC 27001 and the HITRUST Common Security Framework, and you can request those reports for your own auditors.
Which Microsoft 365 apps are covered by the HIPAA BAA?
So is Office 365 HIPAA compliant? Microsoft’s HIPAA documentation, last checked in 202, lists these commercial services as in scope. Coverage means you may store PHI in them, not that they are configured safely.
| Service | Covered by Microsoft’s BAA? | What to watch |
|---|---|---|
| SharePoint Online and its lists | Yes | External sharing and broad site permissions |
| OneDrive for Business | Yes | Personal folders shared by link |
| Microsoft Teams | Yes | Guest access and files stored in channel sites |
| Exchange Online (Outlook) | Yes | Unencrypted email to outside recipients |
| Power Automate (cloud) | Yes | Flows that send data to non Microsoft connectors |
| Power BI (cloud) | Yes | Publish to web and exported reports |
| Office apps, including Word | Yes, as Office Pro Plus and Office Online | Files saved to personal, non work accounts |
| Microsoft Copilot and Copilot Chat | Yes | Copilot shows users anything they already have access to |
| Azure | Yes, for services in Azure’s audit scope | Check each Azure service individually |
What most articles miss is the Power Automate connector problem. The service itself is covered, yet a flow that copies a SharePoint list item into Gmail, Dropbox or a third party CRM pushes PHI to a vendor that needs its own BAA. Microsoft’s coverage stops at the edge of Microsoft’s services.
Copilot raises a similar issue. Because it surfaces whatever a user can technically open, oversharing that nobody noticed for years suddenly becomes searchable in a sentence.
How to make SharePoint HIPAA compliant
Making SharePoint HIPAA compliant means pairing Microsoft’s BAA with your own safeguards, because the BAA covers Microsoft’s duties, not yours. Work through these steps, ideally alongside a documented risk analysis:
- Confirm your plan and BAA. Use a commercial Microsoft 365 plan, download the BAA from the Service Trust Portal and file it with your compliance records. Our Microsoft 365 Business Basic vs Standard comparison explains what each plan includes.
- Require MFA for everyone. Turn on multifactor authentication through Microsoft Entra ID and block legacy sign in methods that skip it.
- Lock down sharing. In the SharePoint admin center, disable “Anyone” links, limit external sharing to approved guests or domains, and set expiration dates on guest access.
- Apply least privilege. Build PHI sites around Microsoft 365 groups with clear owners, and avoid granting access to “Everyone except external users.”
- Label and encrypt. Use Microsoft Purview sensitivity labels to mark PHI documents and apply encryption that travels with the file.
- Turn on data loss prevention. Start from Purview’s U.S. Health Insurance Act (HIPAA) Enhanced template, which can watch SharePoint, OneDrive, Exchange and Teams for content such as diagnosis codes and Social Security numbers.
- Plan audit retention. Audit (Standard) keeps records for 180 days; Audit (Premium) keeps SharePoint and Exchange records for one year and supports longer custom policies.
- Back up and train. Add retention policies, a separate backup that follows the 3 2 1 rule, and staff training on where PHI may live.
In practice, step 3 fixes the most risk for the least effort, because accidental link sharing is how PHI usually escapes a SharePoint tenant.
Common misconceptions about SharePoint and HIPAA
The biggest myth is that encryption replaces a BAA. It does not; HHS treats a cloud provider storing encrypted PHI as a business associate even if it cannot read the data.
Another myth involves log retention. HIPAA requires you to keep required documentation, such as policies and risk assessments, for six years. It does not set a specific audit log period, yet investigators expect you to reconstruct who opened a file, so 180 days is often too short. Most people discover this gap only after a suspected breach. Exporting logs to a SIEM or buying longer Purview retention closes it.
Finally, asking “is SharePoint HIPAA compliant” once is not enough, because settings drift. Use our HIPAA compliance audit checklist to review SharePoint settings at least annually.
Is the HIPAA Security Rule changing?
HHS proposed the largest Security Rule overhaul in a decade on January 6, 2025. It would make encryption of PHI at rest and in transit and multifactor authentication required rather than “addressable,” and add asset inventories and 72 hour restoration targets.
As of 2027 it remains a proposal, and the federal regulatory agenda lists July 2027 as the target for final action. The current rule still applies. Building MFA and encryption into SharePoint now, however, means less rework if the rule is finalized.
Is HIPAA applicable in Pakistan or other countries?
HIPAA is a U.S. federal law, so it does not govern hospitals in Pakistan treating local patients. It reaches a foreign company only when that company handles PHI for a U.S. covered entity or business associate, such as offshore medical billing, transcription or IT support. Those vendors must sign a BAA and follow its terms.
Frequently asked questions
What does HIPAA cover in a healthcare organization?
HIPAA covers protected health information through three main rules: the Privacy Rule limits how PHI is used and disclosed, the Security Rule requires safeguards for electronic PHI, and the Breach Notification Rule sets reporting duties after a breach.
What is a business associate agreement?
A business associate agreement is a contract in which a vendor that handles PHI promises to protect it, limit its use and report breaches. HIPAA requires one before any vendor creates, receives, stores or transmits PHI for you.
Does encryption alone make a cloud tool HIPAA compliant?
No. HHS guidance says a cloud provider storing encrypted PHI is still a business associate even without the decryption key, so you still need a BAA with that provider.
Is SharePoint Server on premises HIPAA compliant?
It can support compliance, but you provide every safeguard yourself: physical security, patching, backups, encryption and access logging. No Microsoft BAA applies to software running in your own data center.
Are SharePoint Online lists HIPAA compliant?
Lists are part of SharePoint Online, so they fall under the same BAA coverage. They need the same permission, sharing and DLP controls as document libraries.
Can outside providers safely access a SharePoint site with PHI?
Yes, through guest accounts limited to specific sites, protected by MFA and reviewed regularly. Avoid “Anyone” links, which let anyone holding the link open the file.
Do I need Microsoft 365 E5 for HIPAA?
No. HIPAA does not require a specific license. E5 adds conveniences such as longer audit retention and advanced DLP, but smaller practices can meet requirements with lower tiers plus sound processes.
Can I email PHI from Outlook?
Yes, Exchange Online is in scope, but email to outside recipients should be encrypted, for example with Microsoft Purview Message Encryption, and limited to the minimum necessary information.
Is SendGrid HIPAA compliant?
No. Twilio states that SendGrid is not a HIPAA eligible service, will not sign a BAA for it, and its terms prohibit using it with PHI. Keep patient details out of SendGrid emails.
Is Square HIPAA compliant?
Pure payment processing is exempt from HIPAA under Section 1179 of the law, so no BAA is needed for that alone. Square offers a BAA for other services, which matters if appointment details or health notes pass through it.
What happens if PHI is shared by mistake?
Investigate and document it as a possible breach. If it qualifies, notify affected individuals without unreasonable delay and no later than 60 days after discovery, and report it to HHS.
Does Microsoft offer a BAA for its professional services?
Yes. Microsoft extends its HIPAA BAA to in scope Microsoft Professional Services, such as certain support and consulting engagements. Ask your Microsoft account or services representative to confirm coverage before sharing PHI.
Conclusion
SharePoint Online gives healthcare teams a covered, capable home for PHI, provided you treat the BAA as the starting line. For the official details, read Microsoft’s HIPAA and HITECH compliance offering, the HHS guidance on HIPAA and cloud computing, and Microsoft’s list of Purview DLP policy templates.
