Why This Matters

A botched setup is the silent killer of Copilot adoption. The most common reason new users give up in week one is a stale sign-in token, a privacy setting they meant to change but never did, or an extension that quietly failed to update. Spending ten minutes on a deliberate setup saves hours of confusion later and establishes the verification habit that the rest of this course depends on.

Concept Explained

Setting up Copilot is a four-step pipeline: account → plan → extension → sign-in. Each step has a small failure surface, and the failure is usually silent — Copilot looks like it's working but isn't, or works but with the wrong privacy posture. This lesson walks through all four steps with the explicit checks at each stage so you can verify, not assume.

How It Works

Once installed, the Copilot extension in VS Code does three things:

1. Editor hook — registers a listener on text changes so it can fire inline completions after a debounce.
2. Auth broker — uses VS Code's SecretStorage to hold an OAuth token, refreshed periodically.
3. Chat panel — adds a Copilot Chat view to the activity bar, with its own model picker and slash commands.

Sign-in uses the device flow OAuth: VS Code shows you a code, you open a browser, paste the code, and authorize. The token never leaves your local SecretStorage.

Step-by-Step Tutorial

1. Step 1 — Create or sign in to a GitHub account

If you don't have a GitHub account, create one at github.com/signup. Use a personal email you control, even if you'll later be added to a Business org — your personal GitHub identity is portable.

If your company uses Enterprise Managed Users (EMM), your IT team will provision an account for you. Skip to step 3 once you receive it.

2. Step 2 — Subscribe to a plan

Go to github.com/features/copilot/plans. For most beginners, choose Free (to try) or Pro ($10/month, recommended if you'll use Copilot daily). See BE-03 for the full plan comparison.

If you have a GitHub Education account (students/teachers), Copilot Pro is free — verify at education.github.com.

3. Step 3 — Install the Copilot extension in VS Code

Open VS Code. Open the Extensions view (Ctrl+Shift+X / Cmd+Shift+X). Search for "GitHub Copilot". Install the official extension published by GitHub. After install, the extension will prompt you to sign in.

Also install GitHub Copilot Chat (sometimes bundled — verify in the extension's dependencies). It adds the Chat panel.

4. Step 4 — Sign in via device flow

Click the Copilot icon in the status bar (bottom of the VS Code window) or run Ctrl+Shift+P → "GitHub Copilot: Sign In". VS Code shows a one-time code. Click "Sign in to GitHub" — your browser opens. Paste the code. Authorize. Return to VS Code. The status bar should now show a Copilot icon with no warning triangle.

5. Step 5 — Configure the two privacy settings every new user should touch

Open VS Code Settings (Ctrl+, / Cmd+,) and search for "Copilot". Two settings deserve attention:

• GitHub > Copilot > Chat > Allow Telemetry — turn off if you don't want to send usage telemetry.
• GitHub > Copilot > Duplication — set to "Block" if you want Copilot to refuse suggestions that closely match public code (recommended for any work code; see BE-33 for the full discussion).

For personal accounts, also visit github.com/settings/copilot and toggle "Allow GitHub to use my snippets for model training" off if you prefer not to contribute to model improvement.

6. Step 6 — Trigger, accept, and reject your first three suggestions

Open a new JavaScript or Python file. Try these three prompts:

1. Type function reverseString(s) { and pause. Gray text appears. Press Tab to accept.
2. Type // function that returns the nth Fibonacci number on its own line. A full function appears below it. Press Esc to dismiss — practice rejecting.
3. Type def is_prime(n): in a Python file. When the suggestion appears, press Alt+[ (or Option+[ on macOS) to see an alternative. Pick the one you like better.

If all three worked, your setup is complete.

Real-World Example

A new engineer joined a fintech and was handed a laptop with VS Code pre-installed but no Copilot. They followed the official quickstart, which skipped the privacy settings step. Three weeks later, during a security review, their team lead noticed Copilot's training-data setting was still on (the default for Pro accounts). The engineer's snippets — including some that referenced internal API endpoints — had been contributing to model training. The fix took two minutes; the trust repair took longer. A deliberate setup, including the privacy steps, would have prevented this entirely.

Example Prompts / Commands / Code

# After sign-in, the VS Code status bar (bottom) shows:
[✓ Copilot]                              # signed in, healthy
[⚠ Copilot: Signed out]                  # action needed
[⋯ Copilot: Rate-limited]                # wait or upgrade

# Hover the icon for a tooltip with plan and rate-limit info.

Ctrl+Shift+P (Cmd+Shift+P on macOS) → search:
  - "GitHub Copilot: Sign In"
  - "GitHub Copilot: Sign Out"
  - "GitHub Copilot: Toggle Copilot Completions"
  - "GitHub Copilot: Open Settings"
  - "GitHub Copilot Chat: New Chat"

Common Mistakes

• Skipping the privacy settings — defaults are not always appropriate for work code.
• Assuming the extension auto-updates — verify the version quarterly; Copilot ships monthly.
• Using a personal Pro account for work code — use a Business seat so the org can manage policy and audit.
• Pasting your OAuth token anywhere — it should never leave VS Code's SecretStorage.
• Forgetting to sign out on shared machines — Copilot tokens are account-level, not repo-level.
• Installing Copilot in two editors with the same account simultaneously — usually fine, but can cause confusing rate-limit messages.

Best Practices

• Set up Copilot on your primary editor first; add others later.
• Take a screenshot of your privacy settings page after setup — you'll want to verify they didn't change.
• If your company has a Copilot policy, follow it instead of the defaults above.
• Use a personal access token (PAT) with minimal scopes for any REST API experimentation, never your main account token.
• Bookmark github.com/settings/copilot for quick access to your global settings.
• After any VS Code update, briefly check the Copilot extension still works — extensions occasionally break on major VS Code releases.

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• Quickstart for GitHub Copilot
• Get started with Copilot in VS Code
• GitHub Copilot settings (reference)
• GitHub Education — free Copilot for students

Official References

• Quickstart for GitHub Copilot (official)
• Get started with Copilot in VS Code
• Configuring Copilot settings

Related lessons: BE-03, BE-05, BE-06, BE-12