Forum Discussion
Solved
Only people with access to this org can join its meetings
We moved to Teams Only mode two weeks ago and now we have problems with Teams meetings with some organizations. Everything is configured using this checklist: https://docs.microsoft.com/en-us/microso...
Tomas_SI had to ask Premier support and their answer was:
"As you want to communicate with the different organisations who is not a part of your domain that's why we would be require to enable this setting "Anonymous users can join a meeting". And yes this is secure. And if there is the limitation on guest users tenant then those guest wont be able to join so... Because they have restricted there tenant for the same.And yes for External access there are 3 options which can be set according to the needs of the organization :
- Off Completely
- On except for blocked Domains: In this you can mentioned the domains which you need to block.
- On only for allowed domains: And in this you can mentioned those domains for which you want to communicate "
Tomas_S I have been troubleshooting this for two days. We just started experiencing this error since about January 11th 2021. Then again, we just activated "guest users" for MSTeams in Dec. 2020.
What I noticed in Azure AD, under the user profile, are that accounts with "Identity Issuer" set to domain.onmicrosoft.com all work great, but the accounts set to "mail" do not. If I delete the user completely and add them back in from that screen as a guest user, they are able to login and get to meetings and other MSTeams features. It is like the user's original account creation got "stuck" somewhere and never made it to the "External Azure AD". The users of these accounts had attended a meeting or two prior to this happening, so I am not sure what changed for us.
Again, the only fix was to delete the account, then add it back in from Azure AD, under guests.
We're experiencing that same issue. I have no idea why. I delete the Guest user and add back fresh, no luck. It's a gmail account of which we have many others that work fine. This one in particular keeps showing up with an identity issuer of 'mail' and it's driving us crazy. It breaks the sharing functionality.
