Source note · Teams emergency calling and location policies
Where a cloud proxy rewrites client source IPs, trusted-IP and subnet lookups fail, so on-premises clients fall back to switch/port or BSSID matches if configured, and otherwise to user-confirmed or registered addresses, which in the US means screened rather than direct-to-PSAP calls.
inferred · Checked 2026-09-24
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- network settings
- Deployment
- multi-tenant
- Region
- us
- Release range
- current as of 2026-09-24
- Status
- inferred
- Checked
- 2026-09-24
Sources
- Configure dynamic emergency calling — Microsoft · tier 2 current vendor documentation · Configure network settings > Note and Important callout; combined with emergency-calling-dispatchable-location classification table
Cite this note
APA
WarmTransfer. (2026, September 24). Teams emergency calling and location policies: source note teams-emergency-calling-inf-proxy-degrades-location. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-emergency-calling-inf-proxy-degrades-location
BibTeX
@misc{warmtransfer-claim-teams-emergency-calling-inf-proxy-degrades-location,
title = {Teams emergency calling and location policies: source note teams-emergency-calling-inf-proxy-degrades-location},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-emergency-calling-inf-proxy-degrades-location},
note = {Source note teams-emergency-calling-inf-proxy-degrades-location, checked 2026-09-24}
}