Skip to main content

Is Microsoft Copilot HIPAA compliant? The BAA, what it covers and what stays with you

By Joseph Abear ·
Two panels showing which Microsoft Copilot products are in scope for the Microsoft BAA when properly configured, and what sits outside it: web search queries, personal plans and agents from other vendors.

Last updated: November 17, 2026

Is Copilot HIPAA compliant? The work version can be. Microsoft says Microsoft Copilot and Microsoft Copilot Chat support HIPAA compliance for properly configured implementations, under its business associate agreement (BAA). Web search queries are not covered, and consumer Copilot is a different product. So the answer depends on which Copilot your staff open and how you set it up.

This guide is for IT, security and compliance leads at health systems and multi-site groups. The same steps work for a small clinic on a business plan. We are HIPAA Compliant Hosting, and we sell managed hosting, not Copilot. Weigh the one marked section about our plans as a disclosure.

TL;DR: Quick answer

  • Work Copilot is in scope. Microsoft lists Microsoft Copilot and Microsoft Copilot Chat among the services its HIPAA BAA covers.

  • The BAA comes by default. Microsoft says the BAA comes through its Data Protection Addendum. It applies to covered entities and business associates.

  • Web search is outside it. Microsoft says HIPAA compliance does not apply to web search queries, because its data terms do not cover them.

  • Consumer Copilot is not the same product. Microsoft's HIPAA page does not list personal plans. Keep protected health information (PHI) out of them.

  • Setup decides it. A Copilot HIPAA compliant rollout needs clean permissions, labels, logs and staff rules. Microsoft says the customer owns its own compliance.

Is Copilot HIPAA compliant?

It can be, if you use the work version under Microsoft's BAA and configure it properly. No tool is HIPAA compliant by itself. HIPAA applies to how a covered entity or business associate uses a tool.

Microsoft's own wording is careful. One page says the two work products "support HIPAA compliance for properly configured implementations" and no more. Its HIPAA page adds a warning. Using Microsoft services "doesn't on its own achieve HIPAA compliance" for you.

Microsoft also says no certification settles the question. Its HIPAA page notes that HHS approves no certification standard for a business associate. So a Copilot HIPAA compliant claim rests on two things: the contract and your setup.

The contract comes first. Under 45 CFR 164.308(b), a vendor may handle electronic PHI (ePHI) for you only after you get satisfactory assurances in a BAA. Our guide to the business associate agreement covers what that contract must say.

Which Copilot products does Microsoft's BAA cover?

Table of five Copilot products and their status under the Microsoft BAA: Microsoft Copilot and Copilot Chat for work in scope, Copilot Studio covered, web search not covered, personal Copilot not listed.

Microsoft sells several products with Copilot in the name. Each has its own answer. So "is Copilot HIPAA compliant" is really nine questions. Check the exact product before PHI goes near it.

Product

What Microsoft says

What to do

Microsoft Copilot (work, with Microsoft 365)

Listed as in scope for the HIPAA BAA. Supports HIPAA compliance when properly configured

Use it under the BAA, with the setup steps below

Microsoft Copilot Chat (work)

Listed as in scope. Same wording as above

Sign in with a work account. Govern web search

Web search inside Copilot

HIPAA compliance does not apply to web search queries

Keep PHI out of prompts that search the web, or restrict the feature

Copilot Studio

Covered under the HIPAA BAA. Not intended for use as a medical device

Review each agent you build and the data it reaches

Security Copilot

Listed and covered by the BAA

Treat it like any other covered service

Dragon Copilot (clinical dictation and ambient notes)

Its security paper says Microsoft treats all customer data as though it is PHI. We found no BAA statement there

Get the BAA terms for it in writing

Consumer Copilot (personal and family plans)

Not listed on Microsoft's HIPAA page

No PHI

Copilot Health (consumer)

A direct-to-consumer wellness product. Microsoft says HIPAA does not apply to most such products

No PHI from your organization

GitHub Copilot

The responsible use page we read does not mention HIPAA or a BAA

Ask GitHub in writing first

Microsoft's pages now call the work products Microsoft Copilot and Microsoft Copilot Chat. Product names change often, so match the name in your license to the name on Microsoft's HIPAA page.

How do you get Microsoft's BAA for Copilot?

You do not sign a separate form. Microsoft says its HIPAA BAA comes by default through the Microsoft Online Services Data Protection Addendum. It applies to all customers that are covered entities or business associates.

That is true for a health system on an enterprise agreement and for a five-person clinic on a business plan. The step that makes Copilot HIPAA compliant on paper is the same for both. Read the BAA text, confirm your plan falls under the addendum, and keep a copy in your vendor file.

Then check the scope. The BAA covers the services Microsoft lists as in scope. It does not cover an add-on, agent or connector from another company. Our Microsoft 365 HIPAA guide covers the BAA and setup for the wider suite.

What does the BAA leave out?

Three gaps the Microsoft BAA leaves open for Copilot: web search queries that go to Bing, agents and add ons from outside vendors that need their own BAA, and personal accounts outside your tenant.

Three gaps matter most. Each one can undo a Copilot HIPAA compliant setup if you miss it.

  • Web search. When Copilot grounds an answer on the web, it sends a search query to Bing. Microsoft says its data terms do not cover those queries. It acts as an independent data controller for them. A prompt that names a patient can leak into that query.

  • Agents and add-ons. Microsoft tells admins to check the privacy statement and terms of each agent. An agent from another vendor is that vendor's product. It needs its own BAA before it handles PHI.

  • Personal accounts. Staff who use Copilot on a personal plan are outside your tenant and your contract. That is shadow AI, and it is common. Our guide to AI patient data privacy covers how to manage it.

What does Copilot do with your prompts and files?

