We are migrating the download URLs for Copilot usage metrics reports from Azure Front Door domains to a stable, GitHub-owned custom domain. This change will improve URL stability and make firewall and proxy allowlist management easier for enterprise customers.

What’s changing

Starting May 20, 2026, Copilot usage metrics report download links—returned by the Copilot Usage Metrics API—will use the new domain copilot-reports.github.com instead of the current copilot-reports-*.b01.azurefd.net pattern.

github.com (GHEC) customers:

Current New
Report download URL pattern https://copilot-reports-*.b01.azurefd.net/... https://copilot-reports.github.com/...

ghe.com customers:

Current New
Report download URL pattern https://copilot-reports-*.b01.azurefd.net/... https://copilot-reports.*.ghe.com/...

What you need to do

If your organization uses a firewall or proxy allowlist, add the following domain before May 20, 2026:

  • github.com: https://copilot-reports.github.com
  • ghe.com: https://copilot-reports.*.ghe.com

The legacy copilot-reports-*.b01.azurefd.net pattern will continue to work during a transition period, but will eventually be deprecated. We recommend updating your allowlists as soon as possible.

Note: In rare cases where Azure Front Door is unavailable, report downloads may fall back to direct Azure Blob Storage URLs (*.blob.core.windows.net). If your organization requires uninterrupted access to reports during such events, you should also ensure *.blob.core.windows.net is in your allowlist.

Why we’re making this change

The previous Azure Front Door domains were infrastructure-specific and could change when services were redeployed or reconfigured. Moving to a stable, GitHub-owned domain ensures that:

  • Report download URLs remain constant regardless of infrastructure changes.
  • Enterprise security teams have a predictable, trustworthy domain to allowlist.
  • Automation scripts and integrations are not disrupted by domain changes.

For more information, see the Copilot allowlist reference.

Join the discussion within GitHub Community.