How to Configure Teams Meeting NDI Streaming Policies in PowerShell Using CsTeamsMeetingPolicy

Modern corporate communications, virtual conferences, and enterprise webinars frequently demand broadcast-grade visual production. While standard Microsoft Teams meetings offer adequate webcam and screen-sharing layouts for day-to-day collaboration, professional media productions require routing isolated audio and video streams (ISO feeds) into production switchers such as OBS Studio, vMix, Wirecast, or hardware TriCasters. Microsoft Teams supports this through NewTek’s Network Device Interface (NDI) and Serial Digital Interface (SDI) technology. However, because local NDI streaming broadcasts unencrypted, raw audio and video packets across the local area network, administrators must strictly govern which users can activate broadcast streaming. Using the Microsoft Teams PowerShell module, administrators can manage the AllowNDIStreaming parameter within CsTeamsMeetingPolicy to enforce secure live production governance.

Architecture of NDI Streaming in Microsoft Teams

Network Device Interface (NDI) is a royalty-free software standard developed by NewTek that enables high-definition, ultra-low-latency video and multi-channel audio transmission across standard Gigabit Ethernet networks. When NDI is active in a Teams meeting, the Teams desktop client generates individual, clean NDI output feeds for:

  • Individual Video Feeds: Each meeting participant’s camera stream is broadcast as a distinct NDI video source with embedded audio.
  • Screen Sharing Streams: Any active desktop or application presentation stream is output as a separate, dedicated high-resolution NDI source.
  • Active Speaker Feed: An automated switcher stream that dynamically follows whoever is currently speaking.
  • Large Gallery / Together Mode: Composite layout feeds suitable for secondary program monitor displays.

From a security and compliance perspective, NDI streams are uncompressed or lightly compressed video signals sent via multicast or unicast UDP/TCP across the local subnet. If activated indiscriminately, NDI can congest local network bandwidth (each 1080p stream consumes 100 to 150 Mbps) and expose confidential meeting participant feeds to anyone running an NDI receiver on the same network segment. Consequently, AllowNDIStreaming should be disabled globally and granted exclusively to vetted media production teams.

Connecting to the Microsoft Teams PowerShell Module

Managing meeting policies requires an elevated PowerShell console and credentials assigned the Teams Administrator or Global Administrator role. Begin by connecting to the tenant:

Import-Module MicrosoftTeams
Connect-MicrosoftTeams

Confirm the administrative session context by checking tenant identity:

Get-CsTenant | Select-Object DisplayName, TenantId

Auditing Existing NDI and Broadcast Streaming Policies

Before applying policy modifications, inspect the default Global (Org-wide) meeting policy to determine whether NDI streaming is permitted by default:

Get-CsTeamsMeetingPolicy -Identity Global | Select-Object Identity, AllowNDIStreaming, AllowCloudRecording, AllowScreenSharing

To inspect all defined meeting policies across your organization and audit which custom groups have broadcast streaming permissions, run:

Get-CsTeamsMeetingPolicy | Select-Object Identity, Description, AllowNDIStreaming | Format-Table -AutoSize

In standard commercial tenants, AllowNDIStreaming defaults to $false to protect network bandwidth and data privacy.

Enforcing Global Prohibition of NDI Streaming

In high-security, financial, or healthcare environments, ensuring that general business users cannot broadcast meeting audio/video feeds onto local subnets is a core security baseline. Explicitly lock down the Global policy:

Set-CsTeamsMeetingPolicy -Identity Global -AllowNDIStreaming $false

Verify that the Global policy reflects the locked configuration:

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

When configured to $false, the “Local streaming” toggle under Teams Desktop client settings is hidden and permanently greyed out for regular staff.

Creating a Scoped NDI Streaming Policy for Production Teams

To accommodate internal media communications teams, video engineers, and studio technicians who manage town halls and corporate broadcasts, create a tailored meeting policy with NDI streaming explicitly enabled:

New-CsTeamsMeetingPolicy -Identity "MediaProductionStudioPolicy" `
    -Description "Permits uncompressed NDI and SDI local broadcast streaming for live production switchers" `
    -AllowNDIStreaming $true

To assign this policy to a dedicated broadcast technician or executive producer, execute Grant-CsTeamsMeetingPolicy:

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

For organisations running enterprise audio/visual departments, map the policy dynamically across a designated Microsoft Entra ID (Azure AD) security group:

$StudioGroup = Get-AzureADGroup -SearchString "Live Event Production Staff"
New-CsGroupPolicyAssignment -GroupId $StudioGroup.ObjectId `
    -PolicyType TeamsMeetingPolicy `
    -PolicyName "MediaProductionStudioPolicy" `
    -Rank 1

Client-Side Configuration and Verification

Once the policy propagates (which may take between 15 minutes and several hours across Microsoft 365 cloud services), the assigned technician must enable the feature locally within their Teams client:

  1. Launch the Microsoft Teams desktop client on Windows or macOS.
  2. Navigate to Settings > App permissions (or Advanced in newer Teams builds).
  3. Locate the Local streaming section and toggle the switch to Enabled (this activates NDI and SDI hardware support).
  4. Join or schedule a live meeting. Click the More (…) menu on the meeting toolbar, select Local streaming, and verify that the individual attendee feeds appear as discoverable NDI sources in your local video switcher.

Network Bandwidth Considerations and Monitoring

Because each active NDI stream generates 100 to 150 Mbps of local network traffic, hosting a meeting with 5 isolated camera feeds can generate up to 750 Mbps of sustained bandwidth. Ensure that production workstations are connected via dedicated Gigabit or 10-Gigabit wired Ethernet interfaces rather than Wi-Fi.

To audit user policy assignment and verify that no unauthorized accounts hold NDI permissions, periodically run administrative compliance queries:

Get-CsUserPolicyAssignment -PolicyType TeamsMeetingPolicy |
    Where-Object { $_.PolicyName -eq "MediaProductionStudioPolicy" } |
    Select-Object UserId, PolicyName

Restricting NDI capabilities strictly to authorized production personnel prevents local network congestion while enabling broadcast-quality virtual events.

Get the best tech tips delivered straight to your inbox.

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