Source note · Teams voice routing policies and dial plans
If a user's assigned number includes an extension, the inbound called number must include that extension for Reverse Number Lookup to match. An unmatched call fails, or goes to unassigned number routing if that is configured.
Checked 2026-09-24
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- inbound-rnl
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Checked
- 2026-09-24
Sources
- Microsoft Teams Dial plans for phone call routing — Microsoft · tier 2 current vendor documentation · section 'Number lookup for inbound calls', paragraphs following the +14255551212 example
Cite this note
APA
WarmTransfer. (2026, September 24). Teams voice routing policies and dial plans: source note teams-voice-routing-rnl-extension-must-match. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-voice-routing-rnl-extension-must-match
BibTeX
@misc{warmtransfer-claim-teams-voice-routing-rnl-extension-must-match,
title = {Teams voice routing policies and dial plans: source note teams-voice-routing-rnl-extension-must-match},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-voice-routing-rnl-extension-must-match},
note = {Source note teams-voice-routing-rnl-extension-must-match, checked 2026-09-24}
}