We are unable to log in to the Jira Cloud mobile app on iOS devices where Entra ID is configured as the SAML SSO identity provider. Authentication completes successfully on both the Entra and Atlassian side — Entra sign-in logs show a successful token issuance and our Atlassian audit log records a successful user_login event — but the Jira app itself never picks up the session and shows a login failure.
Environment
What we see in logs
Jira Cloud by Atlassian entries with error 65001 (consent) → 90092 → eventual Success at the broker leveluser_login success but timing suggests this is the browser session, not the app sessionWhat we have tried
Question
We found Atlassian's support article referencing the Microsoft Enterprise SSO plugin for Apple devices as a fix for Entra ID compliance check failures in the Jira iOS app. However our issue appears slightly different — CA compliance is not blocking us, the SAML redirect callback from the browser back to the native Jira app is failing silently.
Has anyone resolved Jira Cloud iOS login failures with Entra ID SAML SSO specifically on iOS 26? Is the Microsoft Enterprise SSO plugin the correct fix for the redirect callback issue, or is there something else at play? Any experience with this on recent iOS versions would be appreciated.
The problem is probably the browser-to-app handoff, not authentication. The mobile browser completes the login but fails to redirect the session back to the Jira app. At least it looks like that for me.
Make sure your Intune/MDM policies allow Edge to share data with Jira, exempt the jiraauth URL scheme, and allow the com.atlassian.jira.app bundle ID. If this also happens with Safari on unmanaged devices, it's likely a broader iOS redirect bug and should be raised with Atlassian Support.
They should be able to identify deterministically in their logs what caused that.
Best,
Arek🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.