Is Microsoft Copilot HIPAA compliant? The 2026 answer per Copilot surface — M365 Copilot, Copilot Studio, GitHub Copilot, consumer Copilot — plus the gap a BAA does not close.
Yes for Microsoft 365 Copilot under the existing M365 BAA, and qualified yes for Azure-hosted Copilot under the Azure BAA. No for consumer Copilot. HIPAA compliance for Copilot requires:
Microsoft's HIPAA / HITECH section in the Service Trust Portal and the Microsoft 365 Compliance documentation define the covered surface. A simplified summary for the AI-relevant products:
The most common mistake: assuming GitHub Copilot inherits the Microsoft 365 BAA because GitHub is owned by Microsoft. GitHub has its own BAA scope and a developer pasting PHI into a copilot.com extension prompt is not automatically covered.
Source link: Microsoft HIPAA/HITECH Compliance — verify against Microsoft's current docs before signing.
Yes for customers on a covered M365 SKU with the existing Microsoft 365 BAA in place. This is the most-deployed Copilot surface for enterprises — the assistant that lives inside Outlook, Word, Excel, PowerPoint, Teams, SharePoint, and OneDrive. The Microsoft 365 BAA most enterprise customers already have generally extends to M365 Copilot when:
That gives Microsoft's BAA-covered processing. It does not give your security team visibility into what PHI users actually paste into a Copilot prompt, what PHI Copilot retrieves from SharePoint when summarizing a document, or what PHI a Teams meeting transcript captures.
Generally yes when built on HIPAA-eligible Azure and Power Platform services, with the right BAAs in place. Copilot Studio is the platform for building custom copilots — internal AI agents that connect to line-of-business systems via connectors. The compliance posture depends on:
A custom Copilot Studio agent that pulls patient data from a connected EHR connector, runs it through an Azure OpenAI prompt, and writes a summary back to SharePoint can be deployed in a HIPAA workflow if every service in the chain is HIPAA-eligible and the BAAs are in place. The compliance failure mode is usually an adjacent service in the pipeline that is not on the HIPAA-eligible list — a Cloud Function, a third-party connector, a monitoring tool — quietly logging PHI outside the BAA boundary.
Treat GitHub Copilot as "do not paste PHI" unless GitHub explicitly confirms BAA coverage for your account. GitHub Copilot is a code-completion service designed for source code. The training data and inference path are not the same as M365 Copilot. Healthcare engineering teams routinely have PHI in test fixtures, seed scripts, and mocked data — that is where the practical exposure happens.
The practical guidance:
No. Consumer Copilot (copilot.microsoft.com under a personal Microsoft account, the Copilot mobile app on a personal phone) is outside any Microsoft BAA. A clinician who pastes a patient note into the Copilot app on their personal phone has transmitted PHI to a non-BAA-covered service.
This is the most-overlooked Copilot exposure in healthcare orgs. The org has Microsoft 365 under BAA — but employees use personal Copilot on the side. The data flow Microsoft sees is from a personal account, not the covered M365 tenant.
A BAA is a contractual document. It commits Microsoft to handle PHI under HIPAA's Privacy, Security, and Breach Notification rules. It does not:
A BAA covers Microsoft's processing of the data you sent. It does not minimize, redact, or restrict the data you send. That responsibility is on the covered entity. Most healthcare organizations only realize this gap after a near-miss.
Strac is the data-layer control that closes the gap a BAA doesn't cover. Strac sits between users and Copilot surfaces, between AI agents and Microsoft 365 data, and between endpoints and the model.
Browser extension for Copilot in the browser — Strac's GenAI browser DLP inspects copy/paste, typed text, and file uploads to copilot.microsoft.com, Copilot in Edge, and any other browser-based Copilot surface. Modes: alert, warn, block. PHI never crosses into the model context. Even on consumer Copilot, the browser extension enforces the same controls.
MCP DLP for Copilot-driven AI agents over Microsoft 365 data — Modern AI workflows involve a Copilot-powered agent reading from SharePoint, OneDrive, Outlook, Teams, and Loop. Strac's Microsoft 365 MCP DLP intercepts those tool calls and redacts PHI inline:
Endpoint DLP for desktop Copilot integrations — Strac's endpoint DLP on Mac and Windows catches file-level exfil that browser controls miss — a Copilot-integrated VSCode session pulling source files with PHI in test fixtures, a Copilot for desktop ingesting screenshots from the clipboard.
Cloud DSPM for Azure-hosted Copilot Studio applications — For custom Copilot Studio agents calling Azure OpenAI or Azure AI services, Strac's cloud DSPM keeps the upstream data stores classified, so engineering teams know which datasets are HIPAA-sensitive before piping them into a prompt template.
Coverage across the broader SaaS surface AI agents touch — Microsoft 365 is rarely the only surface in play. Strac's Slack MCP DLP, Salesforce MCP DLP, Zendesk MCP DLP, and the full MCP cluster extend the same redaction pattern across every AI-agent-reachable SaaS app.
Compliance evidence pre-built — HIPAA mapping, audit log export, and per-event remediation evidence ready for your auditor without a custom integration.
Setup is agentless and under 10 minutes per workspace.
Phase 1 — Inventory and BAA
Phase 2 — Data layer controls
Phase 3 — Governance and audit
No. Consumer Copilot is outside any Microsoft BAA. Healthcare data sent to consumer Copilot is sent to a non-covered service.
Yes for customers on a covered M365 SKU with the M365 BAA executed. Most enterprises already have the M365 BAA in place and can extend it to Copilot by confirming the SKU and configuration in the Service Trust Portal.
Generally yes when built on HIPAA-eligible Azure and Power Platform services with the right BAAs. Verify every connector and adjacent service used in the agent is on Microsoft's HIPAA-eligible list — that is usually where compliance failures hide.
Treat GitHub Copilot as "do not paste PHI" unless GitHub explicitly confirms BAA coverage. The practical guidance: de-identify test fixtures, use endpoint DLP, and use GitHub MCP DLP for repos that AI agents can ingest.
No. Microsoft's BAAs require a paid Microsoft 365 plan with the BAA executed, or a paid Azure agreement. Free consumer accounts are outside the program.
Microsoft offers BAAs for its enterprise Copilot surfaces (M365 Copilot, Azure-hosted Copilot, most Copilot Studio configurations). Anthropic does not currently offer a BAA for Claude consumer or Claude Cowork plans — see Is Claude HIPAA compliant?. Both vendors leave the same data-layer gap that a BAA alone does not close.
Both Microsoft and Google offer BAAs for their enterprise AI surfaces. The practical difference: Microsoft 365 is the largest enterprise productivity surface and most healthcare orgs already have the M365 BAA in place, which simplifies Copilot onboarding. Google Workspace's BAA path is similar but the SKU verification is more variable. See Is Gemini HIPAA compliant? for that comparison.
Strac's browser DLP, endpoint DLP, and Microsoft 365 MCP DLP redact PHI before it reaches Copilot, regardless of which Copilot surface a user is on. A signed M365 BAA covers Microsoft's processing of the data you send. Strac controls what data gets sent in the first place. The combination — M365 BAA + Strac data-layer protection — is what most healthcare auditors want to see.
Purview is good for tenant-scoped data classification and DLP inside the Microsoft 365 environment. It is necessary. It is not sufficient. Purview struggles with non-Microsoft SaaS (Slack, Salesforce, HubSpot, Notion), with AI agent / MCP tool calls outside the M365 boundary, and with browser-side enforcement on consumer Copilot. Strac complements Purview by extending data-layer protection across every surface AI agents actually touch. See Microsoft Purview alternatives for the full breakdown.
Yes. Strac's browser extension supports a block mode that prevents copy/paste and uploads into Copilot until you have the controls in place. Many healthcare orgs use a phased rollout: block in week one, warn-and-allow in week two after browser DLP is tuned, full rollout in week three.
Microsoft Copilot is one of the more HIPAA-friendly AI assistants for enterprises today — most enterprise customers already have the M365 BAA, and Microsoft's compliance posture is mature. But "covered under a BAA" is not the same as "safe to use with PHI." The remaining gap — what users paste, what agents retrieve, what files reach the model — is what Strac is built to close.
See how Strac protects Microsoft Copilot in your environment — book a demo →
.avif){kind=icon}
.gif)
.webp)
