Media Bypass vs. No Bypass in Microsoft Teams

When deploying Microsoft Teams Phone with Direct Routing, one of the most important architectural choices is deciding between media bypass vs no bypass in Microsoft Teams. This decision determines how RTP media flows between the Teams client, Microsoft cloud, and the Session Border Controller (SBC). It impacts call quality, latency, troubleshooting complexity, firewall rules, and the overall reliability of PSTN calling.

In this in‑depth guide, we will break down how Media Bypass and No Bypass work, their advantages and disadvantages, and which option is best for your network topology, user behavior, and SBC environment. By the end, you’ll clearly understand how to design a stable and efficient Teams Direct Routing infrastructure.

What Is Media Bypass in Microsoft Teams?

Media Bypass allows the Teams client to send RTP media directly to an SBC instead of routing media through Microsoft’s Transport Relays. While signaling always flows through the Microsoft cloud, the audio stream bypasses the relay and flows directly between the client and the SBC.

How Media Bypass Works

• The Teams client establishes signaling through Microsoft 365 cloud services.
• Once signaling is complete, the client sends RTP directly to the SBC.
• Symmetric RTP and reachable SBC media IPs are required.
• Firewall rules must allow direct client-to-SBC communication.

This architecture reduces hops and latency, but it requires stable and predictable client‑to‑SBC network paths.

What Is No Bypass in Microsoft Teams?

No Bypass (the default behavior) means the Teams client does not communicate directly with the SBC for media. Instead, all audio flows through Microsoft’s global media relay network.

How No Bypass Works

• The Teams client sends RTP to a Microsoft Transport Relay using ICE/TURN.
• Microsoft relays audio to the SBC.
• Signaling still flows cloud → SBC.
• User devices never interact directly with the SBC.

This model provides the most reliability for remote, roaming, and hybrid users, because clients only need to reach Microsoft 365 services.

Pros and Cons of Media Bypass

✔️ Advantages of Media Bypass

• Lower Latency — Direct media path eliminates relay hops and reduces round‑trip time.
• Improved Call Quality — Fewer intermediate hops mean less chance of jitter and packet loss.
• Reduced Bandwidth Usage — Media does not travel through Microsoft relays or corporate internet breakout.
• Optimized for On‑premises Users — Best for locations where users and SBCs are on the same LAN or WAN.
• Less dependency on TURN/Relay traffic — Fewer interactions with Microsoft media services.

❌ Disadvantages of Media Bypass

• More Firewall Complexity — Clients must reach SBC media IPs directly.
• Requires Symmetric RTP on SBCs; misconfiguration causes one‑way audio.
• Issues with VPN Users — Tunnel policies often break bypass due to NAT or hair‑pinning.
• Not ideal for roaming or mobile devices that change networks frequently.
• Harder to troubleshoot when organizations have multiple subnets, NAT layers, or split‑tunnel configurations.

Pros and Cons of No Bypass

✔️ Advantages of No Bypass

• Most Reliable for Remote/Hybrid Work — Only Microsoft 365 endpoints need to be reachable.
• Simplest Firewall Setup — No need for SBC reachability from clients.
• Consistent Media Path across devices, networks, and geographies.
• Better for cloud‑hosted SBCs and NATed environments.
• Ideal for BYOD and mobile devices.

❌ Disadvantages of No Bypass

• Potentially Higher Latency — Extra hop through Microsoft relay.
• Higher Bandwidth Usage — More external traffic for RTP.
• Relay Region Mismatch may cause performance issues if geo‑location changes.
• Not optimal for site‑to‑site WAN calls where SBC and user are close together.

Media Bypass vs No Bypass: Architecture Comparison

Media Flow Differences

• Media Bypass: Teams Client → SBC
• No Bypass: Teams Client → Microsoft Relay → SBC

Signaling Flow (same for both)

• Teams Client → Microsoft Cloud → SBC

Impact on Call Quality

Media Bypass Call Quality Benefits

• Reduced latency due to direct path.
• Better jitter performance.
• Stable media for on‑premises networks.

No Bypass Call Quality Considerations

• Relay region may introduce 20–80ms extra latency.
• High internet load may affect relay performance.
• Relay guarantees connectivity even in NAT‑heavy networks.

Which Option Should You Choose?

Choose Media Bypass If:

• Users are inside corporate offices.
• The SBC is inside the same LAN/WAN as clients.
• You want the lowest latency possible.
• Your firewall and NAT policies are clean and predictable.

Choose No Bypass If:

• Your workforce is hybrid or remote.
• You use split‑tunnel VPNs or heavy NAT.
• Your SBC is cloud‑hosted in Azure or data centers.
• You want fewer firewall rules and easier supportability.

Media Bypass Common Issues

• One‑way audio due to NAT or firewall pinholes.
• SBC public IP unreachable from specific user subnets.
• Incorrect ICE candidates processed by Teams client.
• VPN hair‑pinning causing broken media path.

No Bypass Common Issues

• High latency between relay region and SBC region.
• Users in remote geos connecting to far relay endpoints.
• Network congestion on WAN leading to degraded call quality.

Internal Linking Suggestions (Add these on your site)

• Direct Routing: End‑to‑End SBC Configuration for Microsoft Teams
• One‑Way Audio in PSTN to Microsoft Teams Calls: Root Cause Analysis
• How to Configure Microsoft Teams Firewall and Network Requirements
• Teams Call Analytics vs CQD: Full Troubleshooting Guide

Conclusion

Choosing between media bypass vs no bypass in Microsoft Teams depends entirely on your network layout, SBC availability, and user behavior. Media Bypass offers low latency and superior performance for on‑premises networks, while No Bypass delivers the most consistency and reliability for hybrid and remote users. By understanding the strengths and limitations of each model, you can design a Direct Routing environment that delivers excellent call quality, strong stability, and easier troubleshooting across your organization.