GitHub Copilot Changes Model Access Rules for Multi-Organization Users
GitHub CopilotGitHub Copilot changed how model access works for developers who hold Copilot seats in more than one organization, tying their available models to whichever organization pays for their seat rather than the union of every organization's enabled models. Developers can check which organization is billing their seat via the Usage billed to field in their Copilot features settings. The change only affects people with seats spread across multiple organizations; anyone whose Copilot access comes solely through an enterprise or its affiliated organizations is unaffected.
Key Takeaways
- GitHub Copilot now determines model access by billing organization for developers holding seats in more than one organization, replacing the previous rule that combined every org's enabled models.
- Developers losing access to previously available models is a real risk if the organization now paying their seat has a narrower model policy than one they relied on before.
- The "Usage billed to" field in Copilot features settings tells a developer exactly which organization's policy now governs their model access.
- The change is narrowly scoped, and does not affect anyone whose Copilot access comes from a single enterprise or its affiliated organizations.
- This tightens GitHub's approach to per-organization model policy, closing a loophole where multi-org membership effectively bypassed individual org model restrictions.
- The update ships alongside a broader wave of Copilot billing changes in late August and September 2026, including reopened Business and Enterprise sign-ups and new upfront per-seat payment requirements.
Model Access Now Follows the Billing Organization
GitHub Copilot changed how it decides which AI models a developer can use when that developer holds a Copilot seat in more than one organization. Previously, a developer in this situation could access any model enabled by any of their organizations, effectively getting the union of every org's model policy. Under the new rules, model access is determined solely by whichever organization is actually paying for that developer's Copilot seat, referred to as the billing organization.
Why It Matters for Multi-Org Developers
This is a meaningful behavior change for anyone contracting, consulting, or contributing across several GitHub organizations with Copilot seats. A developer who previously had access to, say, Claude models enabled in one org and Gemini models enabled in a different org will now only see the models the specific organization footing the bill for their seat has chosen to enable. If that billing organization has a narrower model policy than the developer previously relied on, models they were using before could simply disappear from their picker.
How to Check Which Organization Is Billing a Seat
GitHub Copilot pointed developers to a straightforward way to check their status: the "Usage billed to" field inside Copilot features settings shows exactly which organization is covering the cost of a given seat, and therefore which organization's model policy now governs access.
What Isn't Changing
The update is scoped narrowly. Developers whose Copilot access comes entirely through a single enterprise or that enterprise's affiliated organizations see no change in behavior, since there is no ambiguity about which policy applies. GitHub Copilot directed readers with more complex licensing setups to its Copilot policy documentation for further detail on how policies resolve across multiple organizations and enterprises.