A robust email, calendaring, and collaboration platform developed by Microsoft, designed for enterprise-level communication and data management.Miscellaneous topics that do not fit into specific categories.
Hi Ali Raza
Thank you for reaching out to Microsoft Q&A forum
This behavior typically points to the Outlook mobile sign-in flow being unable to complete against your Exchange publishing configuration (most commonly Exchange update level / Extended Protection compatibility, TLS + certificate trust, or Autodiscover/ActiveSync reachability).
And because you mentioned that only a subset of users (10–15) are affected, so it often indicates an inconsistency that only some users/devices hit these configurations.
Therefore, in this context, you can follow the below instructions to see if it can help you:
- Validate TLS 1.2 and certificate trust end-to-end
- Outlook for iOS/Android is sensitive to TLS configuration and certificate validity/trust. Confirm the certificate is valid, matches the published namespaces, and is trusted by the mobile devices (public CA or properly deployed internal CA).
- Test Autodiscover + Exchange ActiveSync externally
- Run the Microsoft Remote Connectivity Analyzer tests (Autodiscover + ActiveSync) using an affected user. If the test fails, correct the indicated DNS/certificate/connectivity issue first; if it passes, proceed to client-side remediation.
- Client-side reset for only the impacted users
- On affected devices: remove the account from Outlook mobile, then re-add it after server-side checks are completed (this helps clear cached config/credentials).
Hope my answer will help you. For any further concern, feel free to let me know in the comment section.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.