Forum Discussion

virtual-tech's avatar
virtual-tech
Brass Contributor
Apr 29, 2021
Solved

webinars plus new meeting registration options

I received the change notification below and want to change my option to "Give select users the ability to create a registration page that supports external attendees. All other users would be able c...
Administrator
microsoft teams
Settings
  • VasilMichev's avatar
    VasilMichev
    Apr 29, 2021
    No need to create a security group, you simply need to assign the corresponding policy to the users who you want to be able to create meetings with external attendee registration. To do so, you can use the Grant-CsTeamsMeetingPolicy cmdlet. You can also do it via the TAC, but "registration" related settings are not yet exposed there, at least not in my tenant, so best to confirm the values via PowerShell first. Only the default "Global" policy allows Externals, so you might as well create a custom policy if needed.
virtual-tech's avatar
virtual-tech
Brass Contributor
May 21, 2021
Yup the roll-out is until end of the month. The policies are listed on the tenant but not the who can register - i think. That can be found in powershell....
BBLDCM's avatar
BBLDCM
Copper Contributor
May 22, 2021
I have exactly the same problem. Have you found the solution to allow selected users the ability to create a registration page that supports external attendees? Please advise.
  • Alberto Schiavon's avatar
    Alberto Schiavon
    Copper Contributor
    May 25, 2021

    BBLDCM 

    I have some findings to share:

    1. If I assign the Global policy (WhoCanRegister = Everyone) to a user the "Everyone" option is correctly available

    2. If I create a new policy (WhoCanRegister = Everyone) and assign it to to a user the "Everyone" option is correctly available

    3. If I assign to a user an exiting policy (WhoCanRegister = Everyone) created some months ago  the "Everyone" option is greyed-out !!??

     

    I compared all the policy parameters and even if they are exactly the same, the outcome is different (Everyone greyed-out for the old policy, Everyone available for the new policy).

    Is it a bug?

    Am I supposed to recreate all my policies from scratch?

     

     

    • Alberto Schiavon's avatar
      Alberto Schiavon
      Copper Contributor
      May 26, 2021
      Some updates: the "Everyone" option from the Team app UI was eventually available today also for users who were assigned to my old policy.
      What I believe made it work was setting the WhoCanRegister parameter to "EveryoneIncompany" and then back to "Everyone".
      If this is confirmed, it is definitely a bug.
      It took me a while to realize it as, according to my tests, if I assign a different policy to a user it just needs to re-start the desktop app (or refresh his browser for the web app) to get it applied immediately, but if I change a parameter of a policy it take a few hours to get it applied.
      • JoostvdLinden's avatar
        JoostvdLinden
        Brass Contributor
        May 27, 2021

        Alberto Schiavon ,

        I experience the same behavior.

        We just only use the Global meeting policy for all users within our company.

         

        According to https://docs.microsoft.com/en-us/microsoftteams/set-up-webinars#configure-who-can-register-for-webinars, "AllowPrivateMeetingScheduling" should be set to 'True' and "WhoCanRegister" should be set to 'Everyone'.

        This was already the case. Based on your post I have changed the "WhoCanRegister" parameter to "EveryoneInCompany" and then back to "Everyone". I will wait for a couple of hours and check its behavior.

         

        I will edit this post afterwards with my findings.

        Edit: it indeed works, takes like 3/4 hours to propagate.