Hi all,
I'm helping a bank connect Jira Cloud to Microsoft 365 Copilot. The hard requirement is that every user sees only the Jira data they can see in Jira themselves. Because it's a bank, we can only recommend setups that are officially documented and supported. I have two questions.
1. Global permissions: groups only, or groups and users?
The Microsoft Jira Cloud connector account needs two global permissions (Administer Jira, Browse users and groups). The Atlassian docs give two different answers on how to grant them:
- "What are global permissions" says they "can be granted to groups created by your Organization admin".
https://support.atlassian.com/jira-cloud-administration/docs/what-are-global-permissions-and-what-do-they-do/
- "View, grant, or revoke global permissions" says to use the Grant Permission section "to grant access to a group or user".
https://support.atlassian.com/jira-cloud-administration/docs/view-grant-revoke-global-permissions-in-jira/
On my Cloud site, the Grant Permission form only offers a group, so the second page looks outdated. Can anyone from Atlassian confirm which is correct?
2. Atlassian MCP server with Microsoft Copilot Studio
The alternative to the connector is a Copilot Studio agent that connects to the Atlassian MCP server (https://mcp.atlassian.com/v2/mcp). Each user would sign in with their own Atlassian account, so permissions apply immediately instead of after the connector's daily sync.
What I found so far:
- Atlassian's list of supported clients names ChatGPT, Claude, Docker, Gemini and Amazon Quick Suite. Copilot Studio is not on it.
https://support.atlassian.com/atlassian-ai-gateway/docs/set-up-clients/
- Microsoft documents adding an existing MCP server to a Copilot Studio agent, but says nothing about Atlassian specifically.
https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent
- Microsoft's Copilot Studio CAT team blogged a working setup using OAuth 2.0 with Dynamic discovery. It's a blog post, not official documentation.
https://microsoft.github.io/mcscatblog/posts/atlassian-jira-remote-mcp-copilot-studio/
- Community threads report AsyncResponsePayloadTooLarge errors, 400/404 errors on create, and agents running under the builder's account instead of each user's.
Questions:
a) Is Copilot Studio an officially supported client for the Atlassian MCP server, or on the roadmap?
b) Has anyone confirmed per-user authentication (each end user signs in with their own Atlassian account) when the agent is published to Teams and Microsoft 365 Copilot? Does the audit log show the individual users?
c) Does this need a paid Rovo plan, or only Rovo enabled on the site?
Any official answer or real production experience would help a lot.
Thanks,
Pavel