Forum Discussion
Public Teams Live Event prevents MSFT accounts from joining
- Hi grommit,
Have raised a uservoice for you here
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/43875447-support-msa-accounts-in-public-live-event
Would recommend to vote up to push it up the agenda. Whilst uservoice will end soon these will be moved to a new system at some point so it's important to make sure it's on there for Microsoft line of sight. I would mention it on AMA's here in the Teams community and I will also pass it along to the product and engineering team later this week.
Hope that answers your question
Best, Chris
grommit ChrisHoardMVP Hello, I just tried to reproduce the issue by creating a Public Live Event from a "work account" and send the link to a personal MS account (@outlook.com). This account is not a guest user or federated user and I was using a personal laptop signed in with that personal account. Every time, no matter if I'm using Teams on the web or the desktop app (signed in all over with @outlook.com account) I got this prompt.
For me it worked like a charm to select Join anonymously over and over. My guess is that the users that had problems with loops etc. were caused either by mixed/cached credentials or by trying to sign in to the tenant not being allowed (hence the error message).
For the record I was signed in with the Microsoft account the entire time.
Hmm, yeah, I think it may be a dual problem. Did you manage to test if you were logged into Teams for personal use at the time with that MSA account? Being in Teams for Personal use could cause the caching but I would be interested to see a confirm on that behavior for both sign in and caching. My thoughts on it is that it's not possible to join a public event whilst in use of Teams Personal. You would literally need to join anonymous from an incognito session or a browser session where you've blown the cache. If you don't have Teams for Personal Use and just the MSA account this would make for an easier sign in.
Best, Chris
Teams App
1. I had the Teams windows app up and running, logged in using my MSFT personal account.
2. I opened Edge (New/Chromium) then browsed to the public Teams Live Event url
3. The Teams windows app flashed up automatically, but rather then the expected logged in session I had before I was prompted with the below Live Event Sign In page.
4. Clicked sign-in, if memory serves my MSFT personal account was displayed so only had to accept the MFA prompt to allow this from my MSFT authenticator app.
5. Now stuck on “We just need to sign in, and then we’ll get you to your meeting“ for about 1 minute which then changes back to ‘Welcome to the live event!’ sign in page.
6. If I select Sign In again, I go through the same logon failure loop.
7. If I select Join anonymously I join the Teams Live Event without issue.
8. If I select Sign In again but provide my M365 Business work account details it works fine, different tenant to the organizser, I'm not a guest on that tenant, I wasn't invited directly to the meeting.
This is broken and not user friendly.
I've not tested from my mobile, but the M365 tenant which created the public Teams Live Event has that SharePoint Online/Onedrive setting enabled to limit un-managed devices to web access only, no apps. This may explain why the Teams app on mobile logged into using MSFT personal account threw error about needing to be a managed device, however this is a PUBLIC Teams Live Event so should just work for anyone, MSFT 365 Business accounts and MSFT Personal accounts AND anonymous.
Teams webpage
0. Set Edge (New/Chromium) to not open Teams app
1. Logon to the Teams webpage using my MSFT personal account.
2. Browsed to the public Teams Live Event url
3. Select Watch on the web instead
4. Flashes between "We're sorry - weve run into an issue" and trying again until finally gets stuck on "To open the web app, change your browser settings to allow third-party cookies or allow certain trusted domains. Try again If that doesn't work, try signing out and back in."
Teams webpage in-private
0. Delete application link that opens Team URL in Teams app
1. Open Edge (New/Chromium) in-private
2. Select watch on web
3. Select Sign in
4. Entered MSFT personal account username
5. Accepted passwordless MFA prompt to select number from MSFT authenticator app
6. MSFT sign message
Microsoft
Sign in
Sorry, but we’re having trouble with signing you in.AADSTS50020: User account '%MY MSFT PERSONAL ACCOUNT%' from identity provider 'live.com' does not exist in tenant '%PUBLIC TEAMS LIVE EVENT ORGANISER DOMAIN%' and cannot access the application '5'(Microsoft Teams Web Client) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account.
This is ridiculous, as if something can be access anonymously then why all the issues when trying to access the same thing whilst authenticated to MSFT using MSFT personal account.
How many people have given up trying to connect to public Teams Live Events, because they have MSFT personal accounts and get logon loops or unhelpful error messages? This is extremely poor, even by MSFTs low standards.grommit I can understand the frustration. But as we're talking about public events anyone can join, not anyone can sign in. If you're trying to sign in with an anonymous account (not a guest user or trusted/federated user) it will not work as the account isn't added to your org. in any way. You can actually read this in the "error message" you get. If these "live accounts" where added to the org. it would work to select the sign-in option.
ChrisHoardMVP Perhaps my MS account wasn't the best one to test with as I do have a Teams free org. associated with that as well. But, I was properly signed out of all sessions and only signed in to Teams for Personal use, both online and desktop. I did notice though right now that the icon changes from the white personal to the blue business when connecting to the live event. So perhaps I should create a brand new @outlook.com account and test again.
- For sure. I think we kind of nailed it here, the experience is inconsistent, spectral and it's not exactly intuitive which would impact your day to day users. Not a clean experience - kind of like the differing meeting experience depending on whether you were part of the org, a guest, a fed user or anon. It's definitely something which could be referred for the team to look at because I don't think this feedback is going to be the exception 😄
