Forum Discussion
Stream "sign in" or "sign up" page blocking video views
MicrosoftShort answer:
If you add the query string parameter NoSignUpCheck=1 to the end of any Stream URL (including videos) it should skip the "marketing / interceptor" page you have a screen shot of above and go directly to the login.microsoftonline.com login page. You then enter your email address and it will redirect to your ADFS login page. (At least this worked when I just tried it out now).
Example:
https://web.microsoftstream.com/video/c3f9d897-5ac0-44dd-b184-363ed3062310?list=trending&NoSignUpCheck=1
For embed codes, if you add the query string parameter domain_hint=<ADFS domain> to end of a src URL on an embed code, we'll skip going to login.microsoftonline.com and go to the ADFS login page for the domain specified directly.
Example:
<iframe width="640" height="360" src="https://web.microsoftstream.com/embed/video/c3f9d897-5ac0-44dd-b184-363ed3062310?autoplay=false&showinfo=true&domain_hint=contoso.com" frameborder="0" allowfullscreen ></iframe>
Regardless of above we are also working to improve the design of that marketing / interceptor page to make it more clear for people that already have a login. (See long answer below)
I think ideally what you are looking for is a feature on our backlog for the future to look at implementing something with ADFS login acceleration, where we can skip the marketing page and login.microsoftonline.com page, and go directly to your ADFS organization specific login page. This is on the backlog but we haven't determined when we'll be able to get to that project.
Long answer:
Stream is both a service you get as part of O365 and also a service you can buy standalone. For standalone we do offer free trial sign ups of the service.
When a user isn't logged in already we send them our sign in / sign up "marketing (aka interceptor - great name you gave it) page. This offers the user to either sign in with their existing account or do a free trial if they aren't licensed yet (ad-hoc / viral sign up).
I agree with you, the page we have today isn't great for users that already do have a login. To help alleviate some of this problem we are in the process of redesigning this "marketing / interceptor" page. The new design will be something like this. When this is done do you think this will help at all?
Or do you still feel this would be an issue for your users?
Marc-
Apologizes for the SLOW response, I hate it when people don't follow-up.
I think you nailed it - we are looking for a combination of domain_hint and NoSignUpCheck in the same embedded url. We are trying to "ease" the process for our users between on-premises content and cloud-hosted content. We have found that any "friction", including login prompts, leads to calls to our help desk and general dissatisfaction with the "new" service. Office 365 smart links and using domain_hint in our Azure hosted applications have greatly reduced the calls and increased satisfaction.
I think the screen shot that you showed is an improvement over the current one, which looks rather like an error page, but I think it is just a "better" bad page. And I don't want to sound too harsh! I totally get that you guys in stream have a tough problem to crack with the various ways people access the service and I don't want to pass judgement from afar. I am also happy to help and provide feedback where needed!
- I agree with everything Larry said in his response. We are just beginning to look at using Stream in our org, and this looks like it could be the thing that prevents us from using it.
+1 to ADFS login acceleration (I think this should be the default when pulling embed code for a protected video in an ADFS enabled org).
+1 on the "better" bad page.