Forum Discussion
Solved
Public Teams Live Event prevents MSFT accounts from joining
A client created a public Teams Live Event, they informed us several people had trouble joining. Anyone can join the event anonymously, no problem. Also if they are logged into the Teams websi...
- 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 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 😄
- Totally agree. I've probably assisted with hundreds of issues related to credentials, loops, weird error messages and which type of user it was. Been having them myself needing to wipe the autostart settings (LoggedInOnce, HomeUserUpn etc.). When you send feedback to the team tell them I'm with you ;D
- I've had to remove machines from Azure AD Join then rejoin then to sort some issues.
I just wish MSFT support, MSFT 365 support, Azure AD support etc etc etc were all authorized to say "Yes, that is a bug. Thank you for reporting that to us, we will pass along all the evidence to the appropriate team. Here is a URL to the bug which you can share and track progress".
MSFT support told me to create a website to inform unknown attendees how make sure their browser is not set to open links in Teams, then to join the meeting using in-private tab and the anonymous option. Then spouted other utter ridiculousness.
I explain the issue when creating the support ticket, with screenshot.
Then they call and want a demo, so go through that.
Then they email and want a break down with screenshots, which was provided when created the ticket and again when they called the first time and issue was demo'd, so do that.
They they say the spoke to some support duper team and it is known that MSFT personal accounts cannot sign in.
Ask for documentation so I can go back to my client, there is none.
Ask for an email saying what they told me verbally, so I can provide that as documentation. Just a long long email with loads of links posted in none of which states what they told me verbally.
Query when it will be fixed, because we'll end up as have already with external parties not being able to join. Told to provide examples AGAIN.
Just venting.
I miss DOS 6.22, everything just worked once you'd got your batch sorted to load different mem configs. Turns out DOS was someone else's code that MSFT purchased then just changed a few bits like A:\ to be C:\, so no wonder it just worked.
I was impressed when MSFT created Teams rather then buying Slack, but now they should have just again bought someone else's code so it just worked.
