You can get Copilot answering inside VS Code without ever opening a GitHub account, but only if your license comes from somewhere other than a personal GitHub plan. The practical routes are a Microsoft 365 Copilot license tied to a work or school Entra ID, a Copilot Business or Enterprise seat assigned by an organization's admin, or the free tier that Microsoft has been rolling out to VS Code users. Sign in with the Microsoft or organizational account that holds the license, install the GitHub Copilot extension anyway (the name is legacy), and the chat panel lights up. The GitHub part is a delivery mechanism, not a requirement. What follows is the exact sequence, the settings that matter, and the failure cases that trip people up.
What "Without GitHub" Actually Means for Copilot in VS Code
The Copilot extension in VS Code is published under the GitHub Copilot name because GitHub built it and Microsoft owns GitHub. That branding confuses people into thinking a GitHub account is mandatory. It isn't for every license type. A Microsoft 365 Copilot license, assigned through a Microsoft 365 admin center, can authenticate the same extension through your organizational identity.
Three distinct identities exist in this stack, and mixing them up causes most setup failures. Your VS Code installation is local and anonymous. Your Microsoft account (personal, work, or school) controls the Copilot license. Your GitHub account, if you have one, controls GitHub-specific features like Copilot code review on pull requests. Only the middle one is required for in-editor chat.
The extension identifier is GitHub.copilot and the chat companion is GitHub.copilot-chat. Both appear in the Extensions view search as "GitHub Copilot" and "GitHub Copilot Chat." You install them regardless of which identity you'll sign in with. Think of the name as a brand inherited from the original launch, similar to how "Kleenex" describes a tissue.
Microsoft has steadily decoupled licensing from GitHub accounts since Copilot's general availability. The Microsoft 365 admin center now lists Copilot as a licensable service alongside Office apps, and organizations assign seats the same way they assign Exchange Online mailboxes. If your employer pays for Microsoft 365 Copilot, you almost certainly have a path in without touching github.com.
Before You Install: Accounts, Licenses, and Version Checks
Confirm three things before downloading anything. First, your VS Code version: the chat experience requires a reasonably current build, and Microsoft documents version requirements on the VS Code release notes page rather than in a fixed number that survives across quarters. Check Help > About on Windows or Code > About Visual Studio Code on macOS, and update through Help > Check for Updates if you're behind.
Second, your license source. Ask your IT admin whether you hold a Microsoft 365 Copilot license, a standalone Copilot Business or Enterprise seat, or neither. The admin center's Users > Active users page shows assigned licenses per person. If you're an individual with no organizational account, your options narrow to the free tier and consumer Microsoft 365 plans that include Copilot.
Third, your sign-in method. If your organization uses Entra ID (formerly Azure AD), your work email is the identity. If you're a solo user with a personal Microsoft account, that's the identity. Write down which one you'll use, because switching later requires signing out of both the Accounts menu and the Copilot chat panel separately.
Network access is the fourth check nobody mentions. Corporate firewalls that block api.githubcopilot.com or Microsoft's Copilot endpoints will let the extension install and then fail silently at the first chat request. Ask whether your proxy allowlists those domains before you spend an hour debugging a "sign-in succeeded but nothing happens" symptom.
Step-by-Step: Installing and Signing In Without a GitHub Account
Follow these in order. Each step names what you should see on screen so you can confirm success before moving on.
1: Open VS Code and press Ctrl+Shift+X (Cmd+Shift+X on macOS) to open the Extensions view. 2: Search GitHub Copilot. Install the extension whose publisher is GitHub. Then search GitHub Copilot Chat and install that too β chat ships separately and won't appear without it. 3: Reload the window when prompted (Command Palette > Developer: Reload Window). 4: Click the Copilot icon in the Activity Bar, or press Ctrl+Alt+I (Cmd+Ctrl+I on macOS) to open the Chat view. 5: Choose "Sign in with Microsoft" or "Sign in with GitHub" β pick Microsoft if your license is organizational. If only the GitHub option appears, your extension version is older; update it. 6: Complete the browser handoff. VS Code opens your default browser, you authenticate, and the browser shows a success page that says you can close the tab. 7: Return to VS Code. The Chat view should show a model picker and an empty prompt box rather than a sign-in button.
If step 7 shows a sign-in button again, the token didn't persist. Open the Command Palette and run "GitHub Copilot: Sign Out," then repeat steps 5 through 7. A stale token from a previous GitHub sign-in is the most common cause, and it survives extension reinstalls because credentials live in the OS keychain, not the extension folder.
If the browser handoff fails because your default browser is on a different machine or profile, copy the device code VS Code displays and paste it into the browser manually. The code expires after roughly fifteen minutes; start over if it lapses.
Configuring the Core Settings That Control Copilot's Behavior
Open Settings with Ctrl+, and search copilot. The settings you'll actually change live under Extensions > GitHub Copilot and Extensions > GitHub Copilot Chat. Defaults are conservative: inline suggestions are on, chat is on, but several useful behaviors are off until you enable them.
Turn on github.copilot.enable for the languages you care about. The setting is a per-language map, and by default it enables most common languages but disables Copilot for plaintext and some markup files. If you write a lot of YAML or Markdown, add those keys explicitly or you'll wonder why suggestions never appear.
Set github.copilot.editor.enableAutoCompletions to true if you want ghost-text suggestions as you type rather than only on demand through the Command Palette. Many teams disable this deliberately because the inline suggestions distract during code review or pairing sessions β decide based on whether you're writing or reading.
The chat-specific settings under github.copilot.chat control context. github.copilot.chat.codeGeneration.useInstructionFiles lets the extension read a .github/copilot-instructions.md file in your workspace, which is how you give it project conventions without retyping them each session. Enable it and create that file with your framework, testing library, and style rules.
Finally, check github.copilot.advanced for the debug flag. Setting "debug": true writes request logs you can inspect when chat returns errors, and it's the first thing support will ask you to enable. Turn it off afterward; the logs are verbose.
Using Chat, Inline Suggestions, and the Command Palette in Practice
The Chat view is the workhorse. Press Ctrl+Alt+I, type a question in plain English, and reference files with the # symbol β typing # opens a picker of workspace files and symbols. You can also drag a file from the Explorer into the chat input, or select code in the editor and press Ctrl+Alt+I to attach the selection automatically.
Four chat modes exist in current builds: Ask, Edit, Agent, and a planning-oriented mode depending on your version. Ask answers questions without touching files. Edit proposes a diff across one or more files and shows you accept/reject controls per hunk. Agent runs multi-step tasks, creates files, and executes terminal commands with your approval. Use Ask for explanation, Edit for refactors, Agent for scaffolding.
Inline suggestions appear as grey ghost text. Press Tab to accept, Escape to dismiss, and Alt+] or Alt+[ to cycle through alternative suggestions when the first one misses. If nothing appears, check the Copilot status icon in the bottom status bar β a slash through it means suggestions are disabled for that file's language.
The Command Palette holds the less discoverable actions. Type "Copilot" to see the full list: "Explain This," "Generate Tests," "Fix This," "Generate Docs," and "Copilot: Open Completions Panel" among them. "Generate Tests" is underused and genuinely useful β put your cursor in a function, run it, and you get a test file scaffold in the language your workspace already uses.
Context matters more than prompt wording. Chat sees the files you attach and the file currently open, plus any # references. It does not automatically read your whole repo. If an answer ignores a helper function, attach the file containing it. The difference between a mediocre and excellent answer is usually whether you included the right three files.
Free Tier Versus Paid Seats: What Each Unlocks in the Editor
Microsoft's free Copilot tier in VS Code is real but limited, and the limits changed more than once during the rollout. Rather than quote a monthly completion count that may be stale by the time you read this, check the Copilot billing page in your account settings β it shows your current allowance and reset date. The table below compares the tiers on dimensions that stay stable.
| Dimension | Free tier | Individual paid plan | Business / Enterprise seat |
|---|---|---|---|
| Chat requests per month | Capped allowance, resets monthly | Higher cap, typically unlimited with fair-use limits | Pooled through organization |
| Model choice in picker | Limited model list | Broader model list including premium models | Admin-controlled model policy |
| Policy and audit controls | None | None | Org-level policy, audit logs |
| Data exclusion from training | Opt-out available in settings | Opt-out available in settings | Admin can enforce exclusion |
| Identity required | Microsoft or GitHub account | Same | Entra ID work or school account |
| Setup complexity | Lowest | Low | Requires admin assignment |
The Business and Enterprise tiers are where "without GitHub" becomes truly clean. An admin assigns the seat through the Microsoft 365 admin center or GitHub's organization settings, the user signs in with their work account, and no personal GitHub profile ever enters the picture. Free and individual tiers accept a Microsoft account but the underlying entitlement still routes through GitHub's billing infrastructure, which is why the sign-in flow sometimes offers GitHub first.
Premium model requests consume more of your allowance than standard requests. If you're on a capped tier and use a reasoning-heavy model for every question, you'll exhaust the allowance faster than the raw request count suggests. Reserve premium models for genuinely hard problems.
When Sign-In Fails: Five Symptoms and Their Fixes
The most common failure is a successful browser sign-in that doesn't propagate back. VS Code shows "Signing inβ¦" indefinitely. Kill the process, reopen, and check whether a firewall is intercepting the loopback callback the extension uses. Some corporate VPN clients block localhost redirects.
The second is "No Copilot subscription found" despite a valid license. This usually means you signed in with a personal Microsoft account when the license sits on a work account. Sign out of everything through the Accounts icon in the Activity Bar, then sign back in choosing the organizational identity explicitly.
The third is chat working but inline suggestions dead. That's almost always the per-language enable map. Open Settings, search github.copilot.enable, and confirm your language's toggle is checked. A related cause is a workspace-level settings file overriding your user settings β check .vscode/settings.json in the project.
The fourth is the extension loading but the Chat view showing a blank panel. Corrupted extension host state causes this. Run "Developer: Reload Window" from the Command Palette; if that fails, uninstall both Copilot extensions, reload, and reinstall. Your sign-in survives this because credentials are in the keychain.
The fifth is proxy-related timeouts during requests while the UI looks healthy. Enable github.copilot.advanced debug logging, reproduce the failure, and open the Output panel's Copilot channel. You'll see the failing endpoint in the log, which tells your network team exactly what to allowlist.
Organization Policies That Silence Copilot Even After Install
An installed extension with a valid license can still refuse to answer if your organization's policy blocks it. Admins can disable Copilot entirely at the tenant level, restrict which models appear in the picker, block specific file types from being sent as context, or require that content exclusion rules be respected. When policy blocks a request, the chat usually returns a generic "unable to complete" message rather than naming the policy.
Content exclusions are worth understanding. Organizations can define paths β files matching patterns like secrets directories or customer data folders β that Copilot won't read even when you attach them. If you attach a file and the answer conspicuously ignores it, an exclusion rule may be the reason. Ask your admin for the exclusion list rather than guessing.
Model policy is the other silent blocker. The model picker might show only one option when you expected five. That's an admin decision, not a bug. Enterprise deployments commonly restrict to models with specific data-handling commitments, and the picker reflects that restriction honestly.
If you're the admin setting this up, the Microsoft 365 admin center's Copilot section and GitHub's organization settings both control overlapping surfaces. Assign the license in Microsoft's portal, then confirm the seat appears in GitHub's organization billing page if your org uses GitHub's identity layer. Mismatched assignments between the two portals produce the "license exists but nothing works" ticket that support teams see most often.
Working Without GitHub Features: What You Give Up and What You Keep
Choosing not to use GitHub means losing a specific set of capabilities, and it's worth knowing which before you commit. Copilot code review on pull requests requires GitHub. Copilot in github.com's web interface requires GitHub. Copilot Workspace, the browser-based task planner, requires GitHub. None of these affect in-editor chat.
What you keep is substantial: inline completions, the full Chat view with Ask/Edit/Agent modes, file and symbol references, test generation, doc generation, terminal command suggestions through the integrated terminal's shell integration, and the "Explain This" action on selected code. For most day-to-day coding, that's the whole product.
The gap shows up in team workflows. If your team reviews code on GitHub, the AI review comments won't appear. If your CI runs on GitHub Actions, Copilot's suggested workflow fixes won't have context. Teams standardized on Azure DevOps or GitLab keep their review flow but lose Copilot's GitHub-native review integration entirely.
A practical middle path exists: use an organizational Microsoft account for the license and never create a personal GitHub profile. You get the editor experience, your organization gets the audit trail, and no personal account is exposed. Many enterprises deliberately configure this way, and it's the cleanest reading of "without GitHub" that still delivers the full editor product.
A Realistic Setup Timeline and Where the Minutes Go
Budget roughly twenty minutes for a clean first-time setup on a machine with no prior Copilot install, and up to an hour if you hit a sign-in or proxy issue. The breakdown matters because people underestimate the identity steps and overestimate the install.
| Phase | Typical time | What consumes it |
|---|---|---|
| Version check and VS Code update | 3β8 minutes | Download and restart if the build is old |
| Extension install and reload | 2β3 minutes | Two extensions, one reload |
| Sign-in and browser handoff | 2β5 minutes | Longer if MFA prompts appear |
| Settings adjustment | 4β6 minutes | Per-language map, instruction file, debug flag |
| First chat and verification | 2β4 minutes | Confirming context references work |
| Failure recovery, if needed | 15β45 minutes | Proxy allowlist, identity mismatch, token cleanup |
The failure recovery row is where the variance lives. A blocked endpoint requires a ticket to network operations, which can take a day. An identity mismatch you can fix yourself in ten minutes once you know to sign out of both surfaces. Budget the clean path and set expectations that a corporate laptop may take longer.
Frequency of maintenance is low. Extension updates arrive through VS Code's normal update mechanism, and a major chat feature occasionally requires a fresh sign-in. Plan on one re-authentication every few months, usually after a VS Code major version bump or an organizational password rotation.
FAQ
Can I use Copilot in VS Code with only a Microsoft work account and no GitHub profile at all?
Yes, if your organization assigns you a Copilot license through the Microsoft 365 admin center and your VS Code build is current. The extension authenticates against your Entra ID identity, and no personal GitHub profile is created. Confirm with your admin that the seat is assigned, then sign in choosing the Microsoft option rather than the GitHub one.
Why does the Chat view still ask me to sign in after I completed the browser prompt?
A stale credential in the OS keychain usually causes this, particularly if you previously signed in with a different identity. Run "GitHub Copilot: Sign Out" from the Command Palette, close VS Code fully, reopen, and sign in again. If it persists, a firewall blocking the loopback callback is the next thing to check.
Does the free tier work without any GitHub account?
It can, provided you sign in with a Microsoft account and your region and account type are eligible for the free offering. Eligibility has changed during rollout, so verify on the Copilot plan page in your account settings rather than relying on a blog post. The page shows your current allowance and reset date.
Is Copilot included in my Microsoft 365 subscription automatically?
Not automatically for every plan. Consumer Microsoft 365 plans and organizational plans differ in whether Copilot is bundled or sold as an add-on, and the bundling has shifted over time. Your admin center's license assignment page is the authoritative check for organizational accounts; consumer plans list Copilot on their feature pages.
What's the difference between Copilot Chat and the older inline completions?
Inline completions are ghost-text suggestions accepted with Tab, scoped to the cursor position. Chat is a conversational panel with file attachments, multi-file edits, and agent mode. Both ship in separate extensions, and chat depends on the core extension being installed. You can run completions alone if chat distracts you.
Can my company block Copilot even though I installed it myself?
Yes, tenant-level policy overrides local installation. Admins can disable the service, restrict model choice, and define content exclusions that prevent files from being read as context. When policy blocks a request, the error is usually generic rather than descriptive, so ask your admin for the exclusion list and model policy.
Do I lose anything important by never connecting GitHub?
You lose pull-request code review, the web-based Copilot experience, and Copilot Workspace. You keep inline completions, all chat modes, file references, test and doc generation, and terminal suggestions. Teams that review code on GitLab or Azure DevOps lose only the review integration, not the editor assistance.
How often do I need to re-authenticate?
Roughly every few months in practice, typically triggered by a VS Code major update or an organizational password change. There's no fixed schedule published; the token lifetime is managed server-side. If chat suddenly asks for sign-in on a machine that worked yesterday, re-authentication is the expected fix, not a sign of misconfiguration.
Setup without GitHub comes down to one rule: the license is the requirement, and the extension name is just branding. Get the license confirmed, install both extensions, sign in with the identity that holds the seat, and adjust the per-language and chat settings once. Everything after that is normal editor work.