Microsoft 365 Copilot HIPAA Guide: BAA, Oversharing, Audit

HIPAA and HITRUSTPublished Last reviewed November 20269 min read

Short answer

Yes. Microsoft lists Copilot and Copilot Chat among the in scope services of its HIPAA Business Associate Agreement, which it provides through the Data Protection Addendum. The BAA does not cover web search queries sent to Bing, and it does not fix internal oversharing. Before licensing, close overshared SharePoint and OneDrive content, apply sensitivity labels and Purview DLP, confirm auditing, and update your HIPAA risk analysis.

Check where you stand: take the HIPAA and HITRUST check. About two minutes, no email needed.

Update, November 2026

Microsoft’s documentation now calls these products Microsoft Copilot and Microsoft Copilot Chat, and its HIPAA and HITECH page lists them under those names among the in scope Office 365 services; web search queries are still outside the DPA and BAA. Ethereum Tech has completed Copilot work where oversharing in SharePoint and OneDrive was fixed and sensitivity labels were deployed before Copilot licenses went live.

Yes, an organization that handles ePHI can use Microsoft 365 Copilot under Microsoft’s HIPAA Business Associate Agreement. That settles how Microsoft handles your data. It says nothing about which of your own employees can open which patient files, and that is where Copilot creates real HIPAA exposure. Fix access first, label what holds ePHI, update the risk analysis, then assign licenses.

Is Microsoft 365 Copilot covered by Microsoft’s HIPAA BAA?

Yes. Microsoft’s HIPAA and HITECH Act page lists Copilot and Copilot Chat among the in scope Office 365 services, next to Exchange Online, SharePoint Online, OneDrive for Business and Microsoft Teams.

There is nothing extra to sign. Microsoft makes the BAA available through the Microsoft Products and Services Data Protection Addendum by default to customers that are covered entities or business associates. Copilot prompts and responses fall under enterprise data protection: the same contractual terms that cover your email in Exchange and your files in SharePoint, with Microsoft acting as a data processor and no use of your prompts to train foundation models.

Two cautions. Microsoft says plainly that using its services does not, on its own, meet your HIPAA obligations; your configuration and policies do that. And Microsoft began rolling out a simpler Microsoft Copilot name for the app in August, so look for the product under either name.

What does the BAA not cover when staff use Copilot?

Web search queries are the main exclusion. Agents under their own terms and personal accounts sit outside it too.

When web search is on, Copilot turns part of a prompt into a short query and sends it to Bing. Microsoft removes user and tenant identifiers from that query, but its web search documentation states that neither the Data Protection Addendum nor HIPAA compliance applies to these generated queries. A patient’s name or diagnosis in a prompt can become part of a search term. The Allow web search in Copilot policy in the Cloud Policy service for Microsoft 365 can turn web search off entirely or only in work mode.

Agents are the second gap. Microsoft tells customers to check each agent’s privacy statement and terms of use, so approve agents one at a time in the Microsoft 365 admin center. The third gap is the personal account. Enterprise data protection applies when staff sign in with their Microsoft Entra work account, not a personal Microsoft account in the consumer Copilot app.

Copilot activityUnder the BAA and DPA?What to do
Prompts and responses with a work accountYes, under enterprise data protectionSet retention and include them in eDiscovery
Files, email and chats Copilot reads through Microsoft GraphYes, same terms as the underlying serviceFix permissions, because Copilot follows them
Web search queries sent to BingNoTurn web search off for ePHI roles
Agents and connectors from other vendorsDepends on that vendor’s termsApprove each agent and get a BAA if PHI is involved
Consumer Copilot with a personal accountNoTrain staff and restrict personal accounts on managed devices

Why is oversharing in SharePoint and OneDrive the main HIPAA risk with Copilot?

Because Copilot shows each user whatever that user can already open, and in most tenants staff can open far more ePHI than their jobs require. Copilot does not create new access. It turns forgotten access into instant answers.

HIPAA’s minimum necessary standard at 45 CFR 164.502(b) requires reasonable efforts to limit PHI to the minimum necessary for a use or disclosure. For internal use, 45 CFR 164.514(d)(2) is more specific: identify the people or classes of people in your workforce who need PHI, the categories of PHI each needs and the conditions of access, then make reasonable efforts to limit access to match. HHS guidance on the minimum necessary requirement allows broad access where a role truly needs it, such as clinicians involved in treatment, but the policy has to say so.

Oversharing breaks those rules in practice. The usual sources are ordinary: a billing export on a team site shared with Everyone except external users, scanned intake forms in a OneDrive folder shared through a People in your organization link, an old project site nobody owns. Before Copilot, obscurity protected those files. After Copilot, a front desk employee who asks about a patient’s balance may get a summary built from records they should never see.

The cleanup is the work in our earlier post on Copilot readiness and SharePoint oversharing: data access governance reports in SharePoint Advanced Management, site access reviews for owners, Restricted Content Discovery on sensitive sites still under review, and Specific people as the default sharing link. In a healthcare tenant, start with billing, intake, HR and any site holding exports from the EHR.

How do sensitivity labels and Purview DLP keep ePHI out of Copilot answers?

Labels that apply encryption limit what Copilot can summarize, and a Purview DLP policy for Copilot can stop it from processing labeled files and email at all.

