HIPAA and HITRUSTPublished Last reviewed November 20269 min read
Short answer
A HIPAA Security Rule risk analysis for a practice on Microsoft 365 is a dated, written assessment that inventories ePHI across Exchange Online, SharePoint, OneDrive and Teams, rates each threat by likelihood and impact, records current controls such as MFA, Conditional Access, email encryption, audit logging, retention and Intune, and feeds a risk management plan. 45 CFR 164.308(a)(1)(ii)(A) requires it for covered entities and business associates.
Check where you stand: take the HIPAA and HITRUST check. About two minutes, no email needed.
Update, November 2026
The 2026 Unified Agenda, published in the Federal Register on August 14, 2026, moved the target for the final Security Rule update (RIN 0945-AA22) to July 2027 and lists it as a long term action. As of November 15, 2026, no final rule has been published, and HHS says the current Security Rule remains in effect.
A HIPAA risk analysis for a practice on Microsoft 365 is a dated, written assessment of where your ePHI lives in Exchange Online, SharePoint, OneDrive and Teams, what could go wrong, how likely and how damaging each risk is, and what you are doing about it. Most of the evidence is already in your tenant. The weak analyses we see are templates that never looked at it.
What does 45 CFR 164.308(a)(1)(ii)(A) actually require?
It requires an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the ePHI you hold. It is a required implementation specification, not an addressable one, and it applies to business associates as well as covered entities.
HHS guidance on risk analysis spells out what thorough means. The scope is all ePHI you create, receive, maintain or transmit, in any electronic media. You find where it lives, identify reasonably anticipated threats and vulnerabilities, assess current safeguards, estimate likelihood and impact, assign a risk level and document it. HHS sets no format or frequency, but it expects the process to be ongoing.
The analysis then drives risk management under 164.308(a)(1)(ii)(B), which asks for security measures sufficient to reduce risks to a reasonable and appropriate level. An analysis with no plan attached is half the job.
Where does ePHI live in Exchange, SharePoint, OneDrive and Teams?
In more places than most practice managers expect, and Teams is the main reason. Teams stores its data across the other three services, so an inventory that lists Teams as a single line is already incomplete.
| Workload | Where ePHI tends to show up | What to check |
|---|---|---|
| Exchange Online | Referrals, lab results and scanned forms as attachments; front desk and billing shared mailboxes | Who can open each shared mailbox; forwarding rules to outside addresses |
| SharePoint | Team sites used as a file server for intake packets, billing exports and scanned records | Anyone links, guest access, broken permission inheritance |
| OneDrive | Exports a staff member saved for later; files shared from Teams chats | External sharing; sync to unmanaged home computers |
| Teams | Chat messages are stored in Exchange Online mailboxes; files shared in chats go to the sharer’s OneDrive; channel files go to the team’s SharePoint site; meeting recordings and transcripts go to the organizer’s OneDrive, or to SharePoint for channel meetings | Guest access, recording policy, and whether retention covers chats |
Add the systems outside the tenant too: the EHR, imaging, the phone system and the copier that scans to email. For a business associate, the same exercise covers the customer data you receive and the support tools where staff paste screenshots.
How should a small practice rate threats and likelihood?
Use a simple, consistent scale and tie every rating to something you observed in the tenant. Three levels each for likelihood and impact are plenty for a ten person dental office, as long as the reasoning sits next to each score.
The Microsoft 365 threats that matter are predictable: phishing for passwords, adversary in the middle phishing that steals session tokens and gets past MFA, misdirected email, oversharing through Anyone links, a lost laptop with synced files, a former employee who still has access, and ransomware in synced folders. Likelihood should reflect your real controls. A tenant that enforces MFA for every account through Conditional Access is far less exposed to password spray than one still waiting on half its staff to register.
Rate each threat against each place ePHI lives, not against the practice as a whole. “Phishing: high” tells a reviewer nothing. “Phishing that leads to takeover of the billing shared mailbox, which holds three years of remittance attachments: likely, high impact” shows that someone looked. The HHS Security Risk Assessment Tool, built for small and medium providers, is a reasonable structure, but it will not inspect your tenant for you.
Which Microsoft 365 controls matter most for a HIPAA risk analysis?
Identity, email protection, audit logging, retention and device management move likelihood the most. For each one, record whether it is on, who it covers and every exception.
- MFA and Conditional Access. Conditional Access needs Microsoft Entra ID P1, which Microsoft 365 Business Premium includes. Security defaults are available to every tenant and beat nothing, but they offer no exclusions or device rules. List every excluded account, break glass accounts included, and why.
- Email encryption. Microsoft Purview Message Encryption is included in Business Premium and the E3 and E5 plans. A mail flow rule that encrypts messages to certain recipients or with certain subject words is more dependable than asking staff to remember the Encrypt button.
- Audit logging. Microsoft Purview Audit (Standard) keeps records for 180 days. Audit (Premium), which comes with E5 licensing, keeps Exchange, SharePoint, OneDrive and Entra records for one year by default, and an additional per user license extends that to 10 years. If you cannot reconstruct who opened a mailbox seven months ago, that is a finding. These logs also support information system activity review under 164.308(a)(1)(ii)(D).
- Retention. Purview retention policies cover Exchange mailboxes, SharePoint sites, OneDrive accounts and Teams, but Teams chats and channel messages need their own Teams locations. A mailbox policy does not reach them.
- Device management. Intune compliance policies for BitLocker, operating system version and screen lock, paired with Conditional Access that only admits devices meeting them, keep ePHI off personal laptops.
Microsoft offers a HIPAA business associate agreement through its Products and Services Data Protection Addendum to covered entity and business associate customers. That covers Microsoft’s obligations. Microsoft says plainly that the agreement does not by itself achieve HIPAA compliance; the configuration is yours. A Microsoft 365 security assessment shows where your tenant actually stands before you score anything.
What documentation holds up if OCR asks for your risk analysis?
A dated, written analysis that names your actual systems, shows how each risk was rated, and connects to a risk management plan with owners and target dates. OCR’s recent settlements keep landing on the same finding: no accurate and thorough risk analysis.
On March 5, 2026, OCR announced the 12th enforcement action in its Risk Analysis Initiative, a settlement with a software business associate after a breach affecting about 15 million people. OCR cited a failure to conduct an accurate and thorough risk analysis, and the corrective action plan, monitored for three years, requires one along with a risk management plan, written policies and training.
A file that holds up usually contains:
- A dated scope statement listing every system and Microsoft 365 workload that holds ePHI.
- The ePHI inventory, including Teams storage locations and shared mailboxes.
- Threats and vulnerabilities, each with a likelihood, an impact and a risk level.
- Current controls with evidence, such as Conditional Access exports, audit retention settings and Intune compliance reports.
- The risk management plan: what you will fix, who owns it and the target date.
- Approval by your security official and the events that trigger a review, such as a new EHR, an acquisition or an incident.
Retain it for six years from creation or from when it was last in effect, whichever is later, under 45 CFR 164.316(b)(2)(i). Keep old versions too. Comparing this year’s analysis to last year’s is how a reviewer sees whether you worked the plan.
What is the status of the proposed HIPAA Security Rule update?
As of mid March 2026, it is still a proposal. HHS published the notice of proposed rulemaking in the Federal Register on January 6, 2025, comments closed on March 7, 2025, and no final rule has been published. HHS says the current Security Rule remains in effect while the rulemaking is underway.
The Spring 2025 Unified Agenda listed May 2026 as the target for final action. Targets slip, so plan against the current rule.
The proposal is still useful today. According to the HHS fact sheet, it would require written documentation of all Security Rule policies, procedures, plans and analyses; a technology asset inventory and network map updated at least once every 12 months; MFA and encryption of ePHI at rest and in transit, with limited exceptions; and an end to the distinction between required and addressable specifications. Business associates would have to verify their technical safeguards to covered entities at least once every 12 months. The proposed compliance date is 180 days after a final rule takes effect. An analysis built on a real asset inventory and real tenant settings will need far less rework if it lands.
We work across more than 200 Microsoft 365 and Azure tenants, and the risk analyses that hold up best are the specific ones someone keeps current. For a quick read on where you stand, try our starting point check, or see how we approach HIPAA aligned security work.
If you would like a second set of eyes on your scope or your ratings, book a 30 minute call and we will walk through it with you.
Frequently asked questions
How often should a practice update its HIPAA risk analysis?
The Security Rule does not set a frequency, and HHS describes risk analysis as an ongoing process. A practical cadence is a full review every year plus an update whenever something material changes, such as a new EHR, a change in Microsoft 365 licensing, a new office, an acquisition or a security incident.
Is the HHS Security Risk Assessment Tool enough for a Microsoft 365 practice?
It is a useful structure for small and medium providers, and many practices start there. HHS says using it is not required and does not guarantee compliance. It also cannot look inside your tenant, so you still need to bring your actual Conditional Access, audit, retention and Intune settings into the analysis.
Does Microsoft’s business associate agreement cover our risk analysis?
No. The agreement Microsoft offers through its Products and Services Data Protection Addendum covers Microsoft’s obligations as your business associate for in scope services. Your risk analysis, your tenant configuration and your policies remain your responsibility, and OCR will ask you for them, not Microsoft.
Do business associates need their own HIPAA risk analysis?
Yes. The risk analysis standard in 45 CFR 164.308 applies to business associates as well as covered entities. A billing company, IT provider or software vendor that handles ePHI needs an analysis of its own systems and the customer data it holds, separate from its clients’ analyses.
Is a HIPAA checklist the same thing as a risk analysis?
No. A checklist confirms whether safeguards exist. A risk analysis identifies threats to your specific ePHI, rates likelihood and impact, and assigns a risk level that drives your risk management plan. A completed checklist with no ratings and no plan is unlikely to satisfy an OCR request for your risk analysis.