Microsoft warns that a successful Teams network-site match (which delivers emergency policies) does not confirm the client obtained an emergency address from LIS.
Checked 2026-10-01
A successful network-site match doesn't confirm that the client obtained an emergency address.
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Network sites vs LIS
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-01
- Checked
- 2026-10-01
Sources
- Configure dynamic emergency calling — Microsoft · tier 2 current vendor documentation · Configure Location Information Service > IPv6 subnet matching, Important box
Cite this note
APA
WarmTransfer. (2026, October 1). Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-teams-site-match-not-address. WarmTransfer. https://warmtransfer.net/knowledge/claims/e911-routing-failures-teams-site-match-not-address
BibTeX
@misc{warmtransfer-claim-e911-routing-failures-teams-site-match-not-address,
title = {Troubleshooting 911 calls that route with the wrong location: source note e911-routing-failures-teams-site-match-not-address},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/e911-routing-failures-teams-site-match-not-address},
note = {Source note e911-routing-failures-teams-site-match-not-address, checked 2026-10-01}
}