Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The terms explicitly exclude two user categories from their scope: users who purchase through a Microsoft agreement, and users on the GitHub Copilot Individual plan. Each excluded group is directed to a different governing document.
This analysis describes what GitHub's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that the applicable governing terms for GitHub Copilot depend on the procurement channel and plan type, creating three parallel governance tracks. Organizations should confirm their procurement channel to identify which document governs their use.
Under these terms, only Copilot Business and Enterprise customers purchasing directly from GitHub are governed by this document. Microsoft-channel purchasers are subject to Microsoft Product Terms, and Individual plan users are subject to the GitHub Terms of Service and associated documents.
Cross-platform context
See how other platforms handle Exclusion of Microsoft-Channel and Individual Plan Purchasers and similar clauses.
Compare across platforms →Monitoring
GitHub has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"If you purchase GitHub under a Microsoft agreement, these terms do not apply to you and your use of GitHub Copilot is instead governed by your Microsoft Product Terms, including the Microsoft Product Terms for GitHub Offerings. If you purchase GitHub Copilot Individual, these terms do not apply to you and your use of GitHub Copilot is instead governed by the GitHub Terms of Service, including the GitHub Privacy Statement and the GitHub Terms for Additional Products and Features.Excerpt from GitHub's Copilot Product Terms
(1) REGULATORY LANDSCAPE: The scoping mechanism itself does not directly engage a regulatory framework, but the governing documents applicable to Microsoft-channel purchasers and Individual plan users may contain materially different data protection, liability, and acceptable use provisions. Organizations subject to GDPR or CCPA should identify which governing document applies to their specific procurement context and evaluate data protection compliance under that document. (2) GOVERNANCE EXPOSURE: Low. The exclusion provision is operationally clear and reduces ambiguity about applicable terms. However, organizations that have changed procurement channels or plan types since entering the agreement should confirm which document currently governs their use. (3) JURISDICTION FLAGS: No jurisdiction-specific heightened exposure arises from this provision directly. However, EU/EEA organizations using Copilot through a Microsoft enterprise agreement should ensure that Microsoft's applicable data protection terms satisfy GDPR processor requirements under their specific agreement. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams managing multiple GitHub Copilot deployments across different plan types or purchase channels should maintain records of which governing document applies to each deployment. Mixing direct-purchase and Microsoft-channel agreements within the same organization may result in different applicable terms for different user groups. (5) COMPLIANCE CONSIDERATIONS: Organizations should verify their current purchase channel and plan type and confirm which governing document applies. Where organizations have transitioned between purchase channels, a review of the applicable terms before and after transition may be warranted to identify any gaps in data protection or acceptable use coverage.
Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes that the applicable governing terms for GitHub Copilot depend on the procurement channel and plan type, creating three parallel governance tracks. Organizations should confirm their procurement channel to identify which document governs their use.
Under these terms, only Copilot Business and Enterprise customers purchasing directly from GitHub are governed by this document. Microsoft-channel purchasers are subject to Microsoft Product Terms, and Individual plan users are subject to the GitHub Terms of Service and associated documents.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by GitHub.