Migration of GitHub Team plan organizations to the enhanced billing platform

Starting today, existing GitHub Team plan organizations will begin to gain access to the enhanced billing platform: a suite of new features designed to help administrators understand and manage GitHub spend for their organizations.

Benefits of the new platform include:

  • Spend transparency – view usage for organizations, repositories, products, and SKUs by hour, day, month, or year
  • Improved control – set budgets to limit spending and configure alerts to stay informed of budget utilization

Enhanced billing platform screenshot

What to expect

All existing Team plan organizations will gain access to the enhanced billing platform by the end of March 2025. Organization owners have been informed via email, and an in-app banner will appear on the billing page in advance of the transition.

Here are some things to know about the transition:

  • Once transitioned, a new Billing & Licensing section will appear in the settings menu.
  • Spending limits will be migrated and renamed as budgets in the new billing platform. For more details about budgets, visit Preventing overspending
  • While the new billing platform will not visually display historical usage, you will be able to download a usage report to get your pre-transition historical usage.

Other important changes

Learn more

For more information, visit Using the new billing platform or join the GitHub Community discussion.

Summary

Beginning February 2025, the beta Copilot /usage endpoints will be deprecated.
No new data will be inserted for retrieval via the beta /usage endpoints. This endpoint will be accessible through February, but the 28 day retention policy will remain.

Who’s impacted?

Enterprise organizations with Copilot licenses not yet migrated from the /usage metrics APIs are impacted by this deprecation.

What’s changing and why?

The deprecation of the beta /usage endpoints is a part of GitHub’s effort to deliver more powerful and flexible data offerings for enterprises, organizations, and teams. The new endpoints provide:

  • Visibility into the adoption and consumption of Copilot across various stages of dev lifecycle (from code suggestions to PR reviews), from the team to the enterprise level
  • Expanded scope of metrics, with the addition of GitHub.com Copilot Chat and Copilot for Pull Requests
  • Consistent terminology with the user management API
  • Better visibility into unique users at various drilldowns

Next steps

Ensure your organization is no longer consuming the now deprecated /usage endpoints in any jobs, workflows, and analytics tools.
As an alternative to the beta Copilot /usage endpoints, check out the PowerBI template and the Copilot /metrics endpoints.

Join the discussion in the GitHub community.

See more

Starting today, customers can change the runner image on larger hosted runners without deleting and re-creating them. You can now update the image and the change will be applied on all future workflow runs to that label. For customers using static IPs, you can change the image on your runner while keeping your IP addresses the same.

Note: partner images cannot be edited at this time and still require the runner to be deleted and re-created.

To edit your runners, follow the steps outlined in our documentation.

See more