


By entering a number into the Test textbox and pressing the Test Number button, the tool will highlight all of the rules in the Dial Plan that match in blue. So I wrote a custom testing engine into the tool providing this feature.

If the rule you are setting has a name that matches an existing rule, then the existing rule will be edited.

Create/Edit and Remove Tenant Dial Plan policies using the New., Edit.Note: the Skype for Business Online PowerShell module needs to be installed on the PC that you are connecting from. Log into O365 using the Connect SfBO button in the top left of the tool.This time, in order to ensure that I came up with the most imaginative name possible for the tool, I trekked into the deepest jungles of Peru on a vision quest where after drinking several litres of Ayahuasca came up with the name “Teams Tenant Dial Plan Tool”. So to try and avoid this pain, I decided to make a sister tool to my Direct Routing Tool that will allow for simple configuration and editing of these Tenant Dial Plans. The configuration of these are done using the Skype for Business Online module and bunch of pretty complicated PowerShell that really shouldn’t be inflicted on a regular human being. The number normalisation in O365 is done by the Tenant Dial Plan policies, which contain normalisation rules. As a result, prior to getting to the E.164 based routing rules we need to do some work to ensure that the numbers dialed have been converted into the right format. This step in the process is very important because nearly all users are not going to dial phone numbers in E.164 format. This tool, whilst allowing you to configure all your PSTN Gateways and Routing, did not allow you to configure the normalisation of numbers that users dial prior to being routed. Its name is the imaginative Microsoft Teams Direct Routing Tool. I recently released a tool for configuring Direct Routing within an Office 365 tenant.
