GitHub added team-level targeting to Copilot Enterprise model policies on 31 July.
Until now, model policy was an organisation-wide switch. One list for everyone, set to whatever the most cautious team could tolerate.
The problem with one list
A single policy forces a bad trade. Either the whole organisation gets access to a model that one regulated team should not use, or the whole organisation is held back to that team's constraints.
In practice organisations chose the second, which is why developers spent July reading about models they could not select.
What targeting enables
- A platform team can trial a newly added vendor without exposing it to teams under compliance review
- A team working on regulated data can be restricted to approved models while everyone else moves freely
- Deprecations can be staged team by team instead of as one organisation-wide cutover
Where this fits in a busy fortnight
GitHub shipped three admin-facing model changes in three days: default enablement on 29 July, the August deprecation list on 31 July, and this.
Together they describe model policy becoming a real administrative surface with its own lifecycle — additions, removals and scoping. If nobody at your organisation owns it, that is now a gap.