How to Configure Teams Meeting Live Reactions Policies in PowerShell Using Set-CsTeamsMeetingPolicy

In modern remote and hybrid workplace environments, Microsoft Teams meetings host interactive sessions ranging from informal team catch-ups to high-stakes executive broadcasts, investor earnings calls, and formal academic seminars. To facilitate non-verbal engagement without interrupting speaking presenters, Microsoft Teams includes Live Reactions (floating emojis including thumbs-up, heart, applause, laugh, and surprised reactions). While real-time reactions provide positive engagement during informal team huddles, they can introduce unwelcome visual distraction, unprofessional disruption, or cognitive clutter during solemn board meetings, legal hearings, or formal training webinars. By utilizing the Microsoft Teams PowerShell module with the Set-CsTeamsMeetingPolicy cmdlet, IT administrators can configure, enforce, and audit live reaction permissions across all organizational meetings.

Understanding Teams Meeting Live Reactions Policies

In Microsoft Teams governance architecture, the availability of live emoji reactions within meeting calls is controlled by the AllowMeetingReactions parameter within the CsTeamsMeetingPolicy policy framework.

  • AllowMeetingReactions = $true (Default): Live reactions are enabled for all meetings scheduled by users assigned this policy. Attendees can click or tap reaction buttons, causing animated emojis to float up across their video feed or shared content in real time. Individual meeting organizers can still toggle reactions off on a per-meeting basis in Meeting Options if desired.
  • AllowMeetingReactions = $false: Live reactions are globally disabled for all meetings hosted by assigned users. The reaction toolbar button is suppressed, preventing all internal and external participants from sending animated floating emojis during calls.

Administrators typically deploy custom meeting policies to assign restricted reaction rules to executive departments, legal counsel, and examination proctors while leaving reactions enabled for general staff.

Connecting to the Microsoft Teams PowerShell Module

Before managing meeting policies, verify that your administrative workstation has the current Microsoft Teams PowerShell module installed. Open Windows PowerShell or PowerShell 7 as an Administrator and authenticate to your Microsoft 365 tenant:

Connect-MicrosoftTeams

Sign in using credentials holding Global Administrator or Teams Administrator administrative roles. Confirm session details:

Get-CsTenant | Select-Object DisplayName, TenantId

Auditing Existing Live Reactions Configurations

To inspect the active status of live reactions across all meeting policies configured in your tenant, execute Get-CsTeamsMeetingPolicy:

Get-CsTeamsMeetingPolicy | Select-Object Identity, Description, AllowMeetingReactions

To check the current configuration applied by the tenant Global (Org-wide default) policy, query it directly:

Get-CsTeamsMeetingPolicy -Identity Global | Select-Object Identity, AllowMeetingReactions

By default, standard Microsoft 365 tenants report AllowMeetingReactions : True.

Disabling Live Reactions Globally Across the Organization

If your enterprise requires a uniform, distraction-free meeting culture across all corporate meetings, disable live reactions globally by updating the Global policy:

Set-CsTeamsMeetingPolicy -Identity Global -AllowMeetingReactions $false

Once updated, any meeting scheduled by users inheriting the Global organizational policy will launch with live emoji reactions completely disabled.

Creating a Custom Policy for Formal Executive and Legal Meetings

In many enterprise governance models, maintaining floating reactions for general collaborative staff while restricting them for formal board meetings or legal proceedings provides the ideal balance.

Use the New-CsTeamsMeetingPolicy cmdlet to create a dedicated restricted policy:

New-CsTeamsMeetingPolicy -Identity "Formal-NoReactions" `
    -AllowMeetingReactions $false `
    -Description "Disables floating live reactions for formal corporate and executive sessions."

Conversely, to create an explicitly enabled policy for creative and interactive departments:

New-CsTeamsMeetingPolicy -Identity "Interactive-ReactionsAllowed" `
    -AllowMeetingReactions $true `
    -Description "Permits real-time live floating reactions during all departmental meetings."

Modifying Existing Custom Policy Instances

If corporate requirements evolve, you can update existing custom policies using Set-CsTeamsMeetingPolicy:

Set-CsTeamsMeetingPolicy -Identity "Formal-NoReactions" -AllowMeetingReactions $true

Assigning Policies to Individual Users and Security Groups

After defining meeting policies, assign them to target users using the Grant-CsTeamsMeetingPolicy cmdlet.

To assign the restricted policy directly to an individual organizer by User Principal Name (UPN):

Grant-CsTeamsMeetingPolicy -Identity "[email protected]" -PolicyName "Formal-NoReactions"

To revoke a direct policy assignment and return the user to the tenant Global default:

Grant-CsTeamsMeetingPolicy -Identity "[email protected]" -PolicyName $null

To assign policies en masse across an entire Microsoft 365 Security Group (e.g., Legal and Executive Staff):

New-CsGroupPolicyAssignment -GroupId "e5f6a7b8-c9d0-1234-efab-3456789012cd" `
    -PolicyType TeamsMeetingPolicy `
    -PolicyName "Formal-NoReactions" `
    -Rank 1

Verifying Effective User Policy Assignments

To confirm that the meeting policy has taken effect on a specific user’s account, query the user policy assignment table:

Get-CsUserPolicyAssignment -Identity "[email protected]" -PolicyType TeamsMeetingPolicy

The output reports the active policy identity and assignment type. Policy modifications propagate across Teams client instances within 15 to 30 minutes, after which newly scheduled meetings will enforce the designated live reaction permissions.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.