Posted inMicrosoft Teams

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

4 minutesPosted inMicrosoft Teams
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
38
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 AdminsMicrosoft 365 AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The update changes rollout dates for adding SRT support to Teams meetings and town halls. Admins may need to review encoder compatibility, verify required ports, and update documentation, but the feature is on by default and RTMP remains supported. End users are unaffected as the change is operational for event production teams only.
50
🛡️ Admin Impact
HIGH
10
👥 User Impact
LOW
40
⚡ Urgency
MEDIUM
40
🔧 Effort
MEDIUM
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams town halls and live events now support SRT for streaming, offering better reliability with backup failover for external encoders.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Check encoder support for SRT, allow port 49891, update documentation, and enable the SRT setting if needed.
📅

ROLLOUT TIMELINE

Rolling out:
Ends August 2026

📢 Official Microsoft Message Center Announcement

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

Updated August 5, 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:]

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

[How this affects your organization:]

Who is affected:

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

What will happen:

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

[What you can do to prepare:].

  • Review encoder capabilities to confirm SRT support
  • Ensure you have access to port 49891 and the domain *.rtmpingest.mcr.teams.cloud.microsoft.
  • Update internal event‑production documentation to include SRT as a supported option
  • 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
Tags: