Microsoft Teams Tenant Dial Plan

Requirements for essential Tenant Dial Plan considerations:
  • The default, country-specific set of dialling rules were not enough to meet user requirements. Such as,
    • Speed dial
    • Internal Extension Dial
  • Retaining user dial patterns when users are migrated from on-premises deployments to online.

What is Tenant Dial Plan?

  • Dial plans for Skype for Business Online or Teams tenants.
  • Enable users to dial numbers the way they used to (no need to dial regional or area codes).
  • Each dial plan uses a set of normalization rules, similar to what we used for on-premises deployments.
  • Applies to all Microsoft Phone System deployment options (Microsoft Calling for Office 365, hybrid via CCE and via pool) as well as dial out for Cloud PSTN Conferencing.
  • No change in routing/usages.
  • Only 25 normalization rules per dial plan is a limitation.

Dial Plan Types

  • Service dial plans are the default and applied to users based on location, and they can’t be changed
  • Tenant dial plans can be customized
    • Tenant-Global – the dial plan applies to all users in the tenant
    • Tenant-User – the dial plan applies only to specific users

Dial plan types

Dial plan types

Dial Plan Hierarchy

  • Dial plan scope (or hierarchy) works differently when using tenant dial plans.
  • On-premises Skype for Business or Lync dial plans were based on a hierarchy of Global, Site, Pool & User in which we would apply the most specific or lowest plan in the hierarchy.
  • For tenant dial plans, we actually merge the various dial plans together that are applied to a user, as shown below.

Dial Plan Hierarchy

Dial plan hierarchy

Planning Steps

  • Decide if additional rules are required
    • The cmdlet Get-CsEffectiveTenantDialPlan for a user will list the default rules
  • Determine which dial plan type is required.
    • Tenant user scoped dial plans are required if users have different local dialling requirements.
    • Tenant global dial plans can be used if all users in the tenant share the same requirements.
  • Identify valid number patterns for each dial plan.
    • Only the number of patterns that are not defined in the service level country dial plans are required
    • If you have an existing on-premises deployment you can use that as the basis for determining which rules you need or recreate the on-premises dial plans as tenant dial plans.
    • Make sure that the normalization rules defined there are actually required.
    • If you are migrating from a traditional Phone System, then collect the existing rules and create the corresponding dial plan(s) and normalization rule(s).
  • Maintain consistency of dial plan names.
    • Develop an organization-wide scheme for naming dial plans and normalization rules.


Popular posts from this blog

5 Great Reasons To Connect Solar Power

Microsoft Mesh is the platform that Microsoft is creating for a virtual office in augmented reality

Crypto Wallet