Issues arise when the O365 auth token expires within Microsoft Office 365 environment, the Teams integration breaks but also users that are configured with the Teams profile are reverted back to the default feature profile so not only does the Auth need to be renewed and updated on O365 but all users need to be reconfigured as Teams profile users, with no way of knowing which users were integrated and which were not.

Currently there is no visibility of this being visible from MSL and are reliant on either the customer's IT to notify, or storing reminders outside of the platform.

Therefore, requesting that as part of the token authentication process can MSL track the expiration date of the existing token and store / display this somewhere in the Integration configuration, so that this is visible within MiCollab so tech's can see when this date is and pre-emptively schedule work to renew ahead of the expiration.

If it can't be stored locally, can the MSL poll the token as part of its integration with O365 to then be able to query it on demand to again determine when its due to expire.

Once the Expiration date is either being polled regularly from o365 or stored locally / displayed within MSL - can there then be Alarm notifications added when hit 28 day's expiration in the same manner that Web certificates notify increasing severity alarms as they near the Web certificate expiration date.

I believe there is already a design story in play but also needs visibility from our review for design consideration. Linked to RQST00001147889.