2.1. Using Copilot in the IDE

💡 First Principle: The IDE is Copilot's richest context environment because it can see exactly what you see — open files, the active selection, neighboring tabs, and your edit history. That local context is why the same request often produces better results in the editor than anywhere else.

Why this matters: most exam scenarios that mention "a developer in VS Code" or "in their IDE" are testing whether you know how Copilot is enabled, which interaction surfaces exist there, and how to keep sensitive files out of its view. Miss the setup or the surface and you'll pick an answer that simply isn't available where the developer is working.

The mental model is a workbench. The editor is the bench, your files are the tools laid out on it, and Copilot is an assistant standing beside you who can only help with what's actually on the bench. Tidy the bench (good context) and the help improves; hide a drawer (content exclusion) and the assistant won't touch it.

⚠️ Common Misconception: "If my IDE supports Copilot and I have an email, I can use it." Copilot authenticates through a GitHub identity everywhere. You need a GitHub account on an eligible plan, trial, or free tier — an email alone, or an Azure subscription, does not enable Copilot.