Source record · tier 2 current vendor documentation

Microsoft Teams Dial plans for phone call routing

Publisher: Microsoft
URL: https://learn.microsoft.com/en-us/microsoftteams/what-are-dial-plans
Published: 2025-08-11
Updated: unknown
Accessed: 2026-09-23
HTTP status: 200
License: Microsoft Learn terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

Microsoft says the usual reason for a custom Teams dial plan is to support non-E.164 dialling such as extensions or abbreviated national dialling, and that Direct Routing or extension dialling needs extra call-routing configuration. in context
When normalising a dialled number, Teams gives user dial plan rules precedence over the tenant (Global) dial plan, and tenant rules precedence over the Microsoft-managed service dial plan; a user cannot hold a tenant and a user dial plan at the same time. in context
For Direct Routing, a user's number can be 3 to 38 digits without common symbols, whereas Calling Plan and Operator Connect numbers are E.164. in context
To keep extension dialling across Unified CM and Teams during wave migration, the Teams side probably needs a dial plan rule that expands short extensions to E.164 and a voice route whose pattern covers the numbers still on Unified CM, pointing at the SBC; Unified CM needs the mirror routing toward the SBC for numbers that have moved. inferred in context
A tenant can have at most 1,000 tenant dial plans. in context
Teams routes inbound calls by Reverse Number Lookup on the called number; if the called number does not exactly match a number assigned to a user or resource account, the call fails or follows unassigned number routing if that is configured. in context
A Teams number can carry an extension of 1 to 12 digits after the ';ext=' delimiter; if one is assigned, the inbound called number must include it for lookup to match, and Microsoft says extensions are only needed when users share a main number without a Shared Calling policy. in context
The Teams client normalizes numbers for all outbound calls using the user's effective dial plan, including calls placed from call history or telephone-number links. in context
For Teams Calling Plan, Operator Connect and Teams Phone Mobile, dial plans and voice routing policies are preconfigured at the service level, and no administration is needed. in context
Microsoft's planning guidance says a custom Teams dial plan is typically needed to support non-E.164 dialing such as extensions or abbreviated national dialing. Only patterns missing from the service country dial plan need to be defined. in context
In Microsoft Teams, a dial plan is a named set of one or more number-string translation rules, called normalization rules, that translate called number strings into alternate formats. in context
A Teams phone number can carry an extension of 1 to 12 digits appended with the case-insensitive ';ext=' delimiter. in context
A Teams tenant can have at most 1,000 tenant dial plans. in context
Teams dial plans translate numbers entered in various user formats into a standardized format, typically E.164, for matching against authorized resources and for routing. in context
If a Teams user is assigned a number with an extension, an inbound called number must include that extension for reverse number lookup to match. Otherwise the call fails or follows unassigned number routing if configured. in context
For Teams reverse number lookup, Calling Plan and Operator Connect numbers are E.164 values, while Direct Routing numbers can be between 3 and 38 digits without common symbols. in context
When Teams normalizes a dialed number, user dial plan rules take precedence over tenant (Global) rules, and tenant rules take precedence over service dial plan rules. in context
Teams automatically assigns each user the service dial plan that matches the usage location assigned to that user. in context
A Teams user always has the service dial plan plus either the tenant dial plan or a user dial plan, never both the tenant and a user dial plan at once. in context
Teams has three dial plan scopes: a service dial plan managed by Microsoft that admins cannot configure, a configurable tenant dial plan named Global, and configurable user dial plans. in context
The Teams client applies the user's effective dial plan to every outbound call, including calls placed from call history and from telephone-number links. in context
A Teams dial plan is a named set of normalization rules that translate user-dialed strings into a standardized format, typically E.164, for authorization matching and routing. in context
Teams has three dial plan scopes: a Microsoft-managed, non-configurable service dial plan for each country or region, a tenant (Global) dial plan, and user dial plans. in context
When Teams processes a dialed number, user dial plan normalization rules take precedence over the tenant Global dial plan, and the tenant dial plan takes precedence over the service country dial plan it is merged with. in context
A Teams number can carry an extension of 1 to 12 digits after a case-insensitive ';ext=' delimiter; if an extension is assigned, the inbound dialed number must include it for RNL to match. in context
A Teams tenant can have at most 1,000 tenant dial plans. in context
For Teams Reverse Number Lookup, a Calling Plan or Operator Connect number is stored in E.164 format, whereas a Direct Routing number is stored as 3 to 38 digits without common symbols. in context
For Calling Plan, Operator Connect and Teams Phone Mobile, dial plans and voice routing policies are preconfigured at the service level, and no admin configuration is needed. in context
The Teams client normalizes the number for every outbound call using the user's effective dial plan, including calls placed from call history or from telephone-number links. in context
A Teams dial plan is a named set of one or more normalization rules that translate user-dialed number strings into a standardized format, typically E.164, for authorization matching and routing. in context
Teams has three dial plan scopes: the service dial plan (Microsoft-managed and not configurable), the tenant dial plan (the Global org default) and user dial plans, and the last two are admin-configurable. in context
When normalization rules are processed, rules in a user dial plan take precedence over the tenant (Global) dial plan, which in turn takes precedence over the service dial plan. in context
With Direct Routing, admins must configure call routing themselves by creating voice routes and assigning voice routing policies to users. Route-level number translation rules are optional and handle SBC interoperability. in context
A user's effective dial plan merges the service dial plan for their country or region with the assigned tenant or user dial plan. If the Global dial plan is unmodified and no user dial plan is assigned, the effective dial plan is the service dial plan alone. in context
A tenant can have at most 1,000 tenant dial plans. in context
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. in context
For Reverse Number Lookup, a Direct Routing number value is 3 to 38 digits without common symbols, while Calling Plan and Operator Connect numbers are E.164. An optional extension is appended with ';ext=' (case insensitive) and is 1 to 12 digits. in context
Microsoft defines a service dial plan for each country or region where Teams Phone is available, and assigns each user the service dial plan that matches the user's usage location. in context
Admins can set the skip-RNL option on a resource account's number assignment with Set-CsPhoneNumberAssignment -ReverseNumberLookup. Internal calls to that number then bypass Reverse Number Lookup and route externally through the PSTN. in context
A user always has the service dial plan plus either the tenant (Global) dial plan or a user dial plan, and never both a tenant and a user dial plan at once. in context

Cite this source record

APA

WarmTransfer. (2025, August 11). Microsoft Teams Dial plans for phone call routing. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-dial-plans-routing-overview

BibTeX

@misc{warmtransfer-ms-learn-dial-plans-routing-overview,
  title  = {Microsoft Teams Dial plans for phone call routing},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-dial-plans-routing-overview},
  note   = {Microsoft, accessed 2026-09-23}
}