An enterprise wants to roll out MCP servers for Copilot users while allowing only approved servers. The security team wants a controlled allow list that supports discovery, blocks unapproved servers on supported surfaces, and includes approved local MCP servers. Which four actions should you perform in order? 1. Set Restrict MCP access to registry servers to Registry only 2. Tell developers to manually edit local MCP configuration files 3. Inventory approved MCP servers and required tool access 4. Publish a registry with correct server IDs and manifests 5. Configure the enterprise or organization MCP Registry URL 6. Set the restriction policy to Allow all during rollout

The correct order ensures a secure and controlled rollout. First, inventorying approved MCP servers and required tool access (3) is crucial to understand the environment and what needs to be allowed. Next, publishing a registry with correct server IDs and manifests (4) creates the definitive list of approved servers. Then, configuring the enterprise or organization MCP Registry URL (5) directs clients to this authoritative source. Finally, setting "Restrict MCP access to registry servers" to "Registry only" (1) enforces that only servers listed in the registry can be accessed, blocking unapproved ones. Option 1 is incorrect because it attempts to configure restrictions before defining the approved servers or the registry. Option 3 is incorrect because it suggests manual configuration and a temporary "allow all" policy, which undermines security. Option 4 is incorrect because it configures the registry URL before the registry itself is published and also suggests manual edits and a temporary "allow all" policy.