Back to rankings

GitHub Copilot App: Bring Your Own Key (BYOK) Support

GitHub Copilot

The GitHub Copilot app now supports Bring Your Own Key (BYOK), letting users connect their own model provider API keys, OpenAI, Anthropic, Azure OpenAI, Microsoft Foundry, LM Studio, Ollama, or any OpenAI-compatible endpoint, with keys stored in the local OS keychain.

Sources & Mentions

5 external resources covering this update

GitHub Community — Enterprise-Grade BYOK for Copilot Discussion

GitHub

Medium — GitHub Copilot Is Getting Its Own App!

Medium

DevOps.com — GitHub Copilot Gets Its Own App, and Agents Are the Reason Why

DevOps.com

GitHub — copilot-sdk/docs/auth/byok.md

GitHub

Havoptic — GitHub Copilot CLI Changelog & Release Notes

Havoptic

GitHub Copilot App: Bring Your Own Key (BYOK) Support

GitHub has added Bring Your Own Key (BYOK) support to the GitHub Copilot app, allowing users to connect their own model provider API keys for agent sessions.

What's new

  • Bring your own model provider. Supported providers include OpenAI, Azure OpenAI, Microsoft Foundry, Anthropic, LM Studio, Ollama, and any OpenAI-compatible endpoint.
  • Local, secure key storage. API keys are stored in the local OS keychain and are never accessed by the application UI.
  • Policy gating. Organizations on Copilot Business or Enterprise must have Copilot CLI enabled in policy settings to access the Copilot app.

Why it matters

BYOK lets developers and teams use the Copilot app as a front end while routing to the model and provider of their choice, including local models via Ollama or LM Studio, without sending keys through GitHub's UI.

Mentioned onGitHubMediumDevOps.comGitHubHavoptic