MC1323270: Microsoft Teams Adds Secure Reliable Transport Support for Town Halls and Live Events

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
40
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Teams AdminsTenant AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Timeline shifted for general availability, but rollout is already in progress. Impact centres on Teams event producers and admins managing external encoder workflows. Admins may need to verify firewall ports, encoder SRT compatibility and adjust meeting policies if restricting inputs. End users joining events see no change, so user impact remains minimal.
50
🛡️ Admin Impact
10
👥 User Impact
45
Urgency
40
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams live events and town halls now support Secure Reliable Transport (SRT) for streaming, giving producers a more reliable option with backup streams.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Check encoder SRT support, ensure port and domain access, update event documentation, and inform teams about the new backup stream option.
📅

ROLLOUT TIMELINE

Rolling out:
In progress

📢 Official Microsoft Message Center Announcement


(Updated) Microsoft Teams: Secure Reliable Transport (SRT) support for Teams meetings and events
Message ID: MC1323270 (Updated)

Updated September 3, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

Microsoft Teams town halls and live events will soon support Secure Reliable Transport (SRT), a secure and resilient video streaming protocol designed to deliver high‑quality, low‑latency video over the public internet. SRT will be available alongside Real‑Time Messaging Protocol (RTMP), the existing inbound streaming protocol commonly used with external encoders. Adding SRT provides event organizers with improved reliability and flexibility, including support for backup streams with automatic failover, to help ensure smoother delivery for high‑visibility broadcast events without increasing setup complexity.

This message applies to Teams for Windows desktop and Teams for Mac desktop and is associated with Roadmap ID 554931.

[When this will happen:]

  1. Targeted Release: Rollout begins in early June 2026 and is expected to complete by mid-June 2026
  2. General Availability (Worldwide, GCC): Rollout begins in late June 2026 (previously mid-June) and is expected to complete by mid-September 2026 (previously end of August)

[How this affects your organization:]

Who is affected:

  1. Organizations that host Microsoft Teams town halls or live events using external encoders
  2. Event producers and administrators responsible for configuring broadcast streams

What will happen:

  1. Organizers can use SRT as an alternative to RTMP for inbound streaming
  2. Events can be configured with a primary and backup SRT stream with automatic failover
  3. Existing RTMP workflows remain supported and unchanged
  4. The feature is available by default; no admin policy changes are required
  5. No impact to users attending events

[What you can do to prepare:].

  1. Review encoder capabilities to confirm SRT support
  2. Ensure you have access to port 49891 and the domain *.rtmpingest.mcr.teams.cloud.microsoft.
  3. Update internal event‑production documentation to include SRT as a supported option
  4. Inform event production teams that a backup stream with automatic failover is now available for Teams town halls

We’ve introduced an additional policy control for SRT-In in Teams Events. To enable users to access and use SRT-In, IT admins must explicitly allow the “SRT” setting in the AllowedStreamingMediaInput parameter within CsTeamsMeetingPolicy.


Learn more: Manage RTMP-In for Teams meetings, webinars, and town halls – Microsoft Teams | Microsoft Learn (will be updated before Targeted Release begins)

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1323270] Archive
Tooltip: View earlier revisions of this post

Share This Update