How to Configure Teams Meeting Chat Policies in PowerShell Using CsTeamsMeetingPolicy

In enterprise collaboration environments, chat messaging during virtual meetings provides an essential backchannel for questions, links, and meeting notes. However, unconstrained meeting chat can also lead to communication compliance risks, information leaks to external participants, or persistent discussions long after a sensitive meeting has concluded. In Microsoft Teams, administrators can regulate meeting chat availability before, during, and after sessions using the MeetingChatEnabledType parameter in CsTeamsMeetingPolicy. Configuring these policies in Microsoft Teams PowerShell allows granular control across organizational departments and user tiers.

Understanding Meeting Chat Policy States

The MeetingChatEnabledType attribute within CsTeamsMeetingPolicy dictates chat availability for meetings scheduled by organizers assigned to that policy. It accepts three operational values:

  • Enabled: Meeting chat is unrestricted. Participants can post messages and share attachments before the meeting begins, while the meeting is in progress, and indefinitely after the meeting concludes. This is the default setting for standard collaboration.
  • EnabledInMeetingOnly: Meeting participants can only send chat messages while the meeting is actively ongoing. As soon as the organizer or last participant leaves and the meeting ends, the chat box becomes read-only, preventing post-meeting chatter or subsequent unauthorized file sharing.
  • Disabled: Meeting chat is completely prohibited. The chat panel is hidden or blocked for all participants throughout the session. This is commonly applied to high-security executive briefings, board meetings, webinars, or strict regulatory review boards.

Connecting to Microsoft Teams PowerShell

Open an elevated PowerShell console as Administrator and sign in to your Microsoft 365 tenant using credentials with the Teams Administrator role:

Install-Module -Name MicrosoftTeams -Force -AllowClobber
Import-Module MicrosoftTeams
Connect-MicrosoftTeams

Auditing Existing Meeting Chat Policies

Query your tenant’s existing meeting policies to review current chat settings across global defaults and custom policies:

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

To inspect the detailed properties of the default global policy:

Get-CsTeamsMeetingPolicy -Identity Global | Format-List Identity, MeetingChatEnabledType, AllowExternalParticipantGiveRequestControl

Configuring Tenant-Wide Meeting Chat Behaviour

1. Restrict Meeting Chat to In-Meeting Only (Tenant-Wide)

To prevent persistent post-meeting chat across the entire organization while allowing active discussion during live calls:

Set-CsTeamsMeetingPolicy -Identity Global -MeetingChatEnabledType EnabledInMeetingOnly

2. Disable Meeting Chat Tenant-Wide

For strictly regulated enterprise environments where all text chat must be channeled through audited standard channels rather than ad-hoc meeting threads:

Set-CsTeamsMeetingPolicy -Identity Global -MeetingChatEnabledType Disabled

3. Re-enable Full Unrestricted Chat

To restore standard pre-meeting and post-meeting chat capabilities:

Set-CsTeamsMeetingPolicy -Identity Global -MeetingChatEnabledType Enabled

Creating and Assigning Custom Departmental Chat Policies

Different business units frequently require distinct chat governance rules. For instance, legal and financial compliance teams may mandate that external consultation meetings operate with in-meeting-only chat, while standard engineering teams require persistent chat.

1. Create a New Policy for In-Meeting-Only Chat

New-CsTeamsMeetingPolicy -Identity "InMeetingOnlyChatPolicy" -MeetingChatEnabledType EnabledInMeetingOnly -Description "Restricts chat participation strictly to the duration of the live meeting"

2. Create a High-Security No-Chat Policy

New-CsTeamsMeetingPolicy -Identity "ConfidentialBriefingPolicy" -MeetingChatEnabledType Disabled -Description "Completely disables chat backchannels for executive briefings"

3. Assign Policy to an Individual User

Assign the custom policy to specific meeting organizers:

Grant-CsTeamsMeetingPolicy -Identity "[email protected]" -PolicyName "InMeetingOnlyChatPolicy"

4. Assign Policy in Bulk via Security Group

To enforce the chat restriction across all members of a department using Azure AD / Entra ID groups:

$groupId = (Get-AzureADGroup -SearchString "Financial Advisory Team").ObjectId
New-CsGroupPolicyAssignment -GroupId $groupId -PolicyType TeamsMeetingPolicy -PolicyName "InMeetingOnlyChatPolicy" -Rank 1

Verifying User Policy Assignment and Effective State

To confirm which meeting policy is actively applied to a specific organizer, inspect their effective policy resolution:

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

Meeting Organizer vs Attendee Permissions

Important Architectural Principle: The MeetingChatEnabledType setting is determined by the meeting organizer’s policy, not the individual attendee’s policy. If an executive with Disabled chat schedules a meeting, no participants (internal or external) will have chat access. Conversely, if an organizer with EnabledInMeetingOnly schedules a session, all attendees will find the chat box disabled once the meeting concludes.

Configuring meeting chat policies via PowerShell provides Microsoft 365 administrators with robust governance controls, mitigating data spillover risks and ensuring meeting communication adheres to organizational compliance standards.

Get the best tech tips delivered straight to your inbox.

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