Zoom and Teams Not Working Over VPN: How to Restore Video Calls in 2026

If Zoom and Teams don't work over a VPN, the problem isn't always the service itself or a "bad VPN." Video calls rely on different network scenarios than regular websites: UDP, WebRTC, routing, DNS, latency, packet loss and app policies all matter. Below is a safe, practical checklist for Windows, macOS, Android, iPhone and home routers — without any dubious workarounds.

This guide is useful if Zoom is stuck connecting forever, Teams keeps showing "reconnecting," your voice cuts out for others, screen sharing lags or the call works fine without a VPN but breaks the moment you turn it on. For a stable everyday connection you can start with FoliVPN, and then tune routing so calls don't conflict with your other apps.

Why Video Calls Break Specifically With a VPN

A regular website is usually opened over HTTPS: a request goes out, a response comes back, the browser waits. A video call works differently. Audio, video and screen sharing have to travel almost in real time. If a packet arrives late, you can't "wait it out" without a noticeable pause. That's why for Zoom, Microsoft Teams, Google Meet, browser-based WebRTC calls and corporate webinars, not just raw megabits but also path stability are critical.

In its Microsoft 365 documentation, Microsoft explicitly recommends VPN split tunneling for key cloud scenarios, including Teams: some traffic goes directly to Microsoft 365 instead of through the overloaded corporate tunnel. In a separate article on Teams, Microsoft adds an important point: Teams media traffic isn't tied to URLs, so it must be managed by routes and IP subnets, not just by domain exceptions. This explains a common situation: "we allowed the Teams domain, but audio still goes through the VPN and stutters."

There's also the everyday side. Home Wi‑Fi may have a weak signal, public networks may use a captive portal or filtering, and mobile internet may have an unstable route and carrier-level restrictions. In Russia in 2026, DNS and DPI restrictions on popular platforms and messengers add to this; TechRadar describes the trend of increasing blocks on YouTube, Telegram and WhatsApp via DNS/DPI. For Zoom and Teams this doesn't mean automatic blocking, but the overall environment has become less predictable: one service opens, another freezes, and a third only works in the browser.

Quick Diagnosis in 10 Minutes

Start with a simple test, not by reinstalling everything in sight. The goal is to figure out where the chain breaks: the app, the VPN, Wi‑Fi, DNS, the device or a specific server.

Step 1. Compare Three Modes

Run the same short test three times: 1) without a VPN, 2) with the VPN on the nearest server, 3) with the VPN on a different protocol or server. You don't need to discuss anything confidential during the test — an empty meeting with the camera on and a window shared is enough.

If everything is perfect without a VPN but bad with any server, the issue is in the tunnel, protocol or routing. If it's bad even without a VPN, blame Wi‑Fi, the device, the app or the ISP. If one VPN server is bad and another is fine, choose a stable route rather than "the farthest country for the sake of speed."

Step 2. Check UDP and WebRTC Without Risky Experiments

Video calling often uses UDP because it's faster for real time. In its article on WebRTC, Digital Samba explains: UDP offers low latency but doesn't guarantee packet delivery; TCP is more reliable but can add latency due to retransmissions. For a call this leads to a simple conclusion: "lots of megabits" doesn't equal "a good conversation."

If the app lets you choose a connection mode, or if your VPN client supports several protocols, try a different option. Don't disable your system's security entirely and don't open suspicious ports "to the whole internet." On a home network, it's usually enough to change the VPN protocol and server and check whether the router is throttling UDP too aggressively. On a corporate network, such changes should be made by the administrator.

Teams Over VPN: Where the Error Usually Hides

For Microsoft Teams, the main trap is thinking domain exceptions are enough. According to Microsoft, Teams media traffic has no URL, so media routing must rely on Optimize IP subnets and a correct routing table. HTTPS signaling traffic is less sensitive to latency, but audio, video and screen sharing need a shorter path.

If this is a personal computer, check: is Teams up to date, is an old VPN profile active, are a system proxy and a VPN running at the same time, is an antivirus web filter interfering. If it's a work laptop, don't change corporate policies on your own. The right ticket for IT sounds like: "Teams opens, but media traffic during calls goes through the VPN and I'm getting packet loss/latency. Could you check Microsoft 365 split tunneling and the Optimize routes for Teams?"

More on Windows networking issues is covered in our breakdown of VPN not working on Windows 11. And if websites open but native apps stay silent, the companion article VPN works in the browser but not in apps will help.

Zoom Over VPN: What to Check Without Panicking

Zoom can break in a similar way: your account web page opens but the meeting won't connect, or quality drops sharply. Zoom's public support materials include separate firewall/proxy and Zoom Rooms settings — a clear sign that the problem is often in the network path, not the account. For a home user, work from simple to complex.

First, update Zoom, restart the VPN and pick the nearest location. Next, check that a VPN, system proxy, Private DNS/Secure DNS and a browser proxy extension aren't all active at once. If Zoom doesn't work in the app but works better in the browser, compare camera/microphone permissions, network permissions and per-app filtering. If, on the contrary, browser Zoom is worse, check extensions and browser WebRTC policies.

Don't go hunting for "secret ports" on random forums and blindly opening everything. On a corporate network, give the administrator the precise symptom: which network, which VPN, which app version, what changes when the VPN is off, and whether the issue affects only audio/video or also sign-in.

Phone, Tablet and Router: Separate Nuances

On Android, Google documents the standard path to VPN settings and Always-on VPN mode. For video calls, two things matter: don't enable a mode that blocks all traffic on the slightest VPN hiccup, and don't let the call app "fall asleep" due to battery saving. If Teams or Zoom drops after a couple of minutes, check power-saving settings for the call app itself and for the VPN client.

On iPhone and iPad, Apple supports VPN profiles, On Demand and per-app VPN in managed scenarios. For an ordinary user this means: if the profile was installed via corporate MDM management, don't remove it at random. Better check whether the call works on another network, whether a conflicting Private Relay/proxy mode is off, and whether a second VPN app is installed.

On a router, the issue often disguises itself as "a slow VPN." In reality, a weak home router may not handle encryption and simultaneous video calls from multiple devices. If the VPN is enabled "for the whole house," try temporarily taking the call laptop out of the VPN route, or, the other way around, enabling the VPN only for specific services. For a home network, the article VPN on an ASUS router is handy — the device-selection logic is similar for other routers too.

Stable Video Call Over VPN Checklist

• Pick the nearest stable VPN server, not the most "exotic" region.
• Close torrents, cloud sync, game updates and large downloads.
• Test the call without video: if audio is sta