For the work products, Microsoft makes four promises. Each one matters when you judge a Copilot HIPAA compliant setup.

  • No model training. Microsoft says prompts, responses and data reached through Microsoft Graph do not train foundation models.

  • Existing permissions apply. Copilot only shows data that the user can already view.

  • Labels are honored. Microsoft says Copilot honors the usage rights that sensitivity labels grant to the user.

  • Chats are stored and searchable. The prompt and the response are stored. Admins can search them in Microsoft Purview and set retention policies.

The second point cuts both ways. Copilot does not widen access, but it makes existing access easy to use. A shared folder that everyone can open was a small risk when nobody looked. With Copilot, any user can ask for its contents in one sentence.

That is a minimum necessary problem. Under the minimum necessary standard, staff should reach only the PHI their job needs. Fix oversharing before you turn Copilot on, not after. No Copilot HIPAA compliant setup survives a folder that all staff can open.

How do you make Copilot HIPAA compliant in practice?

Checklist of eight setup steps before staff use Copilot with PHI: confirm the BAA, require work accounts, govern web search, clean up permissions, label PHI, turn on audit and retention, review every agent, update risk analysis and training.

Eight steps turn the contract into a working setup. They scale from a large health system down to a small clinic.

  1. Confirm the BAA. Check that your plan falls under the Data Protection Addendum. File the BAA text.

  2. Require work accounts. Staff sign in with their organization account. Block or ban personal Copilot for work.

  3. Govern web search. Microsoft publishes admin guidance on managing public web access for Copilot. Restrict it for groups that handle PHI, or train staff to keep identifiers out.

  4. Clean up permissions. Review sites, folders and mailboxes that hold PHI. Remove "everyone" access.

  5. Label PHI. Apply sensitivity labels so usage rights follow the file.

  6. Turn on audit and retention. Keep Copilot interactions under the same log and retention rules as other PHI systems. Our guide to HIPAA audit logs covers what to keep.

  7. Review every agent. List each agent and connector, the data it reaches and its vendor's BAA.

  8. Update your risk analysis and training. Add Copilot to your HIPAA risk analysis. Teach staff what not to paste.

None of these steps is special to AI. They are the access, audit and contract controls the Security Rule already asks for. A Copilot HIPAA compliant rollout is those controls, applied before launch.

What changes for a health system and for a small clinic?

Side by side comparison of a Copilot rollout. Health systems: the hard part is scale, permissions review first, pilot group then rollout. Small clinics: the hard part is habit, work accounts only, a one page staff rule.

The rules are the same. The work to keep Copilot HIPAA compliant is not.

  • Health systems and multi-site groups. The hard part is scale. Years of shared sites, merged tenants and broad groups mean real oversharing. Plan a permissions review and a pilot group before a full rollout. Treat Copilot as a new vendor review, even though Microsoft is an old vendor. Our guide to a HIPAA vendor risk assessment lists the proof to ask for.

  • Small clinics. The hard part is habit. One shared mailbox and a few folders are quick to fix. The bigger risk is staff using personal Copilot or another free chatbot. A one-page rule and work accounts solve most of it.

In both cases, ask the same question before go-live. Can a user who should not see a chart get it by asking Copilot? If yes, the setup is not Copilot HIPAA compliant yet.

Where does our hosting fit, and where does it not?

We do not sell or resell Copilot, and our hosting does not make Copilot HIPAA compliant. We sell this, so weigh it as a disclosure.

  • Where we fit. Your website, patient portal or app that holds PHI. Copilot does not host those.

  • BAA. We sign the BAA within 24 hours of signup, before patient data moves. Our BAA covers the servers and services we run. Email, SMS, EHR, form and AI model vendors need their own BAA.

  • Safeguards. Every plan includes CloudFront CDN, a web application firewall (WAF), encryption at rest and in transit, six-year audit logging and tested encrypted backups.

  • What stays with you. Your Microsoft tenant, its permissions and its Copilot settings stay with you and Microsoft.

Monthly plans have no long-term contract. Managed plans from $229 a month.

Frequently asked questions

Is Copilot HIPAA compliant?

The work version can be. Microsoft lists Microsoft Copilot and Microsoft Copilot Chat as in scope for its HIPAA BAA. It says they support HIPAA compliance for properly configured implementations. Web search queries are not covered.

Does Microsoft sign a BAA for Copilot?

Microsoft says its HIPAA BAA is available by default through the Data Protection Addendum. It applies to customers that are covered entities or business associates. You do not sign a separate form.

Is the free or personal Copilot HIPAA compliant?

Do not use it with PHI. Microsoft's HIPAA page lists the work products, not personal plans. Staff who use a personal account are outside your contract with Microsoft.

Can staff put patient information into Copilot?

Only in the work version, under the BAA, with a Copilot HIPAA compliant setup. Even then, keep patient identifiers out of prompts that search the web. Share only the PHI the task needs.

Does Copilot train on our data?

Microsoft says no for the work products. It says prompts, responses and data accessed through Microsoft Graph are not used to train foundation models.

Recap: is Copilot HIPAA compliant?

Is Copilot HIPAA compliant? Only as you set it up. The work products are in scope for Microsoft's BAA, and web search and personal plans are not. Confirm the contract, fix permissions, govern web search and train staff. Then add Copilot to your risk analysis like any other system that touches PHI.

This article is general information, not legal advice. Microsoft's terms, product names and features are as read on November 17, 2026, and they change often. Check Microsoft's current pages and your own agreement, and ask counsel about contract terms. We sell HIPAA compliant hosting. Reviewed November 2026.

Sources

Read full definition

View link to copy manually

Stay current on HIPAA hosting

Practical guidance on compliance, hosting and the rules that actually apply to your practice.