1. Training disclaimer This is a point of time view
This session was recorded in April 2017
The features and functionality describe are current as of this date
O365 is ongoing innovation
We innovate on a constant basis
New features and functionality are added frequently
Always refer to latest trainings
Go to for the latest version of this training
Go to for more trainings

2. Skype Academy presents: Tenant Dial Plans
Skype for Business
6/24/2018 7:34 PM
Skype Academy presents: Tenant Dial Plans
Training from April 2017
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. garth
has a bad day
Training from April 2017

4. Garth has dialed 5551234 which has incorrectly normalized to +15551234
Garth is sad, he wishes that he could dial numbers like he used to
We need to make Garth happy again
Training from April 2017

5. Tenant Dial Plans – Key Learnings
Support for tenant based dial plans
Create custom normalization rules
Applicable to a specific user or to the entire tenant
Training from April 2017

6. Agenda Plan Deliver Operate Summary and resources
Skype for Business
6/24/2018 7:34 PM
Agenda
Plan
What are tenant dial plans?
Why did we implement tenant dial plans?
Understanding tenant dial plan scope
Determine existing dial plan configuration
Deliver
Create, manage and assign tenant dial plans
Discuss automation of importing on-premises data
Operate
Analyzing Logs
Summary and resources
Training from April 2017
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

7. Plan
Training from April 2017

8. What are tenant dial plans?
Why
To make Garth Fort happy again
A single country specific set of dialing rules were not enough
User dial patterns had to change when users were migrated from on-premises deployments to online
Strong customer feedback indicated that this was dramatically impacting the end user experience
What
Dial plans for Skype for Business Online tenants
Enables users to dial numbers the way they are used to
User don’t need to dial regional or area codes
Each plan uses a set of normalization rules, similar to what we used for on-premises deployments
Applies to Cloud PBX for online and hybrid users (CCE and OPCH) as well as dial out for Cloud PSTN Conferencing
No change in routing / usages
Limit of 25 normalization rules per dial plan
Training from April 2017

9. Online dial plans - Before
Prior to the introduction of tenant dial plans each user was assigned a very basic set of normalization rules
Here is an example of the US region
Training from April 2017

10. Dial Plan Types Three different types of dial plans
Service dial plans have always existed and been applied to users, these can’t be changed
Tenant dial plans are new and 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
Service
Tenant
Tenant - Global
Service Country
Tenant - User
Training from April 2017

11. Dial Plan Hierarchy
Dial plan scope (or hierarchy) works different when using tenant dial plans
On-premises 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
No tenant global dial plan and no tenant user dial plan assigned
Tenant global dial plan but no tenant user dial plan assigned
Tenant user dial plan assigned
Service Country
Service Country
Service Country
Tenant - Global
Tenant - User
Training from April 2017

12. Planning Steps Step 1 – Decide if additional rules are required
The cmdlet Get-CsEffectiveTenantDialPlan for a user will show the default rules
Step 2 – Determine which dial plan type is required
Tenant user scoped dial plans are needed if users have different local dialing requirements
Tenant global dial plans can be used if all users in the tenant share the same requirements
Step 3 – Identify valid number patterns for each plan
Only the number patterns that are not defined in the service level country dial plans are required
Step 4 – Maintain consistency in dial plan names
Develop an organization-wide scheme for naming dial plans
Training from April 2017

13. Methods to Identify valid number patterns (Step 3)
Existing On-premises deployment
If you have an existing on-premises deployment you can use that as the basis for determining which rules you need
Make sure that the normalization rules defined there are actually required
Migration from traditional telephone system
If you are migrating from a traditional telephone system then use the rules collected during project envisioning phases
Training from April 2017

14. Caveats Cmdlets only for now Support for External Access Prefix (EAP)
Current plan of record is to enable a UI in the future
Phone normalization rules are not some that change frequently
Support for External Access Prefix (EAP)
Is currently not available with Tenant Dial Plans, but will be enabled soon
Not currently supported with certified IP phones
The current certification spec did not include support for tenant dial plans as this feature did not exist at the time the spec was written
The current plan of record is to update the spec and fully support this feature on our certified phones in the future
Training from April 2017

15. Deliver
Training from April 2017

