05-09-2018 08:43 AM - edited 05-09-2018 08:44 AM
I have a Stream video embedded in an internal intranet site using the Share > Embed iframe generated in Stream when clicking on the Share button.
The internal intranet site is authenticated using Azure AD.
When a user accesses the site on their desktop, the embedded video loads and plays without any problems. When the same page is loaded on a mobile the users are presented with the following.
The request is invalid
Your browser is not configured properly, preventing us from authenticating you. Please contact your administrator.
This is the same across both iOS and Android, have also tried different browsers on the devices too.
05-10-2018 04:28 PM
Are you using intune managed browser or something like that? I wonder if that's causing that message in some way.
05-10-2018 10:37 PM
Nope, it's the same on all devices. Have tried it on my own personal phone using Safari, Edge and DuckDuckGo and it's the same message.
If I access Stream directly the videos play fine on mobile, just seems to be when they are in the iFrame in our intranet.
05-11-2018 08:38 AM
I'm not able to reproduce this myself. My embed from a test environment works fine on Android.
I'm checking with some others on our team to see if they've heard of this issue or know what to look at next. But in parallel, can you work with your O365 Admin to open up a support ticket? Support can help get fiddler/network traces and hopefully track down more of what's going on or what next steps needed.
Sorry!
05-11-2018 08:21 PM
This same error is consistently returned in our organization when using the combination of IE11 and Windows 7. See this thread in the Power Users forum:
07-08-2018 07:13 PM
One of my clients is experiencing the same issue. Did you ever get this resolved? I keep finding solutions for Desktop, not mobile.
09-08-2018 02:27 PM
09-08-2018 02:28 PM
09-13-2018 02:17 AM
10-03-2018 01:14 AM
For Scenarios that don't work only on IOS through Safari: Disable Prevent cross-site tracking on Safari Settings
10-26-2018 11:11 AM
this did not fix it for me. Using the stream web part on a sharepoint page.
10-26-2018 11:14 AM
actually it did, just had to clear cookies and cache.