MS Fabric Remote MCP — AADSTS9010010 OAuth incompatibility

I’m unable to connect to the Microsoft Fabric Remote MCP (https://api.fabric.microsoft.com/v1/mcp/core) due to a known OAuth incompatibility. Cursor sends a resource parameter in the authorization request that Microsoft Entra ID v2 rejects with error AADSTS9010010: The resource parameter provided in the request doesn't match with the requested scopes.

This is the same issue documented in your community forum. Cursor’s static OAuth auth block and the dynamic client registration approach both fail. The Fabric Remote MCP is currently unusable in Cursor.

Could you clarify if there’s a workaround, or if a fix is planned? Many users are hitting this — forum thread for reference: Working Solution: MCP Server OAuth with Microsoft Entra ID on Azure Container Apps

Thanks

Hey @abrxb!

We’re tracking this issue internally, and I’ve added your report.

This appears to affect multiple Microsoft MCP servers, and I think some users have found a workaround using an authorization token rather than OAuth!

Any update on this? It’s also an issue when creating MCP servers that use Entra for OAuth. Needing a wrapper just for Cursor users is painful, and that makes distribution difficult as well.

Hey folks, thanks for checking in.

This is still a known issue we’re tracking, and I don’t have a user-facing change to share yet. The team is actively working in this area of MCP authentication, so I’ll update this thread when there’s something concrete!

In the meantime, two workarounds depending on your setup:

  1. If the server can accept a static token, you can bypass OAuth entirely by putting a bearer token in the “headers” section of your mcp.json entry (and removing the “auth” block).

  2. @dbergin_serverless, if you control your own server’s Azure registration, you may be able to fix it on the Azure side: add the MCP server URL as an additional Application ID URI on the app that owns the requested scope (this requires a tenant-verified domain). That makes the resource value and the scopes resolve to the same app, which Entra accepts.

I’ll try with a domain. I’m doing early testing with the default app id uri which obviously doesn’t work now without a work around wrapper to customize the interaction with Entra due to differences in Oauth implementations between cursor and Entra in that case. Looking forward to trying with an actual dns registered uri, though.