Six domains, with weights from GitHub's skills outline as of January 2026. Every domain summary below is paraphrased from the official study guide; the bullet-level objectives in Azure Mastery are tagged so you always know which domain you're being tested on.
Use GitHub Copilot Responsibly15–20%
The judgement domain. Covers the risks and limitations of generative AI, ethical and responsible AI use, and how to identify potential harms and their mitigations. Most importantly, it tests why you must validate Copilot's output before you trust it — recognising biased, insecure, or simply wrong suggestions, and knowing how a professional responds. Get this mindset right and the rest of the exam makes sense.
Use GitHub Copilot Features25–30%
The largest domain. Copilot inside the IDE — inline suggestions, Copilot Chat, the Copilot CLI, and Plan Mode — plus Agent Mode, Edit Mode, and MCP for tool-connected workflows. Also covers using Copilot in code review, Spaces and Spark, and organization-wide policy management. Expect scenario questions on which feature fits which task and how they combine.
Understand GitHub Copilot Data and Architecture10–15%
What happens under the hood: how your data is used, flows, and is shared; input processing and prompt building; the proxy service that handles filtering and post-processing; and the full code-suggestion lifecycle from keystroke to accepted suggestion. Also covers the limitations of the underlying large language models so you know what Copilot can and cannot do.
Apply Prompt Engineering and Context Crafting10–15%
Getting better suggestions on purpose: prompt structure and the role of context, how Copilot determines the context it uses, and the difference between zero-shot and few-shot prompting. Rounds out with the core principles of prompt engineering — being specific, giving examples, and iterating — so you can steer Copilot rather than accept whatever it offers first.
Improve Developer Productivity with GitHub Copilot10–15%
Copilot applied to real work: generating code, refactoring, and writing documentation; accelerating how you learn a new codebase or language; generating tests and finding edge cases; and using Copilot to improve the security and performance of existing code. This domain is about outcomes — turning Copilot from an autocomplete into a genuine productivity multiplier.
Configure Privacy, Content Exclusions, and Safeguards10–15%
The controls that keep Copilot safe to use: content exclusions and editor settings, the ownership and limitations of Copilot's outputs, duplication detection to avoid matching public code, and the security warnings Copilot raises. Expect questions on configuring exclusions at the repository and organization level and what each safeguard actually protects.