Azure and HIPAA audit prep: what a practice under pressure should test first

Written by

in

If a patient complaint, a breach notice, or a payer questionnaire just put HIPAA on your calendar, you do not need a 200-page binder. You need an order of work that matches how small practices actually run Microsoft 365 and Azure today.

This is HIPAA audit preparation and HIPAA risk assessment work. It is not a promise that you are finished, “HIPAA ready,” or somehow cleared. Regulators care whether you know where ePHI lives and whether you can show decisions and evidence.

Start with where ePHI actually is

Before you open Azure Policy dashboards, list the systems:

  • Practice management / EHR
  • Imaging and sensor workstations
  • Microsoft 365 mail and OneDrive / SharePoint
  • Patient portals and fax/email gateways
  • Billing vendors and clearinghouses
  • Any Azure VM, storage account, or backup vault that holds exports

If that inventory is fuzzy, stop decorating controls. Finish the inventory. OCR settlements keep citing missing or shallow risk analysis more than missing wallpaper policies.

Then test identity, because identity is how breaches start

For a Microsoft-heavy practice, the first technical pass should answer:

  1. Who has Global Admin or privileged roles, and is that standing access?
  2. Is MFA actually required on interactive admin and clinical staff paths, including break-glass handling?
  3. Are legacy authentication protocols still allowed?
  4. Which guest accounts and enterprise apps still have access?
  5. Are shared mailboxes interactive logins?

Azure AD / Entra misconfiguration is not a side quest. It is the front door.

Storage, backups, and logging next

  • Encryption settings on disks and storage that hold ePHI exports
  • Backup jobs that someone has restored on purpose in the last quarter
  • Log retention you can actually query (sign-in logs, audit logs, mailbox audit)
  • Conditional access gaps for apps that touch patient data

A pretty Azure Security score with unrestorable backups is still a bad week waiting to happen.

Policies and BAAs have to match the stack

Auditors and investigators ask for documents that describe the environment you run, not a template from a blog. Business associate agreements should cover the vendors who can see ePHI. Workforce training should mention your real tools.

Dark Edge wording for frameworks we align to: aligned with, management attestation available on request. We do not call this certified, audited, validated, or compliant.

A sane two-week triage when pressure is high

Week 1: ePHI inventory, Entra privileged access and MFA gaps, mailbox forwarding/rules sweep, confirm BAAs for top vendors.

Week 2: backup restore drill on one critical system, patch and expose check on internet-facing hosts, draft or refresh the risk analysis outline with owners and dates.

Then schedule the deeper HIPAA risk assessment so the triage notes become a durable record, not a panic folder.

How Dark Edge helps

We run HIPAA Security Risk Assessments for independent practices, with technical review of the Microsoft estate as part of that work. If we manage an environment, we do not assess that same environment. Independence matters when someone else is reading the report.

Book a strategy call if you need a fixed-scope prep plan in writing before the calendar date lands.