Posted inMicrosoft Teams

MC1387814: Microsoft Teams Pauses RTMP-In Update for Port and Domain Requirements

3 minutesPosted inMicrosoft Teams
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
51
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ 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
The update confirms that the rollout is still paused, reducing immediate urgency but still requiring planning for new network requirements before the stated deadline. Admins must configure firewall and networking rules, coordinate with internal teams and update documentation, which adds complexity. User impact remains indirect because the change affects backend streaming capability rather than broad user experience. Current timeline gives time to prepare, but monitoring is essential as failure to act by early 2027 could disrupt RTMP-In scenarios.
70
🛡️ Admin Impact
HIGH
20
👥 User Impact
LOW
40
⚡ Urgency
MEDIUM
65
🔧 Effort
HIGH
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams will change RTMP-In network requirements. Update network settings now to avoid streaming failures after December 2026.
👥

END USERS

Event organisers may be unable to create or stream RTMP-In events if network settings are not updated.
🛡️

IT ADMINS

Update firewall to allow ports 50118-50119 and domain *.rtmpingest.mcr.teams.cloud.microsoft before the deadline.
📅

ROLLOUT TIMELINE

Timing:
Not specified

📢 Official Microsoft Message Center Announcement

(Updated) Microsoft Teams: RTMP-In port and domain changes required
Message ID: MC1387814 (Updated)

Updated July 27, 2026: We have updated the content; the release of this feature is still paused at this time. We will announce via Message center when we are ready to proceed. We apologize for any inconvenience. 

[What and Why]

Microsoft Teams is updating the port and domain requirements for Real-Time Messaging Protocol (RTMP)-In, which enables organizers to stream content into meetings, webinars, and town halls using external hardware or software encoders. This change improves reliability and scalability for Teams streaming scenarios.

[Rollout Schedule]

  • General Availability (Worldwide): We will announce via Message center when we are ready to proceed.

[Impact on Your Organization]

Who is affected

  • Admins managing Microsoft Teams meetings, webinars, and town halls
  • Event organizers who use RTMP-In with external encoders

Platforms/Services

  • Microsoft Teams (meetings, webinars, and town halls)

What will happen

  • New meetings, webinars, and town halls that use RTMP-In will require updated network access.
  • Admins must allow the required ports and domain endpoints for RTMP-In streaming.
  • Existing meetings, webinars, and town halls already configured with RTMP-In will continue to function through the end of 2026.
  • RTMP-In continues to allow organizers to stream content into Teams from external hardware or software encoders.
  • Without these updates, organizers may be unable to create or stream RTMP-In events, and newly created events may fail after December 31, 2026.

Required network endpoints:

  • Ports: 50118 and 50119 (RTMP/RTMPS)
  • Domain: *.rtmpingest.mcr.teams.cloud.microsoft

[Action Required/Recommendations]

Action required by January 31, 2027.

  • Review your organization’s firewall and network configuration.
  • Allow outbound access to:
    • Ports 50118 and 50119 (RTMP/RTMPS)
    • Domain: *.rtmpingest.mcr.teams.cloud.microsoft
  • Validate connectivity against official Microsoft 365 endpoint and firewall guidance.
  • Communicate this change to your networking and IT teams.
  • Update internal documentation if you support RTMP-In streaming scenarios.

Learn more: Manage RTMP-In for Teams meetings, webinars, and town halls | Microsoft Teams | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

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

Share This Update
Tags: