How to Configure Teams Shared Display Mode Policies in PowerShell Using CsTeamsSharedDisplayModePolicy

Modern hybrid workplaces increasingly feature Bring Your Own Device (BYOD) meeting rooms, huddle pods, and executive focus booths. In these spaces, rather than deploying dedicated Microsoft Teams Rooms consoles with separate resource accounts, employees connect their personal laptops directly to shared displays, TVs, and peripheral audio-video gear. However, traditional screen mirroring presents substantial privacy and usability issues: incoming personal chat notifications appear on the communal screen, participant rosters are hidden, and meeting controls are awkward to navigate.

To deliver a professional meeting room experience in BYOD environments, Microsoft introduced Teams Shared Display Mode. When a user connects their laptop to a shared monitor or peripheral dock, Teams prompts the user to enter Shared Display Mode. The shared screen displays a clean, distraction-free meeting stage with video gallery, meeting roster, and content sharing, while the user’s personal laptop screen acts as a private companion controller. Using the CsTeamsSharedDisplayModePolicy cmdlets in the Microsoft Teams PowerShell module, administrators can centrally configure, govern, and deploy shared display mode capabilities across their organization.

Understanding Teams Shared Display Mode Architecture

Teams Shared Display Mode operates by splitting the Teams meeting interface between the user’s primary device and the connected external display:

  • Shared Room Display: Displays incoming video feeds, shared presentations, captions, and the active speaker spotlight. Personal desktop icons, browser windows, and pop-up chat notifications are completely excluded from the public display.
  • Private Companion Screen (Laptop): Retains private meeting controls, allowing the user to view personal chat messages, take notes, manage participant mute states, and monitor upcoming calendar appointments in private.
  • Proximity and Peripheral Detection: Teams detects when the laptop is connected to an external display or Bluetooth audio puck in a registered room workspace, automatically suggesting Shared Display Mode.

Connecting to the Microsoft Teams PowerShell Module

To configure shared display mode policies, launch an elevated PowerShell terminal and connect to your Microsoft 365 tenant:

# Import the Teams PowerShell module and authenticate
Import-Module MicrosoftTeams
Connect-MicrosoftTeams

Querying Existing Shared Display Mode Policies

To inspect all configured shared display mode policies across your tenant, execute Get-CsTeamsSharedDisplayModePolicy:

# Retrieve all configured shared display mode policies
Get-CsTeamsSharedDisplayModePolicy

To view the output in a clean, structured table:

# Format policy properties into a readable table
Get-CsTeamsSharedDisplayModePolicy | Format-Table Identity, Description, Enabled

In standard tenants, the Global policy applies to all users unless an explicit custom policy is assigned.

Creating Custom Shared Display Mode Policies

To control how shared display features roll out across different departments, administrators can create custom policies using New-CsTeamsSharedDisplayModePolicy:

# Create a custom policy enabling shared display mode for field consultants
New-CsTeamsSharedDisplayModePolicy `
    -Identity "BYOD-Consultants-Enabled" `
    -Description "Enables Teams Shared Display Mode for mobile consultant laptops in BYOD rooms" `
    -Enabled $true

Conversely, for high-security environments, financial trading rooms, or government facilities where communal screen casting from personal laptops must be strictly prohibited:

# Create a restrictive policy disabling shared display mode
New-CsTeamsSharedDisplayModePolicy `
    -Identity "Restricted-NoSharedDisplay" `
    -Description "Prohibits Shared Display Mode casting to prevent accidental information leakage" `
    -Enabled $false

Assigning Policies to Users and Security Groups

Once custom policies are defined, assign them to individual users using Grant-CsTeamsSharedDisplayModePolicy:

# Assign policy to an individual user
Grant-CsTeamsSharedDisplayModePolicy `
    -Identity "[email protected]" `
    -PolicyName "BYOD-Consultants-Enabled"

To deploy the policy across an entire department or branch office using an Entra ID (Azure AD) security group:

# Assign policy across an Entra ID security group
Grant-CsTeamsSharedDisplayModePolicy `
    -Group "18451a30-54cd-4e2a-9812-abcdef123789" `
    -PolicyName "BYOD-Consultants-Enabled" `
    -Rank 1

To verify the effective policy applied to a specific user:

# Check effective policy on a user account
Get-CsOnlineUser -Identity "[email protected]" | Select-Object UserPrincipalName, TeamsSharedDisplayModePolicy

Updating Global Tenant-Wide Policy Settings

If your organization decides to enable Shared Display Mode tenant-wide for all employees by default, update the Global policy instance using Set-CsTeamsSharedDisplayModePolicy:

# Enable Shared Display Mode globally across the entire tenant
Set-CsTeamsSharedDisplayModePolicy `
    -Identity "Global" `
    -Enabled $true

Removing Obsolete Shared Display Mode Policies

When pilot testing concludes and features are merged into the tenant-wide Global policy, remove custom policy records using Remove-CsTeamsSharedDisplayModePolicy:

# Delete an obsolete custom policy
Remove-CsTeamsSharedDisplayModePolicy -Identity "BYOD-Consultants-Enabled" -Confirm:$false

Using CsTeamsSharedDisplayModePolicy allows enterprise IT and AV administrators to modernize BYOD meeting spaces, safeguard personal privacy on shared screens, and deliver an intuitive, professional meeting experience across Microsoft Teams.

Get the best tech tips delivered straight to your inbox.

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