Source note · Voice for remote and home workers
Teams media traffic has no URL, so VPN split-tunnel routing for Teams media must be controlled by IP subnets rather than URL- or FQDN-based rules.
Checked 2026-09-25
Teams media traffic has no URL associated with it, so control of routing for this traffic must be done using IP subnets.
- Vendor
- Microsoft
- Product
- Teams
- Subsystem
- vpn-split-tunnel
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Securing Teams media traffic for VPN split tunneling — Microsoft · tier 2 current vendor documentation · Configuration (second paragraph)
Cite this note
APA
WarmTransfer. (2026, September 25). Voice for remote and home workers: source note remote-worker-voice-teams-media-no-url. WarmTransfer. https://warmtransfer.net/knowledge/claims/remote-worker-voice-teams-media-no-url
BibTeX
@misc{warmtransfer-claim-remote-worker-voice-teams-media-no-url,
title = {Voice for remote and home workers: source note remote-worker-voice-teams-media-no-url},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/remote-worker-voice-teams-media-no-url},
note = {Source note remote-worker-voice-teams-media-no-url, checked 2026-09-25}
}