MC1387814: Microsoft Teams Pauses RTMP-In Port and Domain Requirement Changes

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
Microsoft has paused the release of the RTMP-In port and domain change with no new date provided, reducing immediate urgency but leaving prior admin work partially relevant. Admins still need to track this for future readiness as firewall updates and validation will eventually be mandatory. Current user impact is minimal since existing streams continue working through 2026, but future changes will affect event workflows once resumed.
55
🛡️ Admin Impact
20
👥 User Impact
30
Urgency
50
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams RTMP-In streaming will need new ports and domains. Apply the changes early or new events might fail once rollout resumes.
👥

END USERS

Organisers may not be able to create or stream RTMP-In events if network changes are missing.
🛡️

IT ADMINS

Check firewall rules, allow ports 50118/50119 and domain *.rtmpingest.mcr.teams.cloud.microsoft, and update internal docs.
📅

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 17, 2026: We have paused release of this feature 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 mid-July 2026.

Required network endpoints:

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

[Action Required/Recommendations]

Action required by mid-July 2026.

  • 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

Latest Posts

Pass It On
Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply