Copilot on the GitHub platform
This page covers the GitHub-platform half of Domain 2: agentic help on issues and pull requests, platform summaries, Copilot Spaces, MCP servers, retired features, and organization policy controls.
Copilot cloud agent and Copilot code review
The current name is Copilot cloud agent. It was renamed from Copilot coding agent on April 1, 2026. The old name can still appear in exam-source material, but current docs use the cloud-agent name.
The official study guide predates the rename and can still point candidates toward the former Copilot coding agent wording. Current product wording is Copilot cloud agent. A fair exam item may say "formerly" and expect you to map the names.
Cloud-agent lifecycle
- An issue is assigned. The cloud agent is given work from GitHub, usually from an issue or task.
- It works in its own environment. It does not simply type into your local editor. It runs in a separate GitHub-hosted environment.
- It makes changes. The agent can work through code changes, using the repository context and applicable instructions.
- It opens a pull request. Human review remains part of the flow. The pull request is where changes are inspected, discussed, tested, and merged or rejected.
| Feature | Where it runs | Output | Common trap |
|---|---|---|---|
| Agent mode in the IDE | IDE workflow | Multi-step changes in the editor context | Confusing it with the cloud agent |
| Copilot cloud agent | Its own GitHub-hosted environment | A pull request from assigned work | Thinking it is only chat or ghost text |
| Copilot code review | GitHub pull request workflow | Review comments and suggested fixes | Assuming it replaces human review |
Copilot code review
Copilot code review is an agentic feature. It helps review pull requests and coding changes, but responsible use still requires human accountability. Organization instructions can apply to Copilot code review on GitHub.com, and on pull requests Copilot reads instructions and skills from the head branch, not the base branch.
Code review assistance can surface issues, but it does not remove the need for tests, security scanning, policy compliance, and human approval. Cross-link this back to verification.
Pull request summaries
Pull request summaries are an assistive Copilot feature. They help reviewers understand changes faster by summarizing what a pull request changes. The exam may group PR summaries with other platform features such as code review, Spaces, and retired features that used to appear in the study guide.
| Use PR summaries for | Do not use them for |
|---|---|
| Getting a quick overview of changed files and intent. | Replacing code review. |
| Helping reviewers triage the pull request. | Proving security, correctness, or test coverage. |
| Reducing context-switching during review. | Bypassing organization policies or required approvals. |
PR summaries explain. Code review critiques. The cloud agent creates a pull request. Keep those roles separate.
Copilot Spaces
Copilot Spaces are the current way to give Copilot organized context. The retired Copilot knowledge bases feature was replaced by Copilot Spaces after knowledge bases retired on November 1, 2025.
Older exam-source material can describe knowledge bases as the Enterprise feature for organization context. Current reality is Copilot Spaces. Treat "create a knowledge base" as a retired-feature distractor unless the question explicitly asks about history.
How to think about Spaces
Use Spaces when the scenario asks for a shared, organized source of context for Copilot. They sit in the customization group of Copilot features, alongside custom instructions, Copilot Memory preview, prompt files, MCP servers, agent skills, custom agents, subagents, and hooks.
| Need | Current answer | Wrong retired answer |
|---|---|---|
| Give Copilot curated project or organization context. | Use Copilot Spaces. | Create a Copilot knowledge base. |
| Reuse instructions for a repository. | Use repository custom instructions or prompt files where supported. | Assume Spaces replace every instruction mechanism. |
| Apply policies across an organization. | Use organization and enterprise Copilot settings. | Use Spaces as a policy engine. |
MCP servers
MCP servers are the current replacement for GitHub App-based Copilot Extensions, which fully sunset on November 10, 2025. MCP belongs to the customization group and appears in the study guide wording for enhanced development and workflows.
The retirement applies to GitHub App-based Copilot Extensions. Client-side VS Code extensions are a completely different thing and are unaffected. Do not answer as if all editor extensions were retired.
What MCP gives Copilot
MCP servers connect Copilot workflows to additional tools and context. On the exam, read MCP as the current extensibility answer when a retired extension name appears as a distractor.
| Question wording | Best answer | Why |
|---|---|---|
| "Extend Copilot with external tools or context." | MCP servers. | Current replacement for the retired GitHub App-based extension model. |
| "Use a VS Code extension installed in the editor." | Client-side VS Code extension. | Unaffected by the Copilot Extensions sunset. |
| "Manage the enterprise MCP policy." | Use enterprise or organization policy where MCP support is generally available. | The brief notes that the MCP servers policy does not control the GitHub MCP server inside third-party hosts like Cursor, Windsurf, or Claude. |
Retired features and replacements
Retired feature names are excellent distractors. The rule is simple: learn them so you can reject them as current answers.
Use retired names only when you are explicitly saying they were renamed, retired, no longer live, formerly used, or replaced. Never present them as the correct current feature.
| Retired or renamed item | Status | Current replacement or safe framing | Exam trap |
|---|---|---|---|
| Copilot Spark | Retired August 31, 2026. | Build directly with Copilot in VS Code, Copilot CLI, and the GitHub Copilot app. Already-deployed Spark apps continue to work. | The August 7, 2026 study guide still says to utilize Spark. |
| Copilot Extensions | GitHub App-based Copilot Extensions fully sunset November 10, 2025. | MCP servers. | Confusing retired GitHub App-based extensions with unaffected client-side VS Code extensions. |
| Copilot knowledge bases | Retired November 1, 2025. | Copilot Spaces. | Choosing "knowledge base" for organization context instead of Spaces. |
| Copilot Workspace | Retired. The exact sunset date is unverified in the brief. | State the retirement fact only. Do not state a date. | Overconfident study material that invents a sunset date. |
| GitHub Models | Retired July 30, 2026 as the inference service behind Spark's llm() function. | Do not present it as a live service. Use current Copilot workflows instead. | Keeping a retired Spark-era service as a current answer. |
| Copilot Edits | Renamed in current docs. | Edit mode. | Missing that the study guide still uses the old name. |
| Copilot coding agent | Renamed April 1, 2026. | Copilot cloud agent. | Thinking the old name and new name are two separate features. |
| Premium requests | Renamed in current docs. | GitHub AI Credits. | Answering with retired billing terminology. |
The brief confirms Copilot Workspace was retired, but flags the exact sunset date as unverified. This page deliberately omits that date.
Organization and enterprise settings
Organization and enterprise settings control feature availability, policies, subscriptions, audit logs, and safeguards. GH-300 Domain 2 objective 2.4 covers organization-wide policy management, code review policies, feature availability across IDEs and GitHub.com, audit log events, and subscription management using the REST API.
This page covers settings at a high level. Study detailed content exclusions, public-code matching, retention, and safeguards on privacy settings and exclusions and safeguards.
| Control area | What to remember | Trap |
|---|---|---|
| Enterprise policy | Policies live on the enterprise AI controls tab or in organization settings. For most policies, enterprise admins can enable, disable, or let organizations decide. | For Copilot cloud agent, enterprises select exactly which organizations get access. |
| Policy conflicts | Multiple organizations within the same enterprise usually use the least restrictive policy. Multiple different enterprises almost always use the most restrictive policy. | Reversing the conflict direction. |
| Client policies | The Copilot app and Copilot CLI are governed by separate, independent client policies. | Assuming allowing one automatically allows the other. |
| Audit logs | Audit logs include Copilot plan changes and agent activity on the GitHub website. Query all Copilot events with action:copilot. | Assuming local client prompts are logged. They are not. |
| Subscriptions | Domain 2 includes managing subscriptions using the REST API. | Confusing plan management with personal instruction precedence. |
| Custom instructions | Instruction precedence is personal, then repository, then organization, even though org policies can control availability. | Assuming organization instructions outrank personal instructions. |
Policy memory hooks
Policies: enterprise first, then organization where allowed. Instructions: personal first, repository second, organization third. Same enterprise conflict: usually least restrictive. Different enterprises: almost always most restrictive.
The brief states that Copilot is not currently available for GitHub Enterprise Server. Do not choose an answer that says GH-300 Copilot features are supported there.
The night-before cheat sheet
Agent features
Copilot cloud agent was renamed from Copilot coding agent on April 1, 2026. It is assigned an issue, works in its own environment, and opens a pull request. IDE Agent mode is different.
Platform help
PR summaries explain pull requests. Copilot code review critiques changes. Neither replaces human review, testing, policy compliance, or security scanning.
Replacements
Copilot Spaces replaced retired knowledge bases. MCP servers replaced retired GitHub App-based Copilot Extensions. Client-side VS Code extensions are unaffected.
Retired traps
Copilot Spark retired August 31, 2026. GitHub Models retired July 30, 2026. Copilot Workspace is retired, but do not state its date. Premium requests are now GitHub AI Credits.
Policies
Most enterprise policies can enable, disable, or let orgs decide. Same-enterprise conflicts usually use least restrictive; different-enterprise conflicts almost always use most restrictive.
Audit logs
Audit logs include plan changes and agent activity on GitHub.com. They do not include local client session prompts. Retention is 180 days.