Summary

Customers using Microsoft Entra ID as their Identity Provider (IdP) are requesting support for Enterprise Managed Authentication, also referred to as Cross-App Access (XAA), on the Atlassian Rovo MCP Server.

The current official documentation only describes Okta as the supported IdP. Microsoft Entra ID has not yet been formally tested, validated, or documented for this workflow.

Customer Impact

Customers that use Microsoft Entra ID as their primary IdP need Enterprise Managed Authentication to centrally control how users authorize MCP clients to access Atlassian tools through the Rovo MCP Server.

Without documented and validated Entra ID support:

• Customers cannot confirm whether the integration is supported.
• Customers do not have Entra-specific configuration instructions.

Current State

The existing Configuring Enterprise Managed Authentication documentation is written exclusively for Okta.

The documented setup steps refer to:

• The Okta Admin Console
• An Okta XAA Resource application
• Okta tenant URLs and configuration values

Enterprise Managed Authentication is understood not to be inherently Okta-specific. However, Microsoft Entra ID has not been formally tested or certified for use with the Rovo MCP Server, so there is currently no confirmation that the workflow operates correctly with Entra ID.

Requested Capability

Add supportability for Microsoft Entra ID as an Identity Provider for Enterprise Managed Authentication (XAA) on the Atlassian Rovo MCP Server.

This should include formal validation of the integration and the publication of Entra-specific setup documentation.

What Is Needed

1. Testing and certification of Entra ID with XAA
   1. Formally test and validate Enterprise Managed Authentication with Microsoft Entra ID.
   2. Confirm that users can authorize MCP clients through Entra ID and access Atlassian tools through the Rovo MCP Server.
   3. Identify any functional differences, limitations, or configuration requirements compared with Okta.
   4. Document the supported Entra ID configuration and any known limitations.

Reference

• Configuring Enterprise Managed Authentication