[Urgent] Existing Azure-billed Copilot Business entitlement disappeared after organization left an enterprise #203267
Replies: 2 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
Hi @Jungwon423 , This community is managed by GitHub employees, but it is not a support forum. You have done everything necessary on your end by opening a ticket on our Support page. This is a public forum, and the community is unable to assist with nor escalate your ticket, but we can assure you it is in the right place. There are an extremely high volume of Support tickets right now, yours will be answered in the order it was received based on the amount of tickets ahead of yours. Please open only one ticket per request. As no other Community Discussions team members will be able to provide additional help with account related questions I am going to close this discussion. We appreciate your understanding and patience while Support works through your request! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Copilot in GitHub
Body
Summary
Our organization previously had an active GitHub Copilot Business subscription with two assigned seats, billed through an Azure subscription.
We temporarily connected the organization to a GitHub Enterprise account. Copilot enablement at the enterprise level failed with a “temporarily unavailable” error. The “Re-enable Copilot” and “Allow this organization to assign seats” actions also failed.
We then removed the organization from the enterprise, expecting its previous standalone Copilot Business state to be restored. However, the existing entitlement and seat-management access were not restored.
Current behavior
The Azure billing connection remains active.
The GitHub API still reports
plan_type: business.The API reports two existing seats.
seat_management_settingis reported asdisabled.Both seats are marked as pending cancellation on July 31, 2026.
The two affected users now show Copilot Free.
The organization’s Copilot settings have disappeared from the UI.
Attempting to assign the existing seats through the API returns:
422: Copilot Business is not enabled for this organization.Expected behavior
Because this was an existing Azure-billed Copilot Business subscription—not a new purchase—removing the organization from the enterprise should restore its previous standalone entitlement and both assigned seats.
Impact
Both developers have lost access to Copilot, and our active development work is blocked. The pending cancellation date makes this extremely time-sensitive.
Request
Could a GitHub staff member please help route this to the Copilot Billing/Entitlements engineering team?
We need the existing Azure-billed Copilot Business entitlement and both seats restored. This should not be processed as a new-customer activation.
We already have GitHub Support cases and a Sales inquiry open. A GitHub staff member may contact us privately for the organization name, enterprise name, and support ticket numbers.
All reactions