❤️Answer:
Yes, developers will still be able to use GitHub Copilot features (including Copilot Chat in pull requests) on repositories from Org 1, even if:

• Copilot Enterprise is active on Org 2 (which has no repos), and
• Copilot is disabled on Org 1,
• As long as:
  -The developers are licensed under Copilot Enterprise in Org 2, and
  -They have access (permissions) to the repositories in Org 1.

🧠 Explanation:
-GitHub Copilot Enterprise licenses are user-based, not repo/org-based.
-Features like Copilot Chat in PRs work wherever the licensed user has access — even across different organizations or repositories.
-So as long as your developers:
-Are assigned licenses in Org 2, and
-Are collaborators/members with access to the repositories in Org 1,
— they can continue using Copilot Chat, inline suggestions, and other features across both orgs.

If you switch your Copilot subscription to the second organization (Org 2) and turn it off in the first one (Org 1), your developers can still use Copilot’s help in their coding tools. But to see Copilot’s suggestions and chat inside pull requests, they need to have permission to access the code. If Org 1’s code is private and Copilot is turned off there, Copilot might not work on those pull requests. So, to keep everything working well, you either keep Copilot on in Org 1 or move the code to Org 2 where Copilot is active.