can confirm same issue. any updates on this?

Just chiming in to note that this used to work fine in the past, only ran into the issue after having to reinstall VSCode

Login with your enterprise GitHub account and try again. And also check your GitHub configurations.

Just wanted to note that if you can't see the gear and account icons, go to View -> Appearance -> Activity Bar. It took me far too long to figure this out. Why is this menu not on the Copilor status indicator on the status bar? The only option there is disable / enable the extension. The UX of signing out of an account with expired Copilot and into another account with active Copilot is terrible at the moment with multiple VSCode restarts and in-browser re-authorizations .

Same problema here, I tried using the vscode profiles option, but it also doesn't allow multiple copilot accounts...

I have the same problem, have a personal account that I use for literally everything and an Enterprise account thats sole existence is to have the copilot licence. This issue makes using copilot basically impossible unless I want the hassle of having to log into each account every time I restart vscode :(

Like someone else said, the only solution appears to be using one github account and one microsoft account.

This sounds like a prime example for a “multi account/per extension account” extension for the vs code marketplace.

This problem is still ongoing

It's probably time to try alternatives such as Codeium.

April 2024, still not fixed!

Goodness, why can't such a basic function be supported? The user experience is so terrible.

Ok, I just cancelled my copilot subscription, not being able to use other extensions due to this limit makes it not worth it.

I'd gladly subscribe again when this feature become available

Still not fixed, wake up Github!

Still not fixed.
I tried to set up multiple profiles, but that didn't work because if you log out of one account on one profile, it will be logged out for all profiles.

Is this acceptable for paying customers? @ashtom

The problem is still not fixed. Any update on this? it's frustrating to keep switching profiles, logging out and logging in hoping that copilot will work this time. Please fix this as soon as possible. Thanks!

This still does not work, I have a paid subscription to Copilot that I can't get to work in VSCode, after numerous attempts and different approaches. It works with Visual Studio however. There is some weird interaction with Github desktop which seems to not completely log out of the account used for commits, and will not let me login as the account with the Copilot subscription.
Why is there not a simple "Sign in" on the VSCode Copilot, there is a "Sign up" when it warns there is no access.
The ability to login is pretty basic and this issue has been going on for months on a paid service.

I did not investigate if any of this is actually possible as a plugin, but since this problem has been going on for over year without a solution in sight, i have been thinking on formally defining the problem and how a solution for it would need to look like.

Please note this is my personal take on what the cause of the problem is, it may not reflect what others are experiencing.

Feel free to discuss and add to this, please stay nice. It's just a wild idea.
I think it's far more fun than constantly reading seeing new reactions like: 'i have this problem too', 'i need this problem solved', 'it's still not solved', and in the end, it might spark some ideas and who knows what we will have in another year's time?
Those are needed to keep the thread alive, but in the end, i think that defining a soltion as clearly and as complete as possible can turn out to be more productive and can lead to a formal feature request that is well thought out and covers most if not all the needs of all people involved. Having been discussed here possibly also resolves the issue that for a feature request to be considered by Microsoft it has to be supported by a significant amount of people within a fairly limited timeframe.

Note:
I use account and user account interchangeably. They mean the same thing whicever way i name it.

Example:
Plugin 1: GitHub Repositories
Plugin 2: GitHub Copilot

Premise:
You have 2 different GitHub accounts: 'Account A' and 'Account B'
On 'Account A' you have a subscription for GitHub Copilot.
On 'Account B' with different features enabled. This account is required for commiting code to github.

Problem:
Visual Studio Code 1.88.1 and earlier can only use a single account for all plugins.
There is not enough control over user account usage.

Solution:
A plugin that takes control of user account handling functions that can be configured to use a specific account per plugin.

Requirements:

• Retrieve a list of all user accounts in VS Code ( * )

• Retrieve a list of all installed plugins ( * )
  ( * ) This needed is for initial setup only.
  For each installed plugin it's needed to determine if it requires user account interactions or not.
  If it does, pre-populate a plugin and user account association entry in a list in the configuration.

• A VS Code event handler for a new plugin that has been installed.

  • The handler needs to be able to determine if the newly installed plugin requires user account interactions.
  • If user account interaction is required:
    • Prompt for a user account to be used with this plugin, or allow to create a new account.
    • Generate a new plugin and account association entry in the list in the configuration.

• A VS Code event handler a plugin that has been uninstalled.

  • Remove plugin and account association from the list if it exists. (Configurable?)

• A VS Code event handler that is triggered by a plugin requesting authorization (i.e. account is logged in).

  • Provide the user account from the plugin and user account association configuration if it exists.
  • Prompt for a user account to be used for the plugin, and/or allow for new account creation.
    In the event the association didn't exist before allow it to be stored.

• A Configuration Manager with the following functions:

  • Select a default account to be used for new plugins.

  • Create a new user account.

  • Read existing user accounts. (list).

  • Update existing user account.

  • Delete existing user account.

  • Create a new plugin and account association.
    Selectable from dropdown lists or listboxes. Only list those plugins that require user accounts.

  • Read existing plugin and account associations.

  • Update plugin and account associations including the option to create a new account for the plugin.

  • Delete plugin and account association.

  • Selection:
    1). Use default account for newly installed plugins.
    2). Prompt for using an existing account or creating a new one for newly installed plugins.
    3). Both 1 + 2, with an accept button to accept the default.
    4). Require to always provide login credentials.