Currently, the Azure DevOps for Jira (Official) app only supports a single Microsoft Entra (formerly Azure AD) tenant connection per user session.

When a user's Microsoft profile is associated with multiple Entra tenants (e.g., a corporate tenant and a sandbox/subsidiary tenant), the integration defaults to the primary tenant during the authorization flow. There is currently no mechanism to manually select, switch, or define a specific tenant ID during the setup

Update the authorization flow within the Azure DevOps for Jira integration to:

1. Allow users to explicitly select which Microsoft Entra tenant they want to connect to.

1. Provide a field to manually input a Tenant ID if the automatic discovery defaults to the incorrect one.

1. Ensure that the authorisationUrl includes the prompt=select_account or common vs tenant-specific endpoints to facilitate switching.

Customers often have complex Azure environments with multiple tenants. Without this feature, users are "locked" into the default tenant recognized by the app, making it impossible to sync Jira with Azure DevOps organizations residing in secondary tenants. This results in the integration being unusable for those specific projects.