Exercise - Create a meeting policy and assign with PowerShell

  • 12 minutes

In this exercise, you'll create a meeting policy to disable remote control and enable lobby bypass for Everyone. We're looking to streamline our administration process so we'll use PowerShell to apply the policy to the group.

First, we'll create and customize the policy in the Teams Admin Center:

  1. Sign in to Teams admin center as a Teams Administrator or the Global Administrator

  2. In the left navigation menu, select Meetings then Meeting Policies

  3. In Meeting Policies, select the Add button to create a new policy.

  4. Give the policy the name “No Lobby and no remote control” and the description **“No Lobby and no remote control”

  5. In the Who can bypass the lobby in the drop down select Everyone

  6. Under content sharing disable External participants can give or request control and Participants can give or request control

  7. Select Save to create the policy.

Screenshot of creating a meeting policy

Assign the Lobby and no remote-control policy with PowerShell

In this step, we'll assign the Messaging Policy to the Tax specialists with PowerShell

  1. Run PowerShell as Administrator.

  2. First, install the Microsoft Teams PowerShell module if it's not already installed. To do so run the following command:

    Install-Module -Name MicrosoftTeams

  3. Next, connect to the Microsoft Teams PowerShell module using the following command:

    Connect-MicrosoftTeams

  4. Now, we'll assign the messaging policy to a security group with the following command:

    Grant-CsTeamsMessagingPolicy -Identity “Tax specialists” -PolicyName “No Lobby and no remote control”

  5. Watch the output. Note the policy is now assigned to that group

You have successfully assigned a Microsoft Teams messaging policy to a security group using PowerShell. Our tax specialists now have both policies applied.

Note

Note Teams policies are not applied to users instantly. It may take up to 24 hours for policies to update and apply to all users on their various clients.

Check your work

Note, it may take up to 24 hours for policies in Microsoft Teams to take effect. Once this period has elapsed, we can test if the policy is applied.

Create a third browser profile, we'll use this to join a test meeting and prove the no lobby policy is applied:

  1. Open the Microsoft Edge browser.

  2. Select the profile button on the top right.

  3. From the drop-down menu, select, other profile and add profile.

  4. Select add and start without your data.

  5. For Make your Microsoft Experience more useful to you, select Allow.

  6. You now have a third isolated browser profile.

  7. Browser to teams.microsoft.com and sign user1 into Microsoft Teams in the web client.

Using the Microsoft Edge browser profile for user1:

  1. In the browser for user1, sign into teams.microsoft.com web client.

  2. Schedule a meeting from user1 in Microsoft Teams.

  3. Join the meeting as user1 with the web client.

  4. When in the meeting, select the three dots, then meeting info.

  5. Select and copy the meeting URL from the invite.

  6. Navigate to your new browser profile, with no user signed into Office 365, and paste the URL.

  7. Now join the user1 meeting as an anonymous user.

  8. When you select join, note the anonymous user joins the meeting directly and doesn't get put in the lobby.

If the anonymous user bypassed the lobby, the policy has been successfully applied.