Small and medium business | Business Central, N...

Issue while connecting MCP server of BC to CO-pilot

(3) Share

Report

Posted on by Sachin.sharma_BCAzu...

Hi,

this issue is coming while tools fetching , yesterday working fine. but tooday and day before night its not working

"[{\"jsonrpc\":\"2.0\",\"error\":{\"code\":0,\"message\":\"An error occurred while creating the connection. Please try again or contact your administrator if the problem persists.  Exception of type \\u0027Microsoft.Azure.Connectors.Common.OData.Exceptions.ODataAuthorizationAlreadyProvidedException\\u0027 was thrown.\"}}]"
 

Categories:

Dynamics 365 Business Central

I have the same question (1)

All responses (3)

Answers (0)

Sort by

Suggested answer

OussamaSabbouh 18,722 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello,

This error points to the connector authentication/connection layer, not the MCP tool definition itself. Since it was working previously, I would first remove and recreate the connector connection, sign in again, and then refresh/reload the tools. The exception ODataAuthorizationAlreadyProvidedException suggests that authorization is being supplied more than once or that the existing connection state has become invalid. Also check whether the connection credentials expired or changed. If recreating the connection does not solve it and multiple users are affected at the same time, check Power Platform Service Health/Known Issues, because this may be a platform-side connector issue rather than something in your configuration.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 3,055 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, Thanks for the details.

This error is coming from the OData connector layer, exception type ODataAuthorizationAlreadyProvidedException. Basically it means the connection already has an authorization/token cached, and when the tool tries to create a new connection or refresh it, it conflicts with the existing one. This is a known flaky behavior on Power Platform side with OData based connectors, usually after token expiry or a failed silent refresh.
Since it worked yesterday and just stopped overnight, most probably the token expired and the automatic refresh is failing for some reason.

Quickest fix: go to the connection for this connector, delete it completely (not just "fix" or "reconnect"), then create a new connection and sign in fresh. If you are testing this in browser, also clear cookies/cache for login.microsoftonline.com, sometimes old auth session is stuck there too.

Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
MS-29082001-0 54 on at

Like (0)

Report
Copy link

Link copied!

we tried all the above suggestions, and none resolved the issue from copilot studio. we are using BC v28.3 and SaaS.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Issue while connecting MCP server of BC to CO-pilot

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Winners!

Women in Power Builds Momentum

Congratulations to the July Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Issue while connecting MCP server of BC to CO-pilot

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Winners!

Women in Power Builds Momentum

Congratulations to the July Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates