Forum Discussion
Stream videos require sign in using Teams desktop app
- May 05, 2021Someone at the client I'm working for has contacted Microsoft and it seems to be a bug they are working on. No estimates when it is solved.
Glenn_ScottI have found with authentication issues like this in the desktop app, that problem is usually solved by having the user take the following two steps. If number 1 doesn't work, try number 2.
- Sign out of Teams completely (Click on profile pic/initials in top right>Sign out) then quit Teams and restart the app and sign-in again.
- Quit the Teams app completely by right clicking on Teams>Quit Teams. Clear the Teams cache by going in Windows Explorer to %AppData%\Microsoft and deleting the Teams folder. Teams will automatically regenerate the folder when the application is restarted. Restart Teams and sign-in.
Thank you, I tried that but it did not work. I also spun up a new virtual machine with a fresh windows install and teams install and the issue occurs on a brand new setup as well with credentials being used for the first time.
The odd thing is that if I uninstall teams completely and reinstall the videos will show just fine the first time I log back into MS Teams desktop app. But if I leave the page and come back to it, the videos are back to being inaccessible and it wants me to sign into Stream. Also, if I click on the link to sign in to stream it just takes me to a blank page and never requests credentials https://web.microsoftstream.com/authredirect
- Anita BoerboomApr 28, 2021Copper Contributor
Glenn_Scott I have the same issue here. Did you already opened a support ticket at Microsoft?
millerblair The two options you mention didn't solve the issue.
- millerblairApr 28, 2021Iron Contributor
Anita Boerboomthanks for the feedback. I haven't opened a support ticket with Microsoft. Perhaps the root cause is different from what users in our tenant were experiencing.
- Anita BoerboomMay 05, 2021Copper ContributorSomeone at the client I'm working for has contacted Microsoft and it seems to be a bug they are working on. No estimates when it is solved.