A team uses Copilot Business and wants developers to use the GitHub remote MCP server from their IDEs. The organization has not previously allowed MCP servers in Copilot. The rollout must avoid local Docker setup and must confirm that GitHub issue and pull request tools are available before developers use the server for repository work. Which four actions should you perform in order? 1. Verify GitHub tools in Copilot Agent mode 2. Add the remote GitHub MCP URL to mcp.json 3. Enable MCP servers in Copilot policy 4. Configure a local Docker MCP server 5. Authenticate with GitHub or a scoped PAT 6. Update workflow triggers for pull requests

The correct sequence is 3 → 2 → 5 → 1. First, you must enable MCP servers in the Copilot policy (3) because the organization has not previously allowed them. Next, you add the remote GitHub MCP URL to mcp.json (2) to specify the server to be used. Then, developers need to authenticate with GitHub or a scoped PAT (5) to access the remote server. Finally, you verify GitHub tools in Copilot Agent mode (1) to confirm that issue and pull request tools are available before developers begin repository work. Option 4 is incorrect because the rollout must avoid local Docker setup. Option 6 is incorrect because updating workflow triggers for pull requests is not a prerequisite for enabling and verifying the MCP server and its tools.