How to Configure Teams Meeting Presenter Role Policies in PowerShell Using Set-CsTeamsMeetingPolicy

In Microsoft Teams meetings, attendees assigned the Presenter role possess extensive administrative authority during the session—including the ability to share desktop screens, take control of shared PowerPoint presentations, admit or deny participants from the lobby, mute other attendees, and remove participants from the call. When organizations permit every attendee to join meetings as a presenter by default, corporate presentations and online educational classes become vulnerable to accidental disruptions and unauthorized screen takeover. Microsoft 365 administrators can enforce governance over default presenter permissions using the Microsoft Teams PowerShell module. This article explains how to inspect, configure, and assign default presenter role policies across an organization using Set-CsTeamsMeetingPolicy.

Understanding Default Presenter Roles in Teams Meeting Policies

When an organizer creates a Microsoft Teams meeting, the session enforces default participant roles regulated by the DesignatedPresenterRoleMode parameter within CsTeamsMeetingPolicy. This setting defines who receives presenter privileges automatically upon joining the meeting:

• Everyone: All participants—including anonymous guests, external federated partners, and internal staff—join the meeting as full presenters with complete screen-sharing and participant moderation rights.
• EveryoneInCompany: Only authenticated users within your Microsoft 365 tenant join as presenters. External guests and anonymous participants join as attendees with restricted controls.
• OrganizerOnlyUserOverride: Only the meeting organizer joins with presenter privileges. All other participants—both internal colleagues and external guests—join as standard attendees. The organizer retains the flexibility to manually promote specific participants to presenters during the call or beforehand in Meeting Options.

Restricting default presenter privileges to OrganizerOnlyUserOverride or EveryoneInCompany is essential in academic institutions to prevent students from muting instructors or hijacking shared screens, and in corporate enterprises hosting confidential multi-party webinars.

Connecting to the Microsoft Teams PowerShell Module

To inspect and modify meeting policies, open an elevated PowerShell window and establish an administrative session with your Microsoft 365 tenant:

Connect-MicrosoftTeams

Sign in using an account assigned the Teams Administrator or Global Administrator role.

Auditing Current Presenter Role Policy Configurations

Before implementing policy adjustments, examine the current presenter role mode configured across your organization. Query the default tenant-wide Global policy:

Get-CsTeamsMeetingPolicy -Identity Global | Select-Object Identity, Description, DesignatedPresenterRoleMode

To review the presenter role configuration across all custom meeting policies in your tenant, execute:

Get-CsTeamsMeetingPolicy | Select-Object Identity, DesignatedPresenterRoleMode | Format-Table -AutoSize

If DesignatedPresenterRoleMode is set to Everyone, any attendee joining a meeting organized by your users receives uninhibited presenter permissions.

Configuring Default Presenter Roles Globally

To establish a secure baseline where external guests cannot present unless explicitly granted permission by the meeting organizer, configure the Global policy to EveryoneInCompany:

Set-CsTeamsMeetingPolicy -Identity Global -DesignatedPresenterRoleMode "EveryoneInCompany"

In highly controlled corporate or government environments where only meeting organizers should hold presenter rights by default, enforce strict organizer isolation:

Set-CsTeamsMeetingPolicy -Identity Global -DesignatedPresenterRoleMode "OrganizerOnlyUserOverride"

Under this configuration, meeting attendees cannot share screens, mute others, or admit people from the lobby unless the meeting organizer explicitly elevates their role.

Creating and Assigning Custom Presenter Policies

Rather than enforcing a single global policy, most organizations deploy tiered meeting policies tailored to specific organizational units. For example, in an educational setting, faculty members require standard collaborative settings, whereas students must never host meetings with open presenter rights.

To create a restricted presenter policy for students, run:

New-CsTeamsMeetingPolicy -Identity "Restricted-Student-Meetings" -Description "Enforces Organizer-only presenter mode to prevent classroom disruptions" -DesignatedPresenterRoleMode "OrganizerOnlyUserOverride"

To assign this policy to an individual user, execute Grant-CsTeamsMeetingPolicy:

Grant-CsTeamsMeetingPolicy -Identity "[email protected]" -PolicyName "Restricted-Student-Meetings"

To assign the policy dynamically across an entire Entra ID (Azure AD) security group containing thousands of student accounts, use New-CsGroupPolicyAssignment:

$GroupId = (Get-MgGroup -Filter "DisplayName eq 'All Enrolled Students'").Id
New-CsGroupPolicyAssignment -GroupId $GroupId -PolicyType TeamsMeetingPolicy -PolicyName "Restricted-Student-Meetings" -Rank 1

Verifying Policy Assignments and Meeting Behavior

To confirm which meeting policy is actively applied to a specific user account, query the user policy assignment table:

Get-CsUserPolicyAssignment -Identity "[email protected]" | Where-Object { $_.PolicyType -eq "TeamsMeetingPolicy" }

Policy updates propagate to Teams desktop, web, and mobile clients within 2 to 4 hours. Once applied, new meetings organized by covered users will automatically configure the “Who can present?” setting to match your administrative policy, preventing unexpected attendee disruptions and securing corporate video collaboration.