Wink Pings

Copilot connected 8 more services—if it won’t connect, it may not be your problem

Copilot adds 8 GitHub-certified connectors, covering Supabase, Box, Calendly, and others, in public preview. But Business and Enterprise users may get stuck on administrator toggles, MCP allowlists, and service-side approval.

Copilot’s connector list just got longer. GitHub-certified connectors add eight services, including Supabase, Box, and Calendly, in public preview. The official update first mentioned this in an update, then added a post on X. Once connected, it works across the Copilot app, CLI, and VS Code—no need to reconfigure each entry point.

Convenient, yes. Whether it actually works is another matter.

Business or Enterprise users should first check whether an administrator has enabled Editor preview features. If the enterprise MCP allowlist names each item explicitly rather than using a wildcard, administrators also need to manually add the new connectors. Some services have their own barriers; the official example is Box, which also needs to be allowed on the service side.

So when it won’t connect, don’t suspect a configuration error first. If any layer—company permissions, administrator toggles, or service-side approval—is not enabled, the entry point won’t appear. Public preview also means it’s still changing. If teams want to connect it to production workflows, they should think through permissions and rollback paths together.

Source: original post

In one sentence: Copilot connecting to more services is a product move; whether administrators open the door is the usage move.

发布时间: 2026-11-19 21:28