Overview
When you initiate a Virtual Event that is connected to Microsoft Teams, Schoox securely communicates with Microsoft to create or sync the meeting on your behalf. This communication relies on an authentication token that confirms permission to act for the connected Teams account.
In some cases, Microsoft may respond with a message indicating that the authentication token is no longer valid due to its lifetime having ended. Specifically, you may receive the following message:
"Event not initiated – InvalidAuthenticationToken Lifetime validation failed, the token is expired."
When this happens, Microsoft cannot proceed with the request, and the Virtual Event initiation does not complete as expected.
What’s Happening Behind the Scenes
To connect Schoox with Microsoft Teams, an authentication session is established through Microsoft’s secure APIs (Graph/Teams API). This session includes a token with a defined lifetime.
Microsoft validates this token every time Schoox requests an action, such as creating or syncing a meeting. If the token has expired, Microsoft returns a response indicating that lifetime validation has failed. This simply means that the existing authentication session needs to be refreshed.
It’s important to note that this situation is not related to the Virtual Event itself or its configuration. It is purely about the authentication session between Schoox and Microsoft Teams.
Why This May Occur
This scenario can appear under normal circumstances, including:
Token expiration over time
Authentication tokens issued by Microsoft have limited lifetimes. After long periods of inactivity or as part of routine security enforcement, these tokens may expire and need renewal.Updates on the Microsoft side
Changes such as updated security policies, permission adjustments, revoked app consent, or password updates can invalidate existing tokens, prompting Microsoft to request a new authentication session.
These behaviors are part of Microsoft’s standard security practices.
Recommended Action
Refreshing the Microsoft Teams connection restores a valid authentication session and allows event initiation to proceed smoothly.
Here’s what you can do:
Reconnect the academy-level Microsoft Teams integration
Disconnect and reconnect Microsoft Teams from your academy’s integration settings in Schoox.Reconnect the user’s personal Teams account (if applicable)
If the Virtual Event is initiated by a specific user with a personal Teams connection, have that user disconnect and reconnect their account as well.Try initiating the Virtual Event again
Once the connections are refreshed, you can proceed with syncing the Virtual Event.
Summary
This use case reflects a standard authentication lifecycle between Schoox and Microsoft Teams. Reconnecting the integration refreshes permissions and ensures continued, secure communication between the platforms. If you encounter a similar message in the future, following the steps above will help you quickly move forward with your Virtual Event.
Related Articles