Reconnecting Tokens After Office 365 Password Reset

\# written by elvira horbachevska | last published at september 02, 2024 \# when you change your microsoft email password, the authentication tokens that manage your login sessions automatically expire these tokens are what allow your erp system to stay connected to your email account once they expire, any actions that rely on this connection—like sending emails—will fail until you renew the token this expiration is a crucial security measure to ensure that all your systems stay in sync after a password update reconnecting your email account within the erp system ensures that your new credentials are correctly recognised, keeping your connections secure and your email deliveries uninterrupted to avoid disruptions like failed emails or connection errors, follow the steps below to update the token and restore your service smoothly \# steps to re synchronise your enapps account after a password change once you’ve changed your microsoft 365 password, it’s essential to follow these exact steps to ensure that your email integration within the erp system is synchronised correctly \# user token reset 1\ open google chrome (preferably in incognito mode) using incognito mode helps prevent caching issues during synchronisation 2\ log in to your enapps account (note only the user associated with the email address for which the password was changed should perform this step ) 3\ navigate to preferences ensure that your microsoft 365 email is connected if not, click on the "connect" button once synchronised, the status should update to “connected ” \# outgoing mail server token reset 4\ go to settings > configuration > email > outgoing email services 5\ select the server that uses your synchronised email 6\ click "authorize ms user" and complete the authorisation steps this ensures that your credentials are updated and synchronised with microsoft 365 7\ once completed, click "test connection " this final check confirms that everything is configured correctly all set! your email is now synchronised, and the necessary tokens are updated to reflect the new credentials