Is Microsoft Copilot HIPAA compliant?
A healthcare organization can use Microsoft Copilot and Azure OpenAI-based chatbots under HIPAA, with conditions. The contractual condition is met by Microsoft: it lists Microsoft Copilot and Microsoft Copilot Chat among the Office 365 services in scope for its HIPAA Business Associate Agreement, in both Commercial and GCC environments (Microsoft Learn, Health Insurance Portability and Accountability Act (HIPAA) & Health Information Technology for Economic and Clinical Health (HITECH) Act, accessed 2026-10-20), and it states that Microsoft Copilot Studio is covered under the HIPAA BAA (Microsoft Learn, Ensure compliance with Copilot Studio, accessed 2026-10-20). The configuration condition is the covered entity's to meet, and it is where most deployments fall short. "Is Microsoft Copilot HIPAA compliant" is therefore the wrong question; the right one is whether the tenant it runs in has been made ready for PHI. EPC Group, a Houston-based Microsoft consulting firm, deploys governed AI for healthcare clients and treats the readiness work as the project, with the Copilot license assignment as its last step.
Can we use Copilot with PHI?
Three Microsoft statements define what Copilot does with organizational data. First, prompts, responses and data accessed through Microsoft Graph are not used to train foundation large language models, including those used by Copilot (Microsoft Learn, Data, Privacy, and Security for Microsoft Copilot, accessed 2026-10-20). Second, Copilot surfaces only organizational data to which the individual user has at least view permission, which is why Microsoft tells customers to use the permission models in SharePoint and the other services to make sure the right people have the right access (same source). Third, when content is encrypted by Microsoft Purview Information Protection, Copilot honors the usage rights granted to the user, and Copilot and agents return data from a labeled item only if the user holds the EXTRACT usage right (Microsoft Learn, Learn about sensitivity labels, accessed 2026-10-20).
The practical consequence: Copilot does not create new access to PHI, but it makes existing overshared access easy to find. A clinician with incidental read access to a billing library that was shared to "everyone" years ago can now ask Copilot to summarize it. EPC Group's order of work for Copilot with PHI is therefore to audit and tighten SharePoint and OneDrive sharing, publish a PHI sensitivity label that applies encryption, extend Purview DLP to the Microsoft 365 Copilot location (Microsoft Learn, Learn about data loss prevention, accessed 2026-10-20), and confirm that Copilot interaction data is retained and searchable through Microsoft Purview with a retention policy set (Microsoft Learn, Data, Privacy, and Security for Microsoft Copilot, accessed 2026-10-20). Only then are licenses assigned, to a pilot group first.
HIPAA-ready chatbots on Azure OpenAI
A custom chatbot built on Azure OpenAI in Microsoft Foundry raises different questions, because the covered entity owns the application layer. Microsoft's commitments for models sold by Azure are that prompts, completions, embeddings and training data are not available to other customers or to OpenAI, are not used by the model providers to improve their models, and are not used to train any generative AI foundation model without the customer's permission; the models are stateless and store no prompts or completions; and prompts and responses are processed within the customer-specified geography unless a Global or DataZone deployment type is chosen (Microsoft Learn, Data, privacy, and security for Models sold by Azure in Microsoft Foundry, change log dated 2025-10-03). Azure and Azure Government are listed as in-scope platforms for the Microsoft HIPAA BAA (Microsoft Learn, HIPAA & HITECH Act, accessed 2026-10-20).
Two details decide whether a chatbot is HIPAA-ready. The first is abuse monitoring: by default the service may store a sample of prompts and completions for human review when abuse indicators are detected, and customers can apply for modified abuse monitoring so that this storage and human review are not performed (same source). EPC Group files that request for every PHI workload before go-live and verifies the ContentLogging capability shows false. The second is logging: because the models keep nothing, the application must write each request and response to the covered entity's own storage with the user identity, timestamp and the grounding data used. EPC Group also deploys the service behind a virtual network with private endpoints, which Azure OpenAI supports (Microsoft Learn, Azure OpenAI frequently asked questions, accessed 2026-10-20), and uses the "on your data" pattern so PHI stays in the designated data source rather than being copied into the model service (Microsoft Learn, Data, privacy, and security for Models sold by Azure in Microsoft Foundry, change log dated 2025-10-03).
The controls a HIPAA-ready AI deployment needs
- A BAA scope check for every AI service before it touches PHI, repeated when Microsoft revises the in-scope list.
- Permission hygiene in SharePoint, OneDrive and Teams, so Copilot has nothing overshared to find.
- A PHI sensitivity label with encryption, and DLP extended to Copilot and to Teams chat.
- Interaction logging with retention set in Purview for Copilot, and application-level logging for Azure OpenAI.
- Modified abuse monitoring approved for Azure OpenAI PHI workloads, with the setting verified.
- A written AI governance policy with human review of any output that reaches a patient or a record.
EPC Group's Copilot consulting practice runs the Copilot readiness and pilot, and its data governance consulting practice runs the classification, labeling, DLP and retention work that both Copilot and custom chatbots depend on.
Documented work
ANON-CASES: EPC Group engagement data in healthcare covers mid-size and large covered entities and business associates, including provider organizations and revenue-cycle firms, for which EPC Group has governed Copilot rollouts and Azure OpenAI assistants that handle PHI. Client names are not published here, and engagements are described by industry and organization size only. No outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.
Primary sources
- Learn about sensitivity labels — Microsoft Learn, accessed 2026-10-20
- Microsoft Purview service description — Microsoft Learn, accessed 2026-10-20
- HIPAA & HITECH Act — Microsoft Learn, accessed 2026-10-20
- Ensure compliance with Copilot Studio — Microsoft Learn, accessed 2026-10-20
- Learn about data loss prevention — Microsoft Learn, accessed 2026-10-20
- Azure OpenAI frequently asked questions — Microsoft Learn, accessed 2026-10-20
Frequently Asked Questions
Is Microsoft 365 Copilot covered under the Microsoft BAA?
Yes. Microsoft lists Microsoft Copilot and Microsoft Copilot Chat among the Office 365 services in scope for its HIPAA Business Associate Agreement (Microsoft Learn, Health Insurance Portability and Accountability Act (HIPAA) & HITECH Act, accessed 2026-10-20). Microsoft notes that Microsoft 365 Copilot is now named Microsoft Copilot and that the rename changes nothing about security, compliance or privacy (Microsoft Learn, Data, Privacy, and Security for Microsoft Copilot, accessed 2026-10-20). Coverage under the BAA does not by itself make a deployment HIPAA compliant; configuration and policy still decide that.
Does Azure OpenAI train on customer data?
No. Microsoft states that prompts, completions, embeddings and training data submitted to Azure OpenAI are not available to other customers or to OpenAI, and are not used to train any generative AI foundation model without the customer’s permission; the models are stateless and store no prompts or completions (Microsoft Learn, Data, privacy, and security for Models sold by Azure in Microsoft Foundry, change log dated 2025-10-03). Abuse monitoring may store prompts for human review unless the customer is approved for modified abuse monitoring (same source).
How do sensitivity labels and Purview control what Copilot can see?
Copilot surfaces only data the signed-in user already has at least view permission to, and when content is encrypted by a sensitivity label it honors the usage rights granted to that user (Microsoft Learn, Data, Privacy, and Security for Microsoft Copilot, accessed 2026-10-20). Copilot and agents return data from a labeled item only if the user holds the EXTRACT usage right (Microsoft Learn, Learn about sensitivity labels, accessed 2026-10-20). EPC Group therefore fixes SharePoint oversharing and publishes a PHI label with encryption before Copilot licenses are assigned.
What logging is needed for AI interactions with PHI?
Every prompt and response involving PHI should be retained, searchable and governed. Microsoft stores the content of Copilot interactions, exposes it through Content search and Purview, and lets administrators set retention policies for Copilot chat data (Microsoft Learn, Data, Privacy, and Security for Microsoft Copilot, accessed 2026-10-20). Purview Audit (Premium) provides extended retention and analysis for Copilot audit records (Microsoft Learn, Microsoft Purview service description, accessed 2026-10-20). For Azure OpenAI chatbots, EPC Group adds application-level logging to the client’s own storage, since the models keep none.
What does a HIPAA AI governance policy contain?
EPC Group’s policy template for healthcare clients has seven sections: the approved AI services, with a BAA scope check for each; the PHI data classes permitted and prohibited in prompts; identity and access rules for who may use each assistant; labeling and DLP requirements that must be in place before a service is enabled; logging, retention and eDiscovery requirements for interactions; human review requirements for any output that reaches a patient record or a patient; and an incident procedure for suspected PHI exposure via AI, tied to breach notification.
Talk to a senior architect
If your organization wants Copilot or a custom assistant in front of clinicians or revenue-cycle staff and your compliance officer has not yet signed off, a 30-minute discovery call with a senior EPC Group architect will cover the BAA scope check, the permission audit and the logging design. See the Copilot consulting service hub for engagement structures.
Email contact@epcgroup.net or call 888-381-9725.
a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.