Facing some issues on MS Teams webinar

Team Talgro 0 Reputation points
2026-09-09T10:27:30.4433333+00:00

I have created a Laravel application that integrates Microsoft Teams for creating webinars that learners can join and later after the webinar completes, the webinar recording is fetched from Teams and kept in database. This functionality has been tested and is working properly on the UAT server and the Production server.

However, we started facing issues on the production server after initial success.

For example, when an instructor started a webinar and a learner tried to join it, the learner was unable to join the webinar. Also, when the webinar was successfully completed, the API to fetch the webinar recording returned a JSON response with a URL Unauthenticated error.

The fetch recording error response was as follows:

 

error Failed to list recordings: {"error":{"code":"unauthenticated","innerError":{"code":"invalidAudienceUri"},"message":"Invalid audience Uri '00000003-0000-0ff1-ce00-000000000000'."}}

We have observed that when we clear the config and cache on the production server, the webinar functionality starts working properly again. However, after some time, the same issue occurs again.

The same code and configuration is working properly on the UAT server. Please note that the Production server is ON 24x7 where as the UAT server is switched off at EOD everyday.

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments No comments

1 answer

Sort by: Oldest
  1. Darren Bruce 1,315 Reputation points Independent Advisor
    2026-09-09T11:57:58.3833333+00:00

    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:

    1. Verify the access token being used when the issue occurs and inspect the aud (audience) claim.
    2. Confirm that tokens for different Microsoft services (Graph, SharePoint, Teams, etc.) are not being stored under the same cache key.
    3. Review the token refresh mechanism and ensure a new Microsoft Graph token is obtained when the previous token expires.
    4. Compare the cached configuration and authentication settings between UAT and Production.
    5. 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. 

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.