In enterprise training sessions, university lectures, multi-department workshops, and structured virtual conferences, meeting facilitators frequently need to divide attendees into smaller interactive working groups. Microsoft Teams enables this collaborative capability through Breakout Rooms. Facilitators can create up to 50 sub-rooms within a single parent meeting, assign attendees automatically or manually, hop between rooms, and broadcast announcements across all groups concurrently.
However, in compliance-sensitive enterprise environments, regulated financial institutions, or external client meetings, unauthorized creation of breakout rooms can bypass central supervision or compliance recording. Microsoft Teams administrators manage breakout room availability across their tenant using Meeting Policies in PowerShell. With Set-CsTeamsMeetingPolicy, administrators can control whether breakout rooms can be instantiated, restrict room management rights, and ensure corporate governance.
Understanding Breakout Rooms Controls in Teams Meeting Policies
Within Microsoft Teams meeting architecture, breakout room management is governed by the AllowBreakoutRooms parameter in CsTeamsMeetingPolicy. The policy controls several core capabilities:
- Breakout Room Instantiation: Determines whether the Breakout Rooms button and management pane appear in the Teams desktop client toolbar during active meetings.
- Meeting Organizer & Co-Organizer Privileges: When enabled, both the primary meeting organizer and designated co-organizers can create rooms, configure timers, assign participants, and close sessions.
- External & In-Tenant Scope: Determines whether meeting hosts can assign breakout rooms in meetings that host federated or guest attendees.
When AllowBreakoutRooms is set to $false, the breakout rooms icon is completely hidden from the Teams toolbar for users assigned to that policy, preventing them from creating or managing breakout rooms even if they organize the meeting.
Connecting to Microsoft Teams PowerShell
To view and update meeting policies, open an elevated PowerShell window and sign in to the Microsoft Teams management module:
# Import and connect to Teams tenant
Import-Module MicrosoftTeams
Connect-MicrosoftTeams
Verify that your session is active by retrieving the list of currently provisioned meeting policies:
Get-CsTeamsMeetingPolicy | Select-Object Identity, Description, AllowBreakoutRooms | Format-Table -AutoSize
Inspecting Current Breakout Rooms Configurations
To inspect the breakout rooms setting on the default organization-wide policy (Global), execute:
Get-CsTeamsMeetingPolicy -Identity Global | Select-Object Identity, AllowBreakoutRooms, AllowMeetNow, AllowChannelMeetingScheduling
The output displays the active boolean configuration:
Identity : Global
AllowBreakoutRooms : True
By default in most Microsoft 365 commercial tenants, AllowBreakoutRooms is set to $true. To query specific custom policies created for sensitive units or compliance groups:
Get-CsTeamsMeetingPolicy -Identity "Compliance-Strict-Policy" | Select-Object Identity, AllowBreakoutRooms
Creating a Custom Policy with Breakout Rooms Disabled
Enterprise best practice recommends leaving standard collaborative policies enabled for general staff while assigning dedicated, restricted meeting policies to audited divisions, legal teams, or executive boardrooms.
To create a new meeting policy with breakout rooms explicitly disabled, run New-CsTeamsMeetingPolicy:
New-CsTeamsMeetingPolicy -Identity "Restricted-Meetings-NoBreakout" -Description "Disables breakout room creation for compliance and legal departments" -AllowBreakoutRooms $false
Verify the newly created policy:
Get-CsTeamsMeetingPolicy -Identity "Restricted-Meetings-NoBreakout" | Format-List Identity, Description, AllowBreakoutRooms
Modifying Existing Meeting Policies with Set-CsTeamsMeetingPolicy
If you need to disable breakout rooms globally across the entire tenant or re-enable them on an existing custom policy, use Set-CsTeamsMeetingPolicy.
To disable breakout room creation org-wide across all standard users:
Set-CsTeamsMeetingPolicy -Identity Global -AllowBreakoutRooms $false
To enable breakout rooms on a specialized training or education policy:
Set-CsTeamsMeetingPolicy -Identity "Corporate-Training-Policy" -AllowBreakoutRooms $true
Confirm the updated setting:
Get-CsTeamsMeetingPolicy -Identity "Corporate-Training-Policy" | Select-Object Identity, AllowBreakoutRooms
Assigning the Breakout Rooms Policy to Target Users
After creating or updating the policy, grant it to individual employees, departments, or entire security groups.
Assigning to an Individual User
To apply the restricted policy to an individual user:
Grant-CsTeamsMeetingPolicy -Identity "[email protected]" -PolicyName "Restricted-Meetings-NoBreakout"
Confirm user policy assignment:
Get-CsUserPolicyAssignment -Identity "[email protected]" -PolicyType TeamsMeetingPolicy
Assigning to an Entra ID Security Group
To assign the policy across an entire department using Entra ID (Azure AD) security groups:
# Retrieve Entra ID group Object ID
$GroupId = (Get-AzureADGroup -SearchString "Compliance & Legal Audit").ObjectId
# Assign policy to group with priority rank
New-CsGroupPolicyAssignment -GroupId $GroupId -PolicyType TeamsMeetingPolicy -PolicyName "Restricted-Meetings-NoBreakout" -Rank 1
Validating Client Behaviour and Participant Experience
Once policies are assigned, changes replicate across Microsoft 365 cloud edge services. Allow approximately 2 to 4 hours for client policy caches to refresh.
Validate the enforcement by scheduling a test meeting as the restricted user:
- Open the Microsoft Teams desktop client on Windows or macOS.
- Join the scheduled meeting as the organizer.
- Inspect the top meeting toolbar: the Rooms icon (represented by two overlapping squares) should no longer appear.
- Verify that when joining meetings hosted by other non-restricted organizers, the user can still be assigned into breakout rooms as a participant, but cannot create or orchestrate sub-rooms independently.
For organizations utilizing compliance recording policies (CsTeamsComplianceRecordingPolicy), ensure that if breakout rooms are permitted, third-party recording bots are configured to automatically follow participants into breakout rooms to maintain complete audio and video audit logs.