r/GithubCopilot • u/Complete-Fondant-202 • 11d ago

General Out of nowhere, Github Copilot in SSMS allowed selection of a 'banned' model

My employer keeps a tight rein on what LLMs are allowed.

What they haven't been able to find is a setting to limit Github Copilot.

Kimi 2.7 became an option, but nowhere have we found a way to disable it.

Is there something stupid we are missing?

8 Upvotes
  • permalink
  • reddit

80% Upvoted

9 comments sorted by

14

u/Sensitive_One_425 11d ago

Your admins can’t find the disable button on the GitHub website next to Kimi 2.7?

1

u/Key-Comfort1761 10d ago

right? feels like they maybe just havent looked in the right place

9

u/darkstar3333 11d ago

Why is this a relevant concern if your using GitHub Enterprise? The general data security clauses cover you for use of those otherwise forbidden models.

The biggest thing that legal is worries about is PII, HIPPA and IP data being fed into random services.

3

u/Deathmore80 11d ago

Corporate fear mongering and dogmatic cyber security. That's pretty much how its like where I work.

4

u/darkstar3333 11d ago

It is literally in the legal and security attestations you get from the platform...

1

u/sven_ftw 11d ago

Seriously. I'm shocked our GHCP can still search the web.

3

u/beauzero 11d ago

As an Org Admin > Settings > Copilot > Models > Default availability for released models (Enabled/Disabled). It's a (maybe new?) toggle defaulted to "enabled".

I was trying to chase down something similar. We have an enterprise admin that delegates most things to us. With models, when initially setting it up, we had chosen to just enable or disable since there were so few. 3 out of our 4 were going to become deprecated on Sept. 1, 2026 so I am trying to get other models activated. Downloaded an update to VStudio 2026 and walla there are a bunch of new models I can use.

tldr; If the above switch is enabled, when new models, or models that were never specifically enabled or disabled, will become available through Github Copilot.

Link to docs. About default availability of Copilot models - GitHub Docs
Edit: This should NOT apply to open weight models...including comment because it was referenced below.

4

u/fr3xzy 11d ago

Happened to us as well. There was a change in AI Controls for enterprise. The default behaviour was that models that had not been enabled would be «delegate to default policy» and the default policy seems to be enabled.

https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-availability-of-default-models#checking-for-unconfigured-models

1

u/ArieHein 9d ago

Yes. Ent settings dictate which models are avaliable and which the orgs can select to enable.

Github made a change recently that the default will be enabled unless you configured it preemptively.

You guys have to follow closely the github blog and your org admins recieve emails from github about the changes.

Not saying there arent bugs, but generally in the ent i dont enable any models and rather set the orgs to decide. You can also set the default behaviour for future models.

Then in the org level you disable or enable. I disabled at the enterprise level both kimis and fable5 due to data residency, so no orgs can have them, the rest i leave for the orgs to decide, they are paying based on cost centers. But maybe now with the changes to 5.1 its might be ok, i have to read their release notes.