Additional team and channel-related features and issues within Microsoft Teams for business
I found the solution.
To watch the video -> Right click the file -> Preview
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are experiencing an issue where external participants in a Microsoft Teams Shared Channel cannot play video files natively within the interface, despite having full access to other documents.
What works: External users can successfully open and collaborate on standard Office documents (Word, Excel, PowerPoint, PDFs) stored in the Shared Channel.
What fails: When an external user attempts to click on and play a video file, the playback fails immediately.
Error Message received: *"Selected user account does not exist in tenant '[Host Tenant Name]' and cannot access the application '[Application ID/Name]' in that tenant."
We have 50 external users in the Shared Channel that require to view the video.
Looking forward to any suggestion that might help to solve the issue.*
Additional team and channel-related features and issues within Microsoft Teams for business
I found the solution.
To watch the video -> Right click the file -> Preview
AI answer
This behavior is consistent with how externally shared video access works in Microsoft 365.
If the video is stored in a location that can’t be shared with external users, external participants can get access failures even though other files in the shared channel work. For SharePoint/Stream video scenarios, the supported workaround is to store the video in a SharePoint Online or OneDrive location that enables external sharing, and then share the video from that location.
For a Teams shared channel scenario, use this path:
Key point: access to Office files in a shared channel does not guarantee native video playback will work if the video is still tied to a storage location or application path that external users can’t access. Storing the video in the shared channel’s SharePoint location and sharing it from there is the recommended workaround supported by the provided guidance.
References: