The listed scope is Desktop and Mac, in the Worldwide (Standard Multi-Tenant) cloud. That is a planned release window, not a shipping guarantee: Microsoft’s roadmap explicitly says dates are estimates and feature information can change.
What the switchboard promises—and what it doesn’t
The announcement establishes a focused change: easier management of Teams-originating NDI sources for production software. It does not describe the interface, available controls, licensing requirements, or whether existing setup requirements will change.
The sensible interpretation is a workflow improvement, not a new broadcast engine. Until Microsoft publishes implementation details, producers should not assume higher video quality, more simultaneous feeds, isolated participant audio, or a replacement for their production application.
In short: a better control desk may be coming. The announcement does not promise a bigger studio.
Why NDI matters to Teams production
Microsoft Learn explains that NDI connects media sources over a local intranet, including between applications on the same computer. This gives the planned switchboard a specific purpose: managing the handoff between Teams and a production environment, rather than merely changing what meeting attendees see.
Teams already offers active-speaker, local-camera, individual-participant, screen-sharing, and Large Gallery NDI outputs. However, Microsoft Support says individual-user feeds share the same mixed incoming meeting audio; separate video feeds do not mean separate audio tracks.
That distinction matters when planning a production. A switchboard could make source management easier without changing what each source contains.
Prepare the existing workflow first
There are no verified setup instructions for the future switchboard yet. Organizations can nevertheless prepare using Microsoft’s documented existing Teams NDI workflow.
Administrator preparation
In Teams admin center:
- Open Meetings > Meeting policies.
- Select an existing policy or create one for the intended production users.
- Under Audio & video, enable Broadcast production with NDI and SDI hardware.
- Save the policy and ensure the intended users have the enabled policy.
Microsoft Learn recommends against enabling broadcast production globally as the most secure configuration. A targeted policy is therefore the better starting point for an organization’s production operators.
Producer preparation
Microsoft Support documents these client steps:
- Before joining a meeting, open Settings > App permissions.
- Under Production tools, download and install the NDI binaries.
- Enable the Production tools toggle; it cannot be enabled during a meeting.
- Join the meeting, then select More actions > Streaming > Broadcast over NDI.
Microsoft also says to repeat the preparation after Teams updates. Validate the intended audio and video in the receiving production application before the event.
Keep today’s constraints in the rehearsal plan
Microsoft recommends two or three NDI-out video streams per computer for stability—not as a stated hard cap. Output depends on the streams and quality received by the Teams client. Pinning important participants helps preserve their feeds; switching to Large Gallery interrupts individual feeds, while returning to Gallery restores them.
These are existing operational constraints, not confirmed specifications of the upcoming switchboard.
The takeaway: November 2026 is the planning window, and simpler source management is the promised benefit. For now, keep policy enablement, client preparation, and a realistic production rehearsal on the checklist. A cleaner switchboard would be welcome; it is not a substitute for testing the show before the audience arrives.