What's Changing

Starting February 27, 2026 at 00:00 UTC, GitHub Copilot coding agent will transition from connecting to a single endpoint (api.githubcopilot.com) to subscription-based network routing that directs traffic to different hosts depending on the initiating user's Copilot plan:

• Copilot Business: api.business.githubcopilot.com
• Copilot Enterprise: api.enterprise.githubcopilot.com
• Copilot Pro and Pro+: api.individual.githubcopilot.com

This change affects teams who have configured the Copilot coding agent to run on self-hosted runners or larger runners with Azure private networking. If your organization falls into this category and has run at least one agent session in the past 60 days, GitHub has already sent you an email notification with a list of potentially-affected repositories.

Action Items Required

You must update your network configurations by the February 27 deadline to maintain continuity:

1. Identify affected repositories by checking the runs-on value in .github/workflows/copilot-setup-steps.yml files in your repositories. If this file doesn't exist, that repository is not affected.

2. Update firewall/network rules to allow connections to the new subscription-based endpoints listed above. You may need to allow multiple hosts if your organization has users on different Copilot plans.

3. Test connectivity before the February 27 deadline to ensure the Copilot agent runtime can communicate with GitHub systems.

Important Deadline

If network configuration updates are not completed by February 27, 2026, Copilot coding agent tasks will fail because the agent runtime will be unable to reach the new endpoints.