When a label encrypts a file, Copilot returns content only if the user has both the VIEW and EXTRACT usage rights. A user with view rights but no extract right gets a link, not a summary. When Copilot in Word, PowerPoint or Outlook creates something from a labeled file, the new content inherits the highest priority label. A Confidential PHI label that encrypts content for clinical and billing groups does real work here.

Purview DLP for Microsoft 365 Copilot adds a policy location for Copilot and Copilot Chat. A rule that matches chosen sensitivity labels stops Copilot from using those files and emails in responses, although the item can still appear as a citation. Microsoft licenses this control with E5 level compliance plans, not Business Premium or E3. A second control, in preview, stops Copilot from answering prompts that contain sensitive information types, including custom types for medical record numbers. It checks typed prompt text, not uploaded files.

How do you audit Copilot interactions in Microsoft Purview?

Purview Audit logs Copilot interactions automatically when auditing is on, which supports the HIPAA audit controls standard at 45 CFR 164.312(b). Each record shows who used Copilot, when, where, and which files or sites it accessed.

Two details catch people. Audit records do not contain the text of prompts and responses; that text sits in a hidden folder in each user’s mailbox, where eDiscovery and Purview Data Security Posture Management can reach it. And Audit (Standard) keeps records for 180 days. Even with Audit (Premium), Copilot records stay at 180 days unless you create a custom audit retention policy, because the default one year policy covers only Exchange, SharePoint, OneDrive and Entra records.

Build Copilot into the activity review that 45 CFR 164.308(a)(1)(ii)(D) already requires. A monthly audit search filtered to Copilot interactions, compared with who should be touching ePHI sites, is a practical start. Add a Purview retention policy for Copilot interactions so your records schedule decides how long chats are kept.

What should you add to your HIPAA risk analysis before turning Copilot on?

Treat Copilot as new technology that changes how ePHI is reached, and update the risk analysis before licenses go live. HHS guidance on risk analysis names planning to incorporate new technology as a reason to perform one, and 45 CFR 164.308(a)(8) calls for evaluation in response to environmental or operational changes affecting the security of ePHI.

Add the new places ePHI can live: Copilot interaction history in mailboxes, files staff upload to Copilot Chat, which land in OneDrive, and Copilot Pages and Notebooks. Rate the new threats, such as overshared sites surfacing in answers, patient details reaching Bing, and inaccurate drafts copied into the chart, and record the controls that answer each one. Our guide to a HIPAA risk analysis in Microsoft 365 covers the method. This is the Copilot addendum, in order:

  1. Confirm Copilot appears in the in scope list on Microsoft’s HIPAA page and keep a dated copy with your BAA records.
  2. Close overshared sites and links that hold ePHI, and put Restricted Content Discovery on what is still under review.
  3. Publish sensitivity labels and apply an encrypting PHI label to the highest risk locations.
  4. Turn off web search, or limit it to web mode, for staff who handle ePHI, and approve agents one at a time.
  5. Confirm Purview Audit is on, set retention for Copilot interactions and schedule the monthly review.
  6. Update the risk analysis, the minimum necessary policy and workforce training, then license a pilot group whose access you have already reviewed.

Our HIPAA aligned Microsoft 365 work follows this sequence, and our Copilot readiness service handles the SharePoint cleanup and labels, alongside the HITRUST e1 and i1 work we do for healthcare clients.

If you are weighing Copilot for a team that touches patient data, book a 30 minute call and we will walk through what your tenant would expose on day one.

Frequently asked questions

Do we need to sign a separate BAA with Microsoft before using Copilot?

No. Microsoft offers its HIPAA Business Associate Agreement through the Data Protection Addendum by default to customers that are covered entities or business associates, so there is nothing extra to sign for Copilot. Download the current BAA from the Service Trust Portal, confirm Copilot appears in the in scope list, and file both with your vendor records.

Can staff paste patient details into a Copilot prompt?

With a work account, prompts and responses fall under enterprise data protection and the BAA, but the minimum necessary standard still applies to what staff share. The exposure is web search, because generated queries sent to Bing are outside the BAA. Turn web search off for roles that handle ePHI and consider a Purview DLP policy for sensitive prompts.

Does Copilot Chat without a Microsoft 365 Copilot license carry the same protections?

Copilot Chat used with a work account is covered by enterprise data protection, and Microsoft lists it among the in scope services for its BAA. It mainly works from web data and files people add to a prompt, so the web search exclusion matters even more. Apply the same web search settings and training to Copilot Chat users.

Can Copilot drafts go straight into a patient’s chart?

Not without review. Microsoft states that generative AI responses are not guaranteed to be factual and that users should check output before sharing it. Write a policy that requires a clinician or qualified staff member to review any Copilot draft that becomes part of the record, and cover that rule in workforce training.

How long should we keep Copilot interaction history?

HIPAA does not set a retention period for chat history, so align it with your records schedule and any state rules. Use a Microsoft Purview retention policy for Copilot interactions so the decision is made centrally. The Security Rule separately requires keeping required documentation, such as policies and risk analyses, for six years.

Keep reading

Related guides

Have a question this raised?

Bring it to a 30 minute call and leave knowing where you stand and what comes next.

Book a 30 minute call

(786) 577-9743sales@ethereumtech.ai

Or take the two minute starting point check