How to configure policy settings for Microsoft Teams Webinars

If you have not used webinars in Microsoft Teams yet, you need to configure some policy settings. Webinars are enabled in your tenant by default, but the ability for external people to register for your events or view the engagement report is disabled. Meetings support up to 1000 attendees for enterprise customers and 300 attendees for M365 Business Premium customers, but the overflow setting is disabled by default. At GA these settings could only be configured using PowerShell, here is how you do it.

#Install latest Teams PowerShell module
#The force switch enables you to install the newest version if you have an older version already installed
Install-Module MicrosoftTeams -force

#Connect to Microsoft Teams
#Minimum requirement is that your user is enabled with the Teams Communications Administrator Role
#Teams Administrator and Global Administrator role works too

#Default config
Get-CsTeamsMeetingPolicy | Format-List Identity, AllowEngagementReport, WhoCanRegister, AllowPrivateMeetingScheduling, StreamingAttendeeMode 

Identity                      : Global
AllowEngagementReport         : Disabled
WhoCanRegister                : EveryoneInCompany
AllowPrivateMeetingScheduling : True
StreamingAttendeeMode         : Disabled

#New config
Set-CsTeamsMeetingPolicy -Identity Global -AllowEngagementReport Enabled -WhoCanRegister Everyone -AllowPrivateMeetingScheduling $True -StreamingAttendeeMode Enabled

Get-CsTeamsMeetingPolicy | Format-List Identity, AllowEngagementReport, WhoCanRegister, AllowPrivateMeetingScheduling, StreamingAttendeeMode 

Identity                      : Global
AllowEngagementReport         : Enabled
WhoCanRegister                : Everyone
AllowPrivateMeetingScheduling : True
StreamingAttendeeMode         : Enabled

Now you are ready to run public webinars, get the engagement report and even have more than 1000 attendees using the overflow to live event feature from user number 1001. You may want to create a separate Teams Meeting Policy for those booking webinars, and not user global as I have done in the above example.

In our environment we were running on AllOn built in policy and it turns out that you cannot set this setting on built in policies, only on custom policies and Global. Also the AllOn MeetingPolicy is depricated so do not use that one. If you are like us, using an old built on policy and want to set global Teams meeting policy, you can either do it manually per user in the Teams Admin Center or you can use powershell and loop through users and revert back to the global policy. If you are not specifying a UPN in the below command, it will loop through all your users and set global policy on all of them, be careful when doing this in production. Setting the policy to $Null will revert you back to a global policy.

Get-CsOnlineuser <UPN> | Grant-CsTeamsMeetingPolicy -PolicyName $Null

Fellow Office 365 for ITPros author, Tony Redmond has a well written blogpost explaining the settings in detail. Teams Meetings Get Webinar Capability (

8 thoughts on “How to configure policy settings for Microsoft Teams Webinars

  1. Hi there,
    Thanks for this excellent article, which I followed step-by-step. Whilst I can now set up a websinar and generate a registration form, it is not visibile to unauthenticated users. The issue is the “For Everyone” is greyed out in the sharing settings in the event setup.
    Thanks in advance

    • It may take time for changes to take effect, and use we client to test in case of local client cache. Also, make sure you changed the correct policy and that you are assigned the correct policy 👍

      • Thanks for your reply Ståle. I presume you meant web client (“and use we client”) … yes, that’s what I’m doing. And I’ve checked the policies assigned to the user account I set up the webinar and they are all set to global (no other policies assigned and not a member of any group assignment policies). What’s the longest time for changes to take effect? … knowing this will help me to “stop banging my head against the wall” (spending time researching the issue). Thanks in advance.

  2. Hi Ståle,
    I’ve very pleased to let you know that “For Everyone” is now available to me (no longer greyed out). Patience is definitely the key! Thanks for your expert guidance and assurance. 🙂

  3. I’ll just clarify (in case anyone else is getting guidance from this blog) that for the original test webinar I set up, “For everyone” is still greyed out. I created another test webinar in case an updated policy would not apply to a webinar already created. I was right in that the new webinar event did have “For everyone” enabled for use. PF

  4. anything that needs PowerShell will most likely only work on that PC, if it works at all, and not for anyone else, and the webinar will probably need to be run off that PC too. Are we really expecting an average user to figure all this out? What happens when i want to setup a webinar on the road via mobile, mobile doesn’t have power shell lol, neither do many devices that can run teams, this is defective, clunky and not user friendly at all. Metting polices say nothing about webinars and it also says nothing about creating list, why do i have search all of google to get these answers?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.