Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Hello Luís Teixeira,
The issue where the “Connect” button does nothing in the M365 Copilot app but works in Teams is most likely caused by differences in how authentication is handled across Copilot surfaces. In most cases, the button triggers an OAuth flow that should open a browser or popup window, but in the M365 Copilot app this can silently fail due to blocked pop-ups, disabled third‑party cookies, or webview limitations. Since your setup works in Teams, it indicates the plugin and MCP server are configured correctly, but the authentication redirect or browser interaction is not completing in the M365 Copilot environment. This is often due to missing or mismatched redirect URIs (typically configured for Teams only), or browser/security settings preventing the auth window from launching or persisting session state.
Adjusting pop-up permissions, enabling cookies, and ensuring your OAuth app supports all required Copilot surfaces generally resolves the problem.