A developer wants Copilot Chat to be able to query the team's live ticketing system and read open issues directly while answering questions, rather than relying only on the open files. Which Copilot capability is designed to connect Chat to that external tool and its data?
- AAdd the ticket descriptions to a custom instructions file so Copilot reads the team's standing context before it answers each question.
- BDefine a content exclusion rule for the ticketing repository so that Copilot is permitted to read its issue data during a Chat session.
- CConfigure a Model Context Protocol server for the ticketing system so Copilot Chat can call it as a tool and read live issue data while it answers. Correct
- DCreate a Copilot Space that bundles the ticket exports so Chat can summarise the issues that were attached when the space was built.
Why A is wrong: Custom instructions inject standing guidance into prompts, but they are static text and cannot query a live ticketing system for current open issues on demand.
Why B is wrong: Content exclusions only stop named files being used as context and never grant access to an external live system, so they are the opposite of what is required here.
Why C is correct: Model Context Protocol lets Copilot Chat connect to external servers that expose tools and data, so a ticketing MCP server gives Chat live access to open issues exactly as needed.
Why D is wrong: A Copilot Space groups curated reference material, but it holds attached content rather than querying the ticketing system live for the latest open issues.