How to Use Microsoft Teams with VPN Split Tunneling?

Microsoft Teams and VPN connection challenges

Why does my Microsoft Teams audio keep cutting out when I’m connected to our company VPN? Many remote workers experience degraded call quality, slow file sharing, and connection drops when using Microsoft Teams through traditional VPN connections. The root cause often lies in how VPN traffic routing affects real-time communication applications like Teams, which require low latency and high bandwidth for optimal performance. Check our Teams sound problems guide for audio troubleshooting.

VPN split tunneling setup for Teams performance

Traditional VPN configurations route all network traffic through corporate servers, creating bottlenecks that severely impact Microsoft Teams performance. When Teams traffic passes through VPN tunnels, users experience delayed audio, pixelated video, and frequent disconnections during critical business meetings. This scenario becomes particularly problematic for organizations with distributed teams relying on consistent communication quality. Learn to test Teams connection performance to verify the improvements.

We will use Windows 10 built-in VPN client alongside popular enterprise VPN solutions to demonstrate split tunneling configuration for Microsoft Teams. The workflow covers identifying Teams endpoints, configuring routing exceptions, and validating performance improvements while preserving security policies for sensitive corporate data.

Teams split VPN configuration process

Begin by identifying your current VPN solution and gathering the necessary Microsoft Teams service endpoints that require split tunneling configuration. Microsoft maintains a comprehensive list of Teams service URLs and IP ranges that should bypass VPN routing to ensure optimal performance and connectivity.

• Access the Microsoft 365 IP Address and URL web service at https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges to download the current Teams endpoints list in JSON format for your region.
• Open Windows PowerShell as administrator and execute the following command to retrieve Teams-specific endpoints: Invoke-RestMethod -Uri "https://endpoints.office.com/endpoints/worldwide?clientrequestid=$(New-Guid)" | Where-Object {$_.serviceArea -eq "Teams"} to filter Microsoft Teams traffic destinations.
• Document the IP ranges and fully qualified domain names returned by the PowerShell command, as these addresses will need explicit split tunneling rules in your VPN client configuration settings.
• Navigate to your VPN client settings panel and locate the split tunneling or selective routing configuration section, which may be labeled differently depending on your VPN provider but typically appears under advanced network settings.

VPN split tunneling Windows 10 network configuration

Configure Windows 10 network routing tables to complement your VPN split tunneling setup and ensure Microsoft Teams traffic follows the most efficient network path. This configuration works in conjunction with VPN client settings to create comprehensive traffic routing policies.

• Open Windows Settings and navigate to Network & Internet > VPN, then select your configured VPN connection and click Advanced Options to access detailed connection settings and routing preferences.
• Enable the “Use VPN only for apps that need it” option if available, which provides application-specific routing control that can be configured to exclude Microsoft Teams from VPN tunneling automatically.
• Access the Windows Route command prompt by opening Command Prompt as administrator and use route print to display current routing table entries and identify conflicts with Teams traffic routing.
• Create persistent route exceptions for Teams endpoints using the route add command with the following syntax: route add [Teams IP range] mask [subnet mask] [local gateway IP] -p to ensure Teams traffic uses local internet connection.

VPN split tunneling Microsoft Teams endpoint optimization

Fine-tune your split tunneling configuration by implementing specific routing rules for Microsoft Teams media traffic, which includes audio, video, screen sharing, and file transfer endpoints that require direct internet connectivity for optimal performance.

• Configure your VPN client to exclude Teams media relay endpoints by adding the IP ranges 52.112.0.0/14, 52.120.0.0/14, and 52.238.119.141/32 to the split tunneling bypass list for improved call quality.
• Set up DNS resolution bypass for Teams domains including teams.microsoft.com, *.teams.microsoft.com, and *.skype.com to ensure proper service discovery and connection establishment outside the VPN tunnel.
• Implement Quality of Service (QoS) policies on your local network interface by accessing Windows Network Adapter settings and enabling QoS packet scheduler for the network adapter used for Teams traffic.
• Test the configuration by initiating a Teams video call while connected to VPN and using network monitoring tools like Wireshark or built-in Windows Resource Monitor to verify Teams traffic bypasses the VPN tunnel successfully.

Expert Tip: Always maintain a backup of your original VPN and network routing configuration before implementing split tunneling changes, as incorrect routing rules can disrupt both VPN connectivity and general internet access.

VPN for Microsoft Teams troubleshooting

Address common configuration challenges that arise when implementing VPN split tunneling for Microsoft Teams, including connection conflicts, performance issues, and security policy complications that may prevent successful deployment.

• Teams connections may fail to establish when VPN client software overrides Windows routing tables, requiring manual route priority adjustment using the route change command with lower metric values for Teams endpoints.
• Audio and video quality degradation can persist even with split tunneling enabled if your VPN client continues to route DNS queries through the corporate tunnel, necessitating manual DNS server configuration to use public resolvers like 8.8.8.8.
• Corporate firewall policies may block direct internet access for Teams endpoints, resulting in connection timeouts that require collaboration with network administrators to create firewall exceptions for Teams traffic on corporate network infrastructure.
• Some enterprise VPN solutions automatically revert split tunneling settings after software updates or policy refreshes, making it essential to document configuration steps and implement automated scripts to restore proper Teams routing settings consistently.