I have been looking forward to the new Teams Webinar functionality. So as soon as I saw it appeared in my tenant I was keen to implement it.
I went to the calendar app inside Microsoft Teams and displayed all the meeting options available in the top right as shown above. In there I could see that I had the Webinar option, which mean that I was in theory good to set up a webinar.
However, I discovered I had a problem that I couldn’t require registration For everyone as shown above. The option was greyed out!
A little digging revealed this article:
Set up for webinars in Microsoft Teams
which indicated I need to run the following PowerShell commands:
Set-CsTeamsMeetingPolicy -AllowPrivateMeetingScheduling $True
Set-CsTeamsMeetingPolicy -WhoCanRegister Everyone
to allow anyone, including anonymous users, to register for webinars.
So, I ran these commands and waited, and waited, and waited but the For Everyone option would still not allow selection??
After much investigation here is what solved the issue for me.
I went into the Teams administration area and selected Users on the left or you can use the direct link:
I then found the user in my tenant I wanted to check and select them.
I then selected Policies from the menu in the middle of the page as shown above.
In my case, you’ll note that the Meeting policy is set to RestrictedAnonymousAccess (Direct) as shown. I then selected Details button and the following dialog appeared from the right:
RestrictedAnonymousAccess didn’t sound like the right option to have set, so I closed that dialog and selected the Edit button to change the policy assignments.
I changed the Meeting policy option to Global (Org-wide default) from the list that appeared and saved the changes.
I received an assignment message at the top of the screen and the Meeting policy value changed to Global (Org-wide default) as shown above.
After about one hour or so I could now see the For Everyone option in the Teams webinar registration section could be selected and I was good to go!
I have no idea why the Meeting policy had changed from Global To Restricted but I found the same configuration on another tenant I have. It may have something to do with the security I set up for my environments. Not sure. However, hopefully, if you see the same issue you now know where to look to get it sorted!
7 thoughts on “Microsoft Teams Webinars not allowing registrations for everyone”
Thanks for this and all the other posts you do!
I am curious, being I have trouble just coming up with answers to problems, let alone document them for others.
Using this as an example, how did this play out? You saw the problem, followed the links, ran the PS commands, etc, and got it working. Then go back and document what you did for the blog, remembering the steps you did?
Or do you immediately start noting the web page you went to, what PS commands you ran (and do screen shots?). Or some mix in between. Again, for myself, I get focused on solving a problem, Yes, it would be better for me to take notes for the next time the issue comes up. But I’d go through lots of websites / steps that lead to dead ends. Documenting all those dead ends would slow down the resolution even more.
I keep a running history in OneNote and create the blog articles after resolution as ‘final’ documentation I can refer to and search. Have a look at as an example of where I am currently stuck on a problem that I am still working on https://blog.ciaops.com/2021/06/02/i-need-help-with-windows-defender-system-guard/. That post is nothing compared to the OneNote notes I have on this issue.
I don’t have the ability to create webinars yet; maybe it’s still in the process of being released?
You should have it. Check with MS to see if it is in your tenant by raising a service request.
Thank you for this information. I’m trying to ensure that guest accounts will not be created in our tenant if we open up webinar registration to everyone. Do you know?
I suggest they will if your guests are using Azure B2B as it is everyone in your org and technically guests u invite are in your org as I understand it.