403 Forbidden on transcript content request

ignatovf - Based on the context provided, there could be a few reasons why the second app is receiving a 403 error when trying to access the /users/<user_id>/onlineMeetings/<onlineMeeting_id>/transcripts/<transcript_id>/content endpoint.

1. Application Access Policy: The tenant administrator must create an application access policy and grant it to a user. This authorizes the app configured in the policy to fetch online meetings or online meeting artifacts on behalf of that user (with the user ID specified in the request path). If this step was not completed for the second app, it could result in a 403 error. 

2. Meeting Expiration: This API works for a meeting only if the meeting has not expired. If the meeting has expired, the API call will result in a 403 error. 

3. Resource-Specific Consent (RSC): The application permission OnlineMeetingTranscript.Read.Chat uses resource-specific consent. If the RSC was not properly configured for the second app, it could result in a 403 error. 

4. Permissions: Ensure that the second app has the required permissions. The permissions required to call this API are OnlineMeetingTranscript.Read.All for Application permission type. If the second app does not have these permissions, it could result in a 403 error.