URGENT: Copilot disabled by GitHub System after org migration to Enterprise

[pennz1]

🏷️ Discussion Type

Bug

Body

Hi GitHub team,

We have an urgent production issue affecting 8 developers for 24+ hours. Support ticket submitted with no response.

Enterprise: yswlingyu
Organization: yswsf

Issue:
After migrating org "yswsf" into enterprise "yswlingyu", GitHub System automatically disabled Copilot seat management
TWICE (confirmed in Audit Log, actor: GitHub System).

Errors:

• "An error occurred while enabling Copilot for your enterprise account"
• "Copilot access has been disabled for the entire enterprise"

When i allow this in organization settings：

"There was an error when trying to allow this organization to assign seats"

Status:

• Azure subscription: active ✅
• Billing: $189/month running ✅
• Copilot: completely unusable ❌

The Audit Log clearly shows copilot.cfb_seat_management_changed triggered by GitHub System, not by any user action.

Can someone from GitHub escalate this to the support team? Or advise how to manually re-enable from the backend?

Thank you.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[queenofcorgis]

Hi @pennz1,

Thank you for your patience. The community is unable to assist with nor escalate your ticket, but we can assure you it is in the right place. It will be answered in the order it was received based on our team's resources and the amount of tickets ahead of yours. We appreciate your understanding!

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.

Thank you!

[JordyForNow]

@pennz1 has your issue been solved? we are running into the same issue with 40+ developers. How long did it take for github to respond?

[pennz1]

yes, our issue has been solved. It took about one month for GitHub to respond and help us resolve it.

[Capturedhumanity]

If willing, could you share the fix? Did you have to toggle some features in the Microsoft tenant?

[JordyForNow]

i imagine github/microsoft fixed it on their end...

[Capturedhumanity]

ahh ok. hopefully they get back soon!

[pennz1]

This is handled by GitHub in the background.