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 / Copilot Studio cannot ...
Copilot Studio
Suggested Answer

Copilot Studio cannot integrate with Atlassian Rovo MCP via OAuth 2.1 DCR

(0) ShareShare
ReportReport
Posted on by 4
I have been trying for days to get my Copilot Studio Agents connect with Atlassian Rovo MCP, but it seems after all this is a waste of time and effort. 
 
From my research it does seem that Atlassian has already migrated to OpenAPI 3 standard whereas the same cannot be said about Power Platform and Copilot Studio MCP support. Needless to say Rovo MCP integrates just perfectly with Claude and ChatGPT, so I don't quite understand why Microsoft is lagging behind, again. It's extremely annoying to be fair. 
 
Tried to check your roadmaps, but couldn't find anything related! Would be appropriate to receive some news on that. 
 
 
Thanks,
Z
 
 
 
 
 
I have the same question (0)
  • Rintu Mondal Profile Picture
    6 on at
    Hi, 
     
    It is working fine with copilotstudio and MCP server with Atlassian API,s 
     
    You have to use the below end point to create the MCP
     
     
  • Suggested answer
    ZL-25062135-0 Profile Picture
    4 on at
    Thanks for your reply! 
     
    That is exactly the endpoint I was trying to connect to, but regardless of how or what I even went as far as to create a new PP environment for that so I could ensure no DLP and ACP policies would be preventing the use of custom connectors, results were the same. Always. At the same time Rovo as I said before, just clicks with Claude for example, which is a confirmation in itself that I have everything set-up properly on Atlassian side. 
     
    As you can see from the attached pic, the connection to Rovo MCP fails right at the beginning, so the DCR does not even take place, and the error what I get from the APIM service is quite annoying, Case is open with MS unified support however. 
     
     
    Thanks,
    Z
    c116887f-6b0f-42e...

    Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

  • Suggested answer
    sannavajjala87 Profile Picture
    515 Super User 2026 Season 1 on at
    Hi Z,
     
    I hear your frustration , you’re definitely not the only one hitting this gap right now.
    What you’re seeing is essentially a platform mismatch rather than something you’ve done wrong. Atlassian Rovo MCP is already aligned around more modern API patterns (OpenAPI 3 / MCP-first integrations), whereas Copilot Studio and Power Platform are still evolving in this space, especially around native MCP-style support.
    That’s why you’re seeing smoother integrations with tools like Claude and ChatGPT , they’re currently more aligned with MCP-based ecosystems, while Microsoft is still bridging that gap through connectors, actions, and Graph-based integrations rather than full MCP-native compatibility.
    At the moment:
    • There’s no direct/native support for Rovo MCP in Copilot Studio
    • Integration would require custom connectors or intermediate services, which can feel like extra overhead for something that should ideally be plug-and-play
    • Public roadmap visibility on MCP alignment is still limited, so it’s understandable that this feels unclear
    If you’re looking for a practical path forward today, the only workable approach is to:
    • Expose Rovo APIs via an OpenAPI definition (if available)
    • Wrap it using a custom connector or middleware layer
    • Then consume that within Copilot Studio actions
    That said, your expectation is valid , this is exactly where the ecosystem is heading, and tighter MCP-aligned integrations will likely become more important moving forward.
    I’d strongly recommend raising this through feedback channels or support as well , these signals do influence prioritization, especially for integration gaps like this.
    If helpful, I can share a simple pattern to wrap Rovo APIs into a Copilot-ready connector without too much overhead.
     
  • ZL-25062135-0 Profile Picture
    4 on at
    Hello sannavajjala87,
     
    Thanks for really taking the time and explain all this, I appreciate that very much! 
     
    Yes, please, I would really be grateful if you could share that wrapper magic with me if it is no trouble for you!

    Thanks in advance,
    Z

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 277

#2
11manish Profile Picture

11manish 206

#3
sannavajjala87 Profile Picture

sannavajjala87 156 Super User 2026 Season 1

Last 30 days Overall leaderboard