Forum Discussion
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/microsoftteams/guest-access-checklist
But still for some reason when we try to have a Teams meeting with them the users get this error message:
"Only people with access to this org can join its meetings. If you have an account with access to this org, sign in with that account. Otherwise, contact the meeting organizer."
The meetings were scheduled from Outlook. What could cause this?
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_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 even after changing the Anonymous users can join a meeting to yes and waiting 2 days its not working or users are getting same error code. do you have any suggestion.
NiladriJJG Hi. I'm facing the same issue now. Did you resolve your issue here?
- Thank you for this post/reply. After working for years Guest access stopped and it was only by switching on "Anonymous users can join a meeting" did our Teams meetings start to work again.
I think the terminology is not helping here as a Guest in the context of a meeting is not the same as Guest to the AAD and why this error is popping up.
My interpretation is it is an anonymous user as far as AAD is concerned not as far as the meeting itself is concerned. It would help in the Guest settings to have the function of Anonymous users described as another level such as non AAD registered users can join a meeting or something.
Took hours to found this solution over a week elapsed as well as users finding alternative meeting solutions as the majority of our MS Teams meeting are with external participants.
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.
I know this is an old thread, but have this same issue that popped up out of nowhere. All guest access in that article has always been enabled.
The only thing I don't have checked is in the MS Teams Admin panel, Meetings, Meeting Settings, the first option, "Anonymous users can join a meeting" is disabled. Rest looks OK. But, that setting seems to mean anybody with the link can join the meeting.
A guest should be able to join per the article related to joining a meeting without an account:
But....no idea what is going on. MS has thrown so many changes into the Teams environment the past six months, and I recall guest stuff many times being in the articles/updates...but not sure what exactly is going on.
The person does not have a guest account in our ADS, we run a hybrid environment, but in the cloud there is no guest email/user with the name that is having the issue. Shouldn't even be a thing, any joker that has the link I guess should be able to join, then the person who is the owner should have a notice to allow them in once they connect.
Just wondering if that option I mentioned earlier matters? I enabled it for now and told the person to test with the user and let me know tomorrow.
Thx
I have had exactly the same issue again today! It was all sorted and had been working fine until now. /as with you. anonymous was off. I have had it switched on and asked the user trying to access to try again tomorrow. Please let me know what happens.
- 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.
Anonymous access is something different, MS is giving the possibility to invite users authenticated via MS, google or using an OTP for other random domains.
Can we have a solution to this problem ?
- I too have just started to look at this issue.
To mee this seems to be a bug. As @Tech Logic linked too, MS states there is a difference between Anonymous and Guest users. The option being mentioned here to fix the issue shouldn't have any effect on Guest users, only Anonymous.
MS recommends having that option set to No to block anonymous, but the whole point of a collaboration suite is to collaborate. Given Guest accounts are 'linked' to your Azure AD they should be treated separately.
Has anyone been able to setup Teams to block Anonymous but allow guest accounts? Tomas_S hello, I know this thread is old but I am facing the same issue. Strangely enough, I am the only one in my organization facing this issue. External attendees are unable to join my meetings (scheduled by me). Nobody else is affected. Does anyone know what could be the issue? Thank you
Tomas_S Where do I find the message allow annonymous users? It is when you set up the meeting? Please provide clear details.
No. It's not when you set the meeting up. You have to go into teams admins and change the policy for your tenant to allow this. It implies in the documents that disabling guest login only disables it for users not logged into teams and just using it to click on links, but I find it blocks everyone external to your group so has to be on.
admin.teams.microsoft.com
Meetings
Meeting Policies
select the global org one unless you have lots of custom ones
Scroll down to participants and guests.
Then enable Let anonymous users join meetings. I don't turn on let them start a meeting.
We're currently experiencing the same problem - all external users are being prevented from joining meetings.
I have checked:
- Users - external access - allowing external access for all domains, teams accounts not managed by an org.
- Meetings - meeting policies - allowing anonymous users etc.
- Meetings - meeting settings - allowing anonymous users etc.
Still, no luck adding external users to calls. Does anyone have any suggestions?
Also, Microsoft really need to sort out consolidation of organisational settings and their awful admin UI. It shouldn't be this difficult to administer something so simple.
