Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs
Dear @Team Talgro,
Based on the information provided, the issue appears to be related to authentication token or cache management rather than the Teams Webinar service itself.
It looks like the Laravel system appears to be incorrectly caching or refreshing the access token. After running continuously in the production environment, a token with an incorrect audience is retrieved for Teams/Graph API calls, resulting in an invalidAudienceUri error. Clearing the cache forces the application to fetch a new token, restoring normal operation. This appears to be an issue with authentication or token caching within the application itself, rather than a problem with Microsoft Teams Webinars.
Here are some recommended checks:
- Verify the access token being used when the issue occurs and inspect the aud (audience) claim.
- Confirm that tokens for different Microsoft services (Graph, SharePoint, Teams, etc.) are not being stored under the same cache key.
- Review the token refresh mechanism and ensure a new Microsoft Graph token is obtained when the previous token expires.
- Compare the cached configuration and authentication settings between UAT and Production.
- Enable logging for token acquisition and token refresh operations to identify whether a different audience token is being cached before the failure occurs.
I hope information above meet your expectations, please feel free to reach out if you have any other questions.
If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.