Hello All,
I'm able to create Jira tickets using the Jira MCP Server in Copilot Studio. I'm hosting my agent in MS Teams. I'm able to do this using OAuth and Api key or secret token authentication. We want the Jira tickets to be created in the logged in user's name. So, we can use only OAuth.
The problem:
Anyone who tries to use the Copilot Studio Agent in Teams, to create a ticket has to first create a Jira Connection.
We have SSO Login to Teams and Atlassian. SSO is from the same provider. How can we make the ticket creation process seamless? The Copilot agent in MS Teams should create a Jira ticket without asking me to create a connection.
Thanks in advance,
Vinay
Thanks for the quick reply.
To be specific, does Atlassian Cloud natively accept Azure AD tokens as bearer tokens for their REST API.
SSO provider for Atlassian and Teams is Azure.
No.
Entra ID can be the common identity provider for Atlassian Cloud and Teams, but Atlassian Cloud does not natively accept a generic Entra ID access token as a bearer token for its REST APIs. You need an Atlassian-supported API authentication mechanism, typically Atlassian OAuth 2.0, API tokens for appropriate use cases, or an Atlassian app framework such as Forge/Connect depending on the integration design.
Hi, When CoPilot supports Enterprise Managed Authorization (https://modelcontextprotocol.io/extensions/auth/enterprise-managed-authorization), this process should be seamless as Rovo MCP Server has supports it.
I was told that CoPilot is looking into supporting it, don't have timelines.
Best,
Sunil
That's great news, thanks a lot. I'll check with the Microsoft team and get back.