Microsoft integration troubleshooting
Since the integration is created from your organisations Microsoft resources problems might occur based on security settings, structure and permission policys applied on the authorised user who activates the integration. Here is a list of common issues
Integration stops after X days / weeks
This can be caused by many different things, such as the end user is removed from your AD organisation (in which case just restart the integration with a different user). Or that the microsoft user / tenant is under the policy of MFA requirement every X days/week or “short sign-in frequency”. Solution is often to review conditional access in Microsoft Entra/AD.
Cause | Explanation | Fix |
|---|---|---|
Conditional Access or MFA Re-auth | Some tenants enforce policies that require users to sign in again periodically (often 30 days). | Adjust tenant Conditional Access or Session Token policies. |
Refresh Token Max Inactivity | If a refresh token isn’t used for 90 days (default) or a shorter time set by the admin, it expires. | Ensure your app exchanges refresh tokens at least once every few days. |
Refresh Token Max Age | Some tenants have a max age policy (e.g., 30 days) regardless of activity. | Admin must increase the |
User is removed from Organisation | The authenticated user was removed by an administrator on your Microsoft organisation (or a license was expired/revoked) | Re-authenticate the integration with a user that is part of your organisation and is activated correctly. |
Ochno All Rights Reserved