web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / OAuth 2.1 Support for ...
Copilot Studio
Answered

OAuth 2.1 Support for MCP Connector

(0) ShareShare
ReportReport
Posted on by 3

Hi all,

I’m currently integrating HubSpot with Copilot Studio using Remote HubSpot’s MCP server.

The MCP server is configured with OAuth 2.1, and I’ve confirmed that the authentication flow works correctly using the MCP Inspector. However, when I try to connect to the same MCP server from an agent in Copilot Studio, the connection fails.

From what I can see, this appears to be related to the authentication protocol on the Copilot Studio side. It looks like the Copilot Studio MCP connector currently expects OAuth 2.0, which may be causing incompatibility with HubSpot’s OAuth 2.1 implementation.

My questions are:

  1. Does Copilot Studio’s MCP connector currently support OAuth 2.1, or if OAuth 2.1 is not yet supported, is there any roadmap or timeline for when it will be implemented?
  2. Has anyone found a workaround when integrating MCP servers that require OAuth 2.1?

Any insight or from others who’ve run into a similar issue would be greatly appreciated.

Thanks in advance

I have the same question (0)
  • Verified answer
    Prasad-MSFT Profile Picture
    Microsoft Employee on at
    1. Does Copilot Studio’s MCP connector support OAuth 2.1?
    No, OAuth 2.1 is not officially supported yet.
    The connector expects OAuth 2.0 flows and may fail if the MCP server enforces OAuth 2.1-specific requirements.
    2. Is there a roadmap or timeline for OAuth 2.1 support?
    Microsoft has not published a public roadmap or ETA for OAuth 2.1 support in Copilot Studio connectors as of January 2026.
    You can track feature requests or submit feedback via the Microsoft Copilot Studio feedback portal.
    3. Workarounds for MCP servers requiring OAuth 2.1:
    If possible, configure your MCP server to allow OAuth 2.0 compatibility mode for Copilot Studio connections.
    Some users have implemented a proxy or middleware that translates OAuth 2.0 requests from Copilot Studio to OAuth 2.1 for the backend service, but this adds complexity and is not officially supported.
    If you control the HubSpot app registration, check if you can relax the OAuth requirements to accept 2.0 flows for this integration.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Copilot Studio

#1
Romain The Low-Code Bearded Bear Profile Picture

Romain The Low-Code... 240 Super User 2026 Season 1

#2
Valantis Profile Picture

Valantis 226

#3
Arild Aarnes Profile Picture

Arild Aarnes 73 Super User 2026 Season 1

Last 30 days Overall leaderboard