Forum Discussion
Remote MCP server returns -32603 on all tools/call with Service Principal
Our application uses a Service Principal to connect to the Power BI Remote MCP
server endpoint (https://api.fabric.microsoft.com/v1/mcp/powerbi). This was
working correctly until approximately July 31, 2026.
Now, all tools/call requests fail with:
{
"jsonrpc": "2.0",
"id": 3,
"error": {
"code": -32603,
"message": "Power BI couldn't process that request right now. Please try again in a moment."
}
}
What works:
- MCP initialize → succeeds, returns server info and session ID
- MCP notifications/initialized → succeeds
- MCP tools/list → succeeds, returns all 4 tools
- REST API POST /v1.0/myorg/datasets/{id}/executeQueries with same SP token → succeeds (DAX executes fine)
What fails:
- GetSemanticModelSchema → -32603
- GenerateQuery → -32603
- ExecuteQuery → -32603
- GetReportMetadata → -32603
Question:
Was Service Principal support for the Remote MCP endpoint changed or restricted in the 7/31 update?
Hi all_eyes_on_you,
Thank you for reaching out to Microsoft Fabric Community.
Thank you for the response, this does not look like service principal configuration issue, since authentication, initialize, tools/list and the Power BI REST API are all working successfully with the same token.
- As multiple MCP tools are returning the same error, this look like service-side issue or regression with the Remote Power BI MCP server rather than a problem in your application.
- If this was working previously and no changes were made on your side, I recommend opening a Microsoft Fabric Support ticket so the product team can investigate the backend behaviour.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar Chippa
6 Replies
Hi all_eyes_on_you,
Thank you for reaching out to Microsoft Fabric Community.
Thank you for the response, this does not look like service principal configuration issue, since authentication, initialize, tools/list and the Power BI REST API are all working successfully with the same token.
- As multiple MCP tools are returning the same error, this look like service-side issue or regression with the Remote Power BI MCP server rather than a problem in your application.
- If this was working previously and no changes were made on your side, I recommend opening a Microsoft Fabric Support ticket so the product team can investigate the backend behaviour.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar Chippa
I am facing the same issue. A few days ago it was working fine. Any suggestions are highly appreciated.
Update : I raised a support ticket and I got resolved.
Hi all_eyes_on_you,
As we haven’t heard back from you, we wanted to kindly follow up to check if your issue is resolved? or have you raised a support ticket?
Thanks and regards,
Anjan Kumar Chippa
yes, thanks for your help!
Thanks for Microsoft's support!
The error resulted from their internal changes, but they've fixed it now.
I'll validate the functional completeness on my end.