16. Working with tenant dial plans
Outcome
Cmdlet Syntax
Create a new dial plan and add normalization rules
New-CsTenantDialPlan -Identity RedmondDialPlan -Description "Dial Plan for Redmond" -SimpleName "Dial-Plan-for-Redmond”
$nr1=New-CsVoiceNormalizationRule -Parent Global -Description “7 digit local dialing” -Pattern ‘^(\d{7})$’ -Translation ‘+1425$1’ -Name NR1 -IsInternalExtension $false –InMemory
Set-CsTenantDialPlan -Identity RedmondDialPlan
Grant a dial plan to a specific user
Grant-CsTenantDialPlan -Identity -PolicyName RedmondDialPlan
View the normalization rules associated with a tenant dial plan
(Get-CsTenantDialPlan RedmondDialPlan).NormalizationRules
Determine the effective dial plan for a specific user
Get-CsEffectiveTenantDialPlan -Identity
Test the outcome a specific user dialing a number
Get-CsEffectiveTenantDialPlan -Identity | Test-CsEffectiveTenantDialPlan -DialedNumber
Allow hybrid users to consume tenant dial plan
Set-CsTenantHybridConfiguration -UseOnPremDialPlan $false
Training from April 2017

17. In action Training from April 2017
Garth has dialed which has incorrectly normalized to
New-CsTenantDialPlan -Identity RedmondDialPlan -Description "Dial Plan for Redmond" -ExternalAccessPrefix 9 -SimpleName "Dial-Plan-for-Redmond”
$nr1=New-CsVoiceNormalizationRule -Parent Global -Description “Organization extension dialing” -Pattern ‘^(\d{7})$’ -Translation ‘+1425$1’ -Name NR1 -IsInternalExtension $false –InMemory
Set-CsTenantDialPlan -Identity RedmondDialPlan
Grant-CsTenantDialPlan -Identity -PolicyName RedmondDialPlan
Our SOF partner has suggested the following changes
Training from April 2017

18. Now when Garth dials 5551234 it correctly normalizes to +14255551234
In action
Now when Garth dials it correctly normalizes to
Garth is happy again
Training from April 2017

19. Changing tenant dial plans
Outcome
Cmdlet Syntax
Delete a tenant dial plan
The –force option forces the removal of the dialplan
If this dial plan is assigned to a user you will be prompted to accept the deletion if you don’t use -force
Remove-CsTenantDialPlan -Identity RedmondDialPlan –force
Remove a normalization rule from a tenant dial plan
$nr1=New-CsVoiceNormalizationRule -Parent Global –name NR1 –InMemory
Set-CsTenantDialPlan -Identity RedmondDialPlan
View the normalization rules associated with a tenant dial plan
(Get-CsTenantDialPlan RedmondDialPlan).NormalizationRules
Training from April 2017

20. Capturing your on-premises dial plans
It is possible to capture your on-premises dial plans and create an input CSV to use for bulk creating the tenant dial plans in their tenant
Training from April 2017

21. Automate on-premises import
Use the data captured from your on-premises dial plans
This sample script shows how you could leverge that data to automatically import your rules into a tenant dial plan
Import-Csv c:\temp\tdpnormrules.csv | % {
$nr = $null
$nr = New-CsVoiceNormalizationRule -Identity ($_.DialPlan + "/" + $_.Description) -Description $_.Description -Pattern $_.Pattern -Translation $_.Translation -IsInternalExtension ([System.Convert]::ToBoolean([int]$_.IsInternalExtension)) -InMemory
Set-CsTenantDialPlan -Identity $_.DialPlan }
Training from April 2017

22. Operate
Training from April 2017

23. Analyzing Logs Run the following cmdlet Examine the output
Get-CsEffectiveTenantDialPlan -Identity | select identity
Examine the output
Identity
b822df5f-f234-41cc-b3c4-4614ade4db7b_RedmondDialPlan_US
Read client log
Use Snooper
Open the most recent .uccapi log file on client PC in %localappdata%\Microsoft\Office\16.0\Lync\Tracing
Search for “LocationProfileDescription”
Training from April 2017

24. Analyzing Logs You will see many messages that match your search
Notice the Name value before was the user’s region
The Name value after is the effective policy name
Before
After
Training from April 2017

25. Summary and resources
Training from April 2017

26. Additional Information
Planning
Creating and Managing
Training from April 2017

27. Tenant Dial Plans – Key Learnings
Support for tenant based dial plans
Create custom normalization rules
Applicable to a specific user or to the entire tenant
Training from April 2017

28. Resource Skype Operations Framework SOF: Tenant Dial Plans training
SOF: Tenant Dial Plans training
Skype Academy
Skype Preview
Training from April 2017

29. Community & blog Community SOF & Academy blog Training from April 2017
Discuss, ask questions and provide feedback
People from Microsoft and your peers are in the forums
SOF & Academy blog
Stay up to date with SOF and trainings
Training from April 2017