Samuel Desrosiers-Theroux

Hello hjbos,

Sounds good—I'll close this topic for now. If after upgrading to 2026.3 you continue to experience repeated alerts about synced disabled users, please let us know and we'll investigate further.

Best regards,

Hello hjbos,

Thanks for the update. I saw in your other thread that you were able to fix your gateway problem, so you should now be able to upgrade.

The synchronization fix shipped in 2026.2 and is also in 2026.3: users that are disabled or deleted on the provider side are no longer reported as warnings, so the "succeeded with warnings" email only goes out for providers that could not be reached or for genuine failures.

Once you have upgraded, let us know if the emails keep coming and we will take another look.

Best regards,

Hello,

Thank you for your patience on this one.

After further investigation, it turns out the emails you are receiving come from the authentication provider user synchronization notifications, which is a separate mechanism from the one addressed by the earlier fix — so that fix was not related to your problem, and we apologize for the confusion this may have caused.

The synchronization notifications were improved in Devolutions Server 2026.2: accounts that are disabled on the provider side no longer trigger the "synchronization succeeded with warnings" email on every run. Upgrading to 2026.2 or later should resolve the issue.

Could you confirm which version you are currently running — are you still on 2026.1? And are the emails you receive still identical to the screenshot in your first post? If not, a screenshot of a recent one would help.

Best regards,

Bonjour Maxime,

Un billet a été créé. Nous allons ajouter cette information dans le rapport prochainement.

Merci

Thank you for the additional information. We identified the issue, and a fix will be available soon. In the meantime, you can work around it by selecting your custom template instead of “Default template” — that should make the password policy settings under Administration → Privileged Access → Default Settings apply correctly.

Best regards,

Hi @rdonohue — Thanks for reporting this. We’ll try to reproduce the issue on our side. In the meantime, could you please confirm what password policy is configured on your user account? You can check this by editing your account settings and reviewing the password policy there.

Best regards,

Hi jmalina,

the issue is resolved in the new release 2023.3.6.

Best regards,

Hi,

Sorry to hear about this, I've found the problem and the fix will be available in the next few days.

Best regards,