GitHub Copilot — Not Supported
GitHub Copilot routes all requests through Microsoft's backend using GitHub's own authentication protocol. There is no base URL setting to redirect those requests through a custom proxy; governance, attribution, and audit logging are not possible for Copilot sessions.
Why Copilot Can't Be Proxied
GitHub Copilot connects to api.githubcopilot.com using GitHub's proprietary authentication. The protocol is not OpenAI-compatible and does not expose an endpoint override. The AI provider (OpenAI, in Copilot's case) is abstracted away entirely; you cannot substitute a custom base URL the way you can with tools that connect directly to AI providers.
What You Lose
Without gateway integration, Copilot sessions have no:
- Spend tracking: Copilot usage is billed per seat with no per-team or per-project breakdown visible to your governance layer
- Policy enforcement: no model restrictions, rate limits, or allow/deny rules
- Audit logging: no record of which completions were requested or which repositories were analyzed
- Attribution: no workload or project tagging
Ask GitHub to Support Custom AI Endpoints
Submit feedback:
- GitHub Copilot Community Discussions
- Ask for: "Support a configurable AI endpoint URL so organizations can route Copilot traffic through their own governance gateway for audit logging, policy enforcement, and spend attribution"
Looking for a supported alternative? Claude Code in VS Code and Cline offer comparable AI coding capabilities and route cleanly through Axemere.