Share via

Visual Studio AI Copilot for GCC

Brett R 0 Reputation points
2025-09-18T18:02:21.3733333+00:00

Are there any plans to allow direct Copilot connections for GCC Cloud? We are NOT creating accounts for Github, absolutely horrible integration, violates rules even under Github Gov.

As a developer and Visual Studio user, I’d like to express my concern about the requirement to use a GitHub account to access GitHub Copilot within Visual Studio. While I understand that Copilot originated within GitHub’s ecosystem, this dependency creates unnecessary friction for organizations and developers who do not use GitHub as their primary platform.

Many teams rely on Azure DevOps, internal Git servers, or other version control systems. Requiring GitHub for authentication and subscription management excludes these users from fully benefiting from Copilot’s capabilities in Visual Studio—a Microsoft product.

I strongly urge Microsoft to consider offering a GitHub-independent pathway for Copilot access in Visual Studio, ideally through Azure Active Directory or Microsoft account integration. This would:

Align Copilot with enterprise identity and access management policies

Enable broader adoption across regulated industries and closed environments

Reduce barriers for organizations already invested in Microsoft’s ecosystem

Developer technologies | Visual Studio | Extensions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Susmitha T (INFOSYS LIMITED) 910 Reputation points Microsoft External Staff
    2025-09-19T09:13:30.2466667+00:00

    Thanks for reaching out.

     
    Currently, GitHub Copilot does require a GitHub account for access within Visual Studio. This integration decision can understandably inconvenience users operating under strict compliance environments like GCC. Here are some options you might consider while waiting for Microsoft to possibly address this in the future:

    1. Stay updated on Visual Studio releases: Regularly check for news on features or enhancements that Microsoft might bring to Visual Studio, especially related to GitHub Copilot and alternatives.
    2. Feedback through official channels: You can continue to provide feedback through UserVoice or the Visual Studio Developer Community, where product teams often look for customer input for future releases. Link: Suggest a feature - Visual Studio (Windows) | Microsoft Learn Developer Community
    3. Explore alternatives: If GitHub serves as a roadblock, you may also want to explore different tools or extensions that can provide similar code assistance features without external account requirements.

    Since you're emphasizing a need for a GitHub-independent pathway, you could explore whether there's a way to facilitate access through Azure Active Directory (AAD) or Microsoft accounts. Microsoft often reviews customer feedback for future enhancements.

     

    Let me know if you need any further help with this. We'll be happy to assist.

    If you find this helpful, please mark this as answered.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.