Support Microsoft Copilot Studio (MCP) authentication: OAuth 2.0 (no DCR) and per‑user impersonation
We need a compliant, privacy‑preserving way to connect MS Copilot Studio to Glean via MCP that aligns with Copilot Studio’s supported auth schemes and enables per‑user access controls without custom headers. Problem: MS Copilot Studio supports MCP auth via No Auth, API Tokens, and OAuth 2.0 without Dynamic Client…