ROVO Agent OAuth2.0 authentication fails in MS Copilot agent saying redirect URI is not allowed

[Patil Satilal]

I am trying to integrate ROVO MCP with MS copilot and it is failing with redirect URI while Oauth authentucation -> The redirect URI is not allowed; the URL is not part of Atlassian allowlisted domains for registered MCP clients. Redirect URI htps://global.consent.azure-apim.net/redirect/ 

can you whitelist MS domain so that we can start using it.

[Dr Valeri Colon _Connect Centric_]

@Patil Satilal This one’s happening for everyone right now — Atlassian’s MCP server only allows redirect URLs for approved MCP clients (Cursor, Claude Code, VS Code). Microsoft Copilot Studio isn’t on that allowlist yet, so OAuth fails with the redirect-URI error.

There’s no way to whitelist a new domain yourself, and Atlassian hasn’t opened custom MCP client registration. Today the only workaround is to run MCP through a supported client.

[Brent Lightsey]

Is there any indication of them changing this with Copilot Cowork and M365 E7 now on the horizon? Or is there a support/idea request where we could vote up an idea to allow this for Copilot Studio? Surely would be useful.