Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 12:24 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Rollout

Ends
30 Nov 2026
Roadmap
554931
Platforms
Desktop, Mac

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Microsoft's start date
26 May 2026
Last changed by Microsoft
22 Sep 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

Updated September 22, 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 October 2026 (previously mid-September)

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.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 12:24 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current