--- title: "Is GitHub Copilot HIPAA Compliant? A 2026 Guide for Healthcare Developers" description: "GitHub Copilot is not HIPAA compliant by default on any tier. Here is what HIPAA actually requires of an AI coding assistant, why GitHub is not on Microsoft's…" url: "https://sonomos.ai/blog/is-github-copilot-hipaa-compliant-2026/" source: "https://sonomos.ai/blog/is-github-copilot-hipaa-compliant-2026/" --- [Back to Blog](https://sonomos.ai/blog/) May 7, 202613 min readLast reviewed: October 1, 2026 HIPAA GitHub Copilot Healthcare Engineering AI Compliance # Is GitHub Copilot HIPAA Compliant? A 2026 Guide for Healthcare Developers S [Sonomos Research](https://sonomos.ai/team/) · Sonomos The Sonomos research team writes about AI privacy, data protection, and how to use generative AI safely at work. **Short answer:** GitHub Copilot is not HIPAA compliant by default on any tier. We could not confirm any Business Associate Agreement (BAA) that covers GitHub Copilot, and GitHub does not appear on the lists of in-scope services on [Microsoft's HIPAA page](https://learn.microsoft.com/en-us/compliance/regulatory/offering-hipaa-hitech), so do not assume that Microsoft's BAA reaches GitHub Enterprise Cloud or Copilot. Only a signed agreement that expressly names the Copilot features you use should change that, and even then the compliance posture depends on what code the developer feeds the model. This guide explains what [HIPAA](https://sonomos.ai/glossary/hipaa/) actually requires of an AI coding assistant, which GitHub plans give you the most administrative control, and how healthcare engineering teams can use AI code assistance without putting [protected health information (PHI)](https://sonomos.ai/glossary/protected-health-information/) into a non-covered model. _Last reviewed October 1, 2026 against the regulations and vendor documentation listed under [Sources and primary references](#sources-and-primary-references)._ ## What HIPAA requires of an AI tool used in healthcare software development HIPAA regulates **covered entities** (hospitals, clinics, health plans, clearinghouses) and their **business associates** (vendors that create, receive, maintain, or transmit PHI on the covered entity's behalf). A software developer writing code that touches a healthcare system is often a business associate. When that developer pastes a patient record, a medical schema, or a sample API response containing real PHI into an AI coding assistant, two things happen simultaneously: 1. The PHI leaves the developer's device and travels to the AI provider's infrastructure. 2. The developer (and the covered entity they work for) may have just made an unauthorized disclosure. HIPAA requires a signed [Business Associate Agreement (BAA)](https://sonomos.ai/glossary/business-associate-agreement/) before a covered entity lets a business associate receive PHI ([45 CFR 164.502(e)](https://www.ecfr.gov/current/title-45/section-164.502)). The BAA must commit the vendor to specific obligations, including limiting its use of PHI, using appropriate safeguards, reporting unauthorized uses and breaches, and returning or destroying PHI at termination ([45 CFR 164.504(e)](https://www.ecfr.gov/current/title-45/section-164.504)). Without a BAA, even a single prompt containing real patient data is an impermissible disclosure, which [45 CFR 164.402](https://www.ecfr.gov/current/title-45/section-164.402) presumes to be a breach unless a documented risk assessment shows a low probability of compromise. **The catch with coding assistants.** Developers often argue that they are not actually sharing PHI — they are pasting code structure, schemas, or test data. The distinction breaks down quickly: - A SQL query that references a real patient ID is PHI if it could identify the patient. - A sample API response with a real name, DOB, and diagnosis is PHI. - A code comment like "patient_id = 12345 (John Doe, DOB 1985-03-12)" is PHI. Code reviews can surface PHI embedded in tests, fixtures, seed files, and log snippets. The safer assumption is that any prompt from a healthcare codebase should be treated as potentially PHI-containing. ## GitHub Copilot tiers and their HIPAA posture ### GitHub Copilot Free / Individual No enterprise contract, no BAA, no DPA alignment with HIPAA. Prompts (called "suggestions context" in GitHub's documentation) are transmitted to GitHub's servers to generate completions. Training opt-out is available but does not change the fundamental BAA-ineligibility. **Verdict:** Not suitable for workflows involving PHI. ### GitHub Copilot Business Copilot Business adds organizational management, policy enforcement, and a commitment that GitHub will not use prompts for training by default. It also includes a **Data Protection Agreement** (DPA). However, as of 2026, the GitHub Copilot Business DPA does not include HIPAA BAA terms for Copilot specifically. **Verdict:** Significantly better than Individual from a privacy standpoint, but not BAA-covered for Copilot. Not suitable for PHI workflows without additional legal review. ### GitHub Copilot Enterprise (on GitHub Enterprise Cloud) Microsoft's HIPAA BAA covers the services on Microsoft's in-scope lists, and GitHub is not on the lists we reviewed ([Microsoft's HIPAA page](https://learn.microsoft.com/en-us/compliance/regulatory/offering-hipaa-hitech)). Earlier versions of this guide suggested that GitHub Enterprise Cloud might inherit Microsoft's BAA. We removed that suggestion because the in-scope lists do not support it. If your organization believes it holds an agreement covering GitHub Copilot, get it in writing, confirm that it names the Copilot features your developers use, and have counsel review it. Even with a signed agreement, a BAA is necessary but not sufficient. The organization still needs to: - Ensure Copilot Business or Enterprise is the tier in use (not individual seats). - Configure organization-level policies to disable public code suggestions and limit context sharing. - Train developers not to paste real PHI into prompts. - Log and audit AI-assisted development workflows. **Verdict:** Not suitable for PHI unless you hold a signed agreement that expressly covers the Copilot features you use, plus organizational controls on top. ### Alternative: Azure AI services for custom coding assistants Some healthcare engineering teams build their own code-assistance tooling on Azure's AI services. Microsoft's HIPAA page lists Azure and Azure Government as in-scope platforms, but the pages we reviewed name Azure at the platform level only. Confirm that the specific service and model deployment you plan to use is in scope under [Microsoft's Azure HIPAA offering](https://learn.microsoft.com/en-us/azure/compliance/offerings/offering-hipaa-us) and your agreement. This approach gives organizations more control but requires significantly more engineering investment. ## What "not sending PHI" actually means in practice The safest approach for healthcare developers is to never send real PHI into any AI coding assistant, regardless of tier. In practice that means: **Synthetic test data.** Replace all real patient values in test fixtures, seed files, and sample API responses with generated but realistic data (fake names, plausible-but-nonexistent MRNs, fabricated DOBs). Libraries like Faker can generate synthetic FHIR resources. **Schema without values.** When asking Copilot to help with a database migration or API schema, paste the table structure or schema definition — not a row export from production. **Code structure, not code in context.** "Help me write a FHIR R4 MedicationRequest resource parser" works without any patient data. "Debug why this parser fails on this record [pastes real patient data]" sends PHI. **Use Copilot Chat for architecture, not debugging.** Architectural and algorithmic questions rarely need real data. Debugging questions are the most likely to involve copy-pasted production content. **Local redaction at the keyboard.** A browser-level or IDE-level tool that detects PHI patterns — MRNs, DOBs, names combined with medical terms — before a prompt is submitted is the technical backstop when habit slips. This is particularly valuable in environments where developers paste from log files or Postman collections. ## Settings to configure for healthcare development teams If your organization uses GitHub Copilot Business or Enterprise: 1. **Disable suggestions matching public code.** Settings → Policies → Suggestions matching public code → Blocked. Reduces the risk of Copilot suggesting code that matches open-source repositories containing real-world PHI samples (rare but documented). 2. **Disable "Allow GitHub to use my code snippets for product improvements."** This is the training-opt-out for your organization. In Business/Enterprise, prompts are excluded from training by default; verify this in your admin console. 3. **Restrict which extensions can use Copilot APIs.** In VS Code and JetBrains, Copilot Chat can be invoked by third-party extensions. Limit this surface area. 4. **Enable audit logging.** GitHub Enterprise includes audit log streaming. Configure it so that your security team can review AI-assisted activity if a PHI exposure is suspected. 5. **Write a Copilot-specific acceptable-use addendum.** Your existing acceptable-use policy probably does not address AI coding assistants specifically. Add: prohibited uses (pasting real PHI), required practices (synthetic test data), and incident-response steps if a developer believes they pasted real data. ## How GitHub Copilot compares to alternatives for healthcare developers | Tool | BAA available? | Training opt-out | PHI-safe configuration possible? | | --- | --- | --- | --- | | GitHub Copilot Free/Individual | No | Yes (individual opt-out) | No | | GitHub Copilot Business | No (DPA only) | Yes (org-level) | No (without BAA) | | GitHub Copilot Enterprise (GHEC) | Not confirmed (GitHub is not on Microsoft's in-scope lists) | Yes (org-level) | No, without a signed agreement naming Copilot | | Amazon CodeWhisperer (Q Developer) | Not on the AWS HIPAA Eligible Services list we reviewed | Confirm with AWS | Not confirmed | | Kiro (AWS) | Requires an AWS BAA; listed as HIPAA eligible, excluding Kiro Web | Confirm with AWS | Yes, with an AWS BAA and in-scope features | | Azure AI services (custom) | Yes for in-scope Azure services; confirm the specific service | Yes | Yes, once the service is confirmed in scope | | Local/on-device models (Ollama, etc.) | N/A | N/A | Yes (no data leaves device) | For teams that cannot confirm a BAA or cannot fully control what developers paste, the practical answer is often to combine whatever AI coding assistant the team uses with a local-first redaction tool that masks PHI before it leaves the developer's machine — reducing the risk without blocking the workflow. ## Frequently asked questions ### Does GitHub have a HIPAA BAA for Copilot? We could not confirm any BAA that covers GitHub Copilot, and GitHub does not appear on the in-scope service lists on [Microsoft's HIPAA page](https://learn.microsoft.com/en-us/compliance/regulatory/offering-hipaa-hitech). Do not assume that GitHub Enterprise Cloud customers inherit Microsoft's BAA. If you hold an agreement that you believe covers Copilot, confirm in writing that it names the Copilot features you use. Treat GitHub Copilot Business and Individual accounts as not covered. ### Can I use GitHub Copilot to write HIPAA-compliant code? Yes — writing code that complies with HIPAA regulations is entirely different from using a HIPAA-covered tool. Copilot can help you write code that implements encryption, access controls, audit logging, and other HIPAA security controls. The HIPAA issue arises only if you paste real PHI (actual patient data) into the prompt. Copilot writing code that handles PHI is fine; Copilot receiving PHI as prompt input is not. ### What is the difference between a DPA and a HIPAA BAA? A Data Protection Agreement (DPA) is a general-purpose contract for GDPR-style data processor relationships. A Business Associate Agreement (BAA) is a HIPAA-specific contract whose required content is set out in [45 CFR 164.504(e)](https://www.ecfr.gov/current/title-45/section-164.504) and, for electronic PHI, in the Security Rule's business associate standard at [45 CFR 164.308(b)](https://www.ecfr.gov/current/title-45/section-164.308). GitHub Copilot Business includes a DPA; we could not confirm a HIPAA BAA for Copilot. The existence of a DPA does not satisfy HIPAA's BAA requirement. ### Is it safe to use Copilot to debug healthcare APIs? It depends on what you paste. If you paste an API request/response that contains real patient data (names, DOBs, MRNs, diagnoses), that data is transmitted to GitHub's servers. If you paste a synthetic or anonymized example, there is no PHI in scope. The practice of "paste your real API response into Copilot Chat to debug it" is a common way for PHI to be exposed accidentally in healthcare engineering teams. ### What about GitHub's "content exclusions" feature? GitHub Copilot's content exclusions feature lets admins specify files or paths that Copilot will not use as context. This is useful for keeping secrets and proprietary algorithms out of AI context, but it operates at the file path level — it cannot detect and exclude PHI within files. A file containing synthetic test data is fine even without exclusion; a log file containing real patient data should be excluded, but the exclusion needs to be configured before the developer opens the file in a Copilot-enabled IDE. ### Should we use an on-device coding assistant instead? For teams with strict PHI containment requirements and a technical staff capable of deploying local models, on-device AI coding assistants (using Ollama, LM Studio, or similar) eliminate the data-transit risk entirely. The trade-off is that local models are generally less capable than hosted models for complex code generation, and require infrastructure investment. Most healthcare engineering teams use a tiered approach: local models for sensitive contexts, GitHub Copilot for generic code. ## A checklist for healthcare engineering teams - Confirm in writing whether any agreement you hold covers GitHub Copilot for PHI. Do not rely on Microsoft's BAA: GitHub is not on its in-scope lists. - Switch all developers to Copilot Business or Enterprise; revoke individual seats. - Enable organization-level training exclusion in the admin console. - Write a Copilot-specific addendum to your acceptable-use policy. - Build synthetic test data generation into your CI/CD pipeline to reduce reliance on production data. - Configure content exclusions for paths known to contain sensitive data. - Deploy a local-first redaction tool for developer workstations that flags PHI before submission. - Add "pasted PHI into AI coding assistant" to your incident-response runbook. - Conduct an annual review of Copilot's HIPAA documentation as Microsoft/GitHub's policies evolve. ## The bottom line GitHub Copilot is a powerful tool for healthcare software developers, but it is not HIPAA compliant out of the box on any currently available tier. The path to an acceptable risk posture runs through organizational configuration (Business or Enterprise seats, not individual ones), developer training, and — most importantly — a culture where synthetic data replaces real PHI in development workflows. The developers most at risk are not the ones who know about HIPAA; they are the ones debugging a production issue at 11pm who paste a log line without thinking. Technical controls that intercept PHI before it leaves the workstation are the backstop that makes the policy durable. For the broader HIPAA picture across consumer AI tools, see [Is ChatGPT HIPAA Compliant?](https://sonomos.ai/blog/is-chatgpt-hipaa-compliant-2026/). For teams evaluating Cursor as an alternative AI coding environment, see [Is Cursor AI Safe for Sensitive Code?](https://sonomos.ai/blog/is-cursor-ai-safe-sensitive-code-2026/). ## Sources and primary references Reviewed October 1, 2026. Regulations are cited to the eCFR. Vendor statements are cited to the vendor's own documentation as it read on that date; vendors revise these pages, so confirm before relying on them. We could not retrieve GitHub's own terms or data protection agreement during this review, so statements about GitHub rest on the absence of GitHub from Microsoft's in-scope lists and should be confirmed with GitHub. - [45 CFR 160.103, definition of business associate](https://www.ecfr.gov/current/title-45/section-160.103) — who counts as a business associate, including subcontractors. - [45 CFR 164.502(e), disclosures to business associates](https://www.ecfr.gov/current/title-45/section-164.502) — satisfactory assurance, documented in a written contract. - [45 CFR 164.504(e), business associate contracts](https://www.ecfr.gov/current/title-45/section-164.504) — what the contract must contain. - [45 CFR 164.402 to 164.410, breach notification](https://www.ecfr.gov/current/title-45/section-164.402) — the presumption of breach, the four-factor assessment, and notification deadlines. - [45 CFR 160.402(c), agency liability](https://www.ecfr.gov/current/title-45/section-160.402) — liability for workforce members and business associates acting within the scope of agency. - [Microsoft, HIPAA and HITECH offering](https://learn.microsoft.com/en-us/compliance/regulatory/offering-hipaa-hitech) — the in-scope service lists, which do not include GitHub. - [Microsoft, Azure HIPAA offering](https://learn.microsoft.com/en-us/azure/compliance/offerings/offering-hipaa-us) — Azure-level HIPAA guidance. - [AWS, HIPAA Eligible Services Reference](https://aws.amazon.com/compliance/hipaa-eligible-services-reference/) — Kiro listed as eligible excluding Kiro Web; Q Developer and CodeWhisperer not listed; AWS BAA required first. ## Related HIPAA guides - [Is ChatGPT HIPAA Compliant?](https://sonomos.ai/blog/is-chatgpt-hipaa-compliant-2026/) - [Is Claude HIPAA Compliant?](https://sonomos.ai/blog/is-claude-hipaa-compliant-2026/) - [Is Gemini HIPAA Compliant?](https://sonomos.ai/blog/is-gemini-hipaa-compliant-2026/) - [Is Microsoft Copilot HIPAA Compliant?](https://sonomos.ai/blog/is-microsoft-copilot-hipaa-compliant-2026/) - [Is Perplexity AI HIPAA Compliant?](https://sonomos.ai/blog/is-perplexity-ai-hipaa-compliant-2026/) - [HIPAA-Compliant AI: A Complete Checklist for 2026](https://sonomos.ai/blog/hipaa-compliant-ai-checklist-2026/) Sonomos publishes this blog and makes Locke, which detects and masks sensitive information on your device before it reaches an AI model. [How Locke works](https://sonomos.ai/locke/) This article is general information about privacy and AI, not legal advice, and reading it does not create a solicitor–client or attorney–client relationship. Regulatory requirements turn on your specific facts and jurisdiction and change over time. Consult qualified counsel before relying on anything here, and check the publication and last-reviewed dates above. We may revise posts, but we do not undertake to keep any post current as the law changes. ## Reference pages for this post - [Locke for GitHub CopilotTool guide](https://sonomos.ai/for/github-copilot/) - [HIPAAGlossary](https://sonomos.ai/glossary/hipaa/) - [Locke for healthcareWho it's for](https://sonomos.ai/who-its-for/healthcare/) - [Locke for engineering teamsWho it's for](https://sonomos.ai/who-its-for/technology/) ## Related Articles September 1, 2026•Sonomos Research ### The Anthropic DPA Explained: Claude Data Processing Agreement Guide (2026) Anthropic offers a DPA on Claude Team, Enterprise, and the API — not on Claude.ai Free or Pro. Here is what the Anthropic DPA covers, how it handles EU-US transfers via SCCs and the DPF, what to verify before signing, and where a DPA stops. Claude DPA GDPR +2 September 1, 2026•Sonomos Research ### Claude EU Data Residency in 2026: What Anthropic Offers, and What European Teams Do Instead Anthropic does not currently offer EU data residency for Claude — every prompt is processed on US infrastructure and constitutes an EEA-to-US transfer. Here is how that compares to OpenAI, Microsoft, and Google, what the EU-US Data Privacy Framework does and does not cover, and the supplementary-measure stack European teams deploy instead. Claude Data Residency Europe +2 September 1, 2026•Sonomos Research ### Can My Employer See My Claude Chats? What's Visible in 2026 (and What Isn't) Whether your employer can see your Claude chats depends on the account (personal Claude.ai vs. work-managed Team/Enterprise), the device, and the network. Here is what is visible in each scenario — including Claude Code — and what deleting a chat actually does. Claude Workplace Privacy AI Privacy +1