When you share your screen in a Teams meeting and try to give control to a participant, the option may be grayed out or the request fails silently. This often happens when your computer is connected to a corporate VPN. The VPN can block the peer-to-peer connection that Teams uses to transfer control permissions. This article explains why the VPN interferes and provides step-by-step fixes to restore the give control feature.
Key Takeaways: Fix Teams Give Control Over VPN
- Teams admin center > Meetings > Meeting policies: Enable the “Who can give or request control” setting to allow participants to receive control.
- VPN split tunneling: Configure the VPN to exclude Teams traffic from the encrypted tunnel, so peer-to-peer connections work.
- Direct connection or web client: Use a non-VPN network or the Teams web app as a temporary workaround.
Why Teams Cannot Give Control Over a Corporate VPN
Teams uses a peer-to-peer connection for screen sharing and control. When you give control to a participant, Teams sends a permission token over that direct connection. A corporate VPN creates a tunnel that encapsulates all your network traffic. This tunnel can block the peer-to-peer path, especially if the VPN uses network address translation or strict firewall rules. As a result, the control request never reaches the other participant, or Teams disables the option entirely.
Another common cause is the Teams meeting policy. The default policy allows the presenter to give control, but an administrator may have restricted it. If the policy blocks control, the option appears grayed out regardless of your network. You must check both the VPN configuration and the policy settings.
How the VPN Interferes with Peer-to-Peer Traffic
When you are on a VPN, your computer sends all traffic through the VPN server. The server then routes it to the internet. For Teams, this means the peer-to-peer connection is no longer direct. The VPN server may not support the UDP protocol that Teams uses for real-time media. Without UDP, Teams falls back to TCP, which is slower and may not handle control signals correctly. In some cases, the VPN firewall blocks the ports Teams uses, such as 3478 through 3481 for UDP.
Meeting Policy Restrictions
Teams administrators can set a policy that controls who can give or request control. If the policy is set to “Off” or “Organizer only,” participants cannot receive control. This is independent of your VPN. You need to verify the effective policy for the user who is sharing.
Steps to Diagnose and Fix Teams Give Control Over VPN
Follow these steps in order. Each step addresses a specific cause. Stop when the issue is resolved.
- Check the Teams meeting policy
Open the Teams admin center at admin.teams.microsoft.com. Go to Meetings > Meeting policies. Select the policy assigned to the user who is sharing. Look for the setting “Who can give or request control.” Set it to “Everyone” or “Organizer and co-organizers” depending on your needs. Save the policy and wait at least 30 minutes for it to take effect. - Verify the VPN client version and configuration
Open your VPN client and check for updates. Older VPN clients may not support split tunneling. Look for a setting called “split tunnel” or “split tunneling.” Enable it if available. This allows Teams traffic to bypass the VPN tunnel. - Configure split tunneling for Teams domains
If your VPN client supports split tunneling, add the Teams domains to the exclusion list. The required domains are teams.microsoft.com, teams.microsoft.com, and skype.com. Also include office.com and sharepoint.com for related services. Consult your VPN administrator for the exact syntax. - Test without the VPN
Temporarily disconnect from the VPN and join the meeting again. Share your screen and try to give control. If it works, the VPN is the root cause. If it still fails, the issue is elsewhere, such as the policy or the participant’s client. - Use the Teams web client as a workaround
Open the meeting in a browser at teams.microsoft.com. The web client uses a different network path that may bypass the VPN issue. Share your screen and give control from the browser. This is a temporary fix but works in many cases. - Contact your VPN administrator
If split tunneling is not possible, ask your IT team to allow UDP traffic on ports 3478-3481 for Teams. Also ask them to allow the Teams IP ranges. Provide them the official Microsoft documentation for Teams network requirements.
If Teams Still Has Issues After the Main Fix
Teams Shows “Give Control” as Grayed Out
This usually means the meeting policy blocks control. Confirm the policy is set to allow everyone. Also check that the participant is not a guest. Guests may not receive control depending on the tenant settings. Ask the Teams admin to review the external access settings.
Control Request Fails but No Error Message
This indicates a network path issue. The peer-to-peer connection is not established. Try turning off the VPN for a moment and reconnecting. If that works, push your IT team to implement split tunneling. Also ensure both you and the participant have the latest Teams update.
Participant Receives Control but Cannot Interact
The participant may be on a different network that also uses a VPN. Both sides need a working peer-to-peer path. Ask the participant to disconnect their VPN or use the web client. Also check that the participant has the correct permissions in the meeting role.
New Teams Desktop vs Teams on the Web: Key Differences for Give Control
| Item | New Teams Desktop | Teams on the Web |
|---|---|---|
| Peer-to-peer support | Full UDP support for low latency | Limited to browser WebRTC, may use TCP |
| VPN behavior | Affected by VPN tunnel and firewall | Often bypasses VPN issues due to different routing |
| Give control feature | Available with proper policy | Available but may have slight delay |
| Best for | High-quality screen sharing | Quick workaround when VPN blocks desktop |
The desktop client offers the best experience when the network is clean. The web client is a reliable fallback when the VPN interferes. Use the web client for urgent meetings while your IT team fixes the VPN configuration.
You can now diagnose and fix the give control issue caused by a corporate VPN. Start by checking the meeting policy, then test split tunneling. If the problem persists, use the web client as a temporary solution. For a permanent fix, ask your IT team to enable split tunneling and allow the required UDP ports. Remember to keep Teams updated to avoid other network-related bugs.