How to Migrate After the GitHub Copilot Billing Preview App Retirement
AI Usage, budgets, cost centers, usage pools, downloadable reports, and the Billing API replace the retired preview, but reporting continuity needs a controlled handoff.
Key takeaways
GitHub confirmed on August 4, 2026 that the Copilot Billing Preview app has been retired and is no longer available. Copilot spend now belongs in GitHub billing settings, including the AI Usage page, budgets, user-level budgets, cost centers, usage-pool allocation, downloadable reports, and the Billing API. Migration is more than replacing a bookmark. Export a final baseline from the old reporting process, map fields, time zone, currency, owners, thresholds, and notifications to the new controls, then run both reporting paths for one complete billing cycle where possible. Reconcile totals, users, cost centers, pools, exports, and alerts before archiving the old workflow. Document API authentication, pagination, rate limits, retries, and failure ownership without exposing credentials.
# How to Migrate After the GitHub Copilot Billing Preview App Retirement
August 14, 2026
Direct answer
Move spend monitoring to AI Usage, budgets, and usage reports. Preserve a baseline and reconcile one full billing cycle before retiring old dashboards, alerts, or exports.
Fact sources
GitHub announced on August 4, 2026 that the Copilot Billing Preview app was retired and unavailable.
Current billing settings provide AI Usage, user budgets, cost centers, and usage-pool allocation.
Raw usage remains available through downloadable reports and the Billing API for custom reconciliation.
Six steps for leaving Billing Preview
- Export a final full-cycle baseline for totals, users, organizations, cost centers, and thresholds.
- Validate AI Usage filters, grouping, export fields, time zone, currency, and AI Credits definitions.
- Rebuild enterprise, organization, and user budgets with limits, alerts, recipients, and escalation.
- Reconcile cost-center and usage-pool assignments for missing or duplicate ownership.
- Move automated reporting to usage reports or the Billing API, documenting authentication, pagination, rate limits, retries, and failures.
- Compare one full cycle, then archive old dashboards, alerts, and ownership only after totals and notifications match.
Why it matters
Retirement changes more than navigation. Fields, aggregation, time zones, alert behavior, and ownership can change. Parallel reconciliation reveals missing budgets, incorrect cost attribution, or broken exports before they create a monitoring gap.
Impact for ordinary AI users
Individuals can inspect and export AI usage from billing settings, while organizations receive finer budget and allocation controls. The real migration cost is report rebuilding, permissions, API work, alert testing, and historical reconciliation.
Related tools and tutorials
Start with one reversible task, verify version, permissions, cost, and logs, then record the result in the team runbook.
AI software and tools · AI account and cost services · AI skill tutorials · AI frontier news
FAQ
Can the Billing Preview app still be used?
No. GitHub says it has been retired and is no longer available.
Does AI Usage automatically replace every old report?
Do not assume so. Compare fields, filters, dates, budgets, cost centers, pools, and exports.
When can the old monitoring process be closed?
After at least one full billing-cycle reconciliation confirms totals, categories, alerts, exports, and ownership.
Source links
- GitHub Changelog: Retiring the Copilot Billing Preview app (2026-08-04)
- GitHub Docs: Budgets and alerts
- GitHub Docs: Billing reports
- GitHub Docs: Copilot billing
What this means for everyday users
Record baseline, billing cycle, time zone, currency, AI Credits fields, budgets, thresholds, cost centers, pools, exports, API, alerts, owner, and archive date.
Related reading
GitHub adds enterprise controls for Copilot agent commands, files, and network access
GitHub released enterprise-managed permissions for Copilot agent operations on September 9. Administrators can centrally set shell commands, file reads and writes, and access to network domains to blocked, approval required, or allowed without a prompt. User preferences, workspace settings, automatic approval, and earlier approvals cannot make the enterprise policy less restrictive. GitHub says the controls are generally available in the Copilot app, Copilot CLI, and Visual Studio Code sessions that use Agent Host for Copilot Business and Enterprise customers. Security and platform teams should begin with a minimum-permission baseline, test representative repositories, and expand only the operations that have a clear owner, audit trail, and rollback path.
GitHub Copilot Customize Tab Is Generally Available for Team Agent Workflows
GitHub Copilot Customize Tab Is Generally Available for Team Agent Workflows. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: configuring team agent behavior in Copilot and validating results with a small task. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
How to Build an AI Agent Evaluation Baseline: From Offline Tests to Production Review
How to Build an AI Agent Evaluation Baseline: From Offline Tests to Production Review. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: establishing a repeatable baseline for AI-agent quality, risk, cost, and human review. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
How to Choose AI Agent Tool Permissions: An AgentCore Dogwood Acceptance Guide
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for How to Choose AI Agent Tool Permissions: An AgentCore Dogwood Acceptance Guide.
GitHub Copilot Enters Slack Public Preview for Shared Coding Work
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for GitHub Copilot Enters Slack Public Preview for Shared Coding Work.
GitHub Copilot Brings Shared Agentic Work to Microsoft Teams
Review the official scope, availability, ordinary-user task, permissions, cost, review, and rollback checks for GitHub Copilot Brings Shared Agentic Work to Microsoft Teams.
Summary
The Billing Preview retirement is a cost-governance migration, not a bookmark change. Baselines, parallel reconciliation, budget tests, and API failure drills protect AI Credits monitoring continuity.
