Start here
Choose your Copilot path
Three questions, answered in your browser. They pick one of the five role-based routes through the lessons that already exist — no new material, no account, nothing sent anywhere.
You chose
Recommended path
Beginner
Anyone who has just been given a Copilot licence.
The shortest route from nothing to using Copilot competently every day. It deliberately skips agents, MCP and enterprise policy — those matter, and they matter later.
Software engineer
Developers writing application code who want Copilot to be useful on a real codebase rather than a demo.
Builds from editor workflow through language-specific behaviour and prompting, and ends where the leverage is: delegating whole changes to agents and giving them tools through MCP.
DevOps engineer
Engineers whose mistakes get applied to running systems rather than caught by a test suite.
Infrastructure work changes the risk calculation: a wrong suggestion may reach production. This path pairs every capability with the boundary that contains it, and spends real time on the CLI's permission model.
Security engineer
Anyone responsible for what an AI coding tool is allowed to reach, and for answering when someone asks whether it is safe.
Concentrates on the documented limits — where content exclusion stops applying, what the public-code filter does and does not assert, and what an MCP server can reach once approved. The recurring theme is that most controls here are narrower than their names suggest.
Engineering manager
Technical leaders deciding what to buy, what to permit, and how to tell whether it helped.
Covers plan economics, governance and adoption, and is candid about measurement: attribution is genuinely hard, and this path says so rather than offering a productivity figure it cannot support.
No path contains new material. Each is an ordering over lessons that already exist, so following two paths that share a lesson does not mean reading it twice — your progress is the same progress everywhere on the site.