Modifications to Microsoft Systems
This article provides a listing of the elements within various Microsoft systems that may be modified to support Direct Routing and the related Apps and processes. This is organized by specific Microsoft admin interfaces, though many of these elements could also be viewed through Azure Active Directory.
Note that the permissions obtained to make these changes are documented here.
Microsoft 365 Admin Center
There are two areas within M365 admin center where items are added: Domains and Users. This is primarily during Direct Routing setup, but also during the configuration of CallApp.
Direct Routing
Setting up Direct Routing generates a unique domain along with an associated user within that domain. Each Direct Route (or Secondary Route) creates a new instance of these objects.
CallApp Configuration
During configuration of the CallApp service, a Resource Account user will be created in the Tenant's default domain and assigned a Teams Phone Resource Account license. This can be viewed in the M365 admin center and will appear as shown here.
M365 Admin Summary
This table summarizes the items created in the M365 Admin Center.
Object | Example |
---|---|
Domain | cust123.sbc.connecttoteams.com |
User | DirectRouting User [email protected] |
User | CallApp Service |
Teams Admin Center
Items are added or modified in several areas in the Teams Admin Center (TAC):
Direct Routing
Voice Routes: Voice Routes are added for each Gateway or secondary Gateway.
PSTN Usages: A PSTN Usage is added for each primary direct route.
Voice Routing Policies: A Voice Routing Policy is added for each direct route
Dial Plans: A Dial Plan and Normalization Rule will be added.
Calling Policy: When PBX Music-on-Hold is enabled, the Global calling policy will be modified to disable Teams Music-On-Hold
Teams Apps: Custom apps are added if they are created for the tenant and installed in the catalog by the Global Admin via the Enterprise Portal.
Users
Phone numbers are assigned.
Voice Routing Policy is assigned.
Dial Plan policy is assigned.
Call Settings for Voicemail handling may be updated.
Voice Routes, Voice Routing Policy, PSTN Usages
Items are added in the locations noted in the image above:
SBCs - items are not added here. Typically, the listing in the SBC tab on the Direct Routing page will be blank.
Voice Routes - Voice Routes are added for every Direct Route. The naming convention is the same for every tenant: TM_PBX_<gateway>_Unrestricted. A suffix of SECONDARY is added for the optional secondary route that is set up for failover. The secondary route will be assigned the PSTN Usage corresponding to the primary route, but the secondary route will have a lower precedence (higher priority number). The "SBC Enrolled" is actually a derived trunk named after the Direct Routing domain created for that Direct Route. NOTE: these "SBC" enrollments are ONLY configurable via PowerShell -- attempting to manipulate these Voice Routes via the TAC will break your calling.
PSTN Usage records - These are added and the names will match the primary voice route.
Voice Routing Policies - The Voice Routing polices reference the PSTN Usages, and the names of the policies match the names of the associated PSTN Usage (and also the primary Voice Route).
Dial Plans, Calling Policy
A Dial Plan will be created in the Dial Plan list, and a Normalization Rule will be created in that Dial Plan. The name of the Dial Plan, the name of the Rule, and the actual Rule regular expression are customizable by the Reseller. See Dial Plan Customization for defaults and more information.
The Global Calling Policy may be updated in the event that the Enterprise is configured to have PBX Music On Hold. In this case, the setting in the call policy would be changed to off (to disable Teams MOH).
Teams Apps
Any Teams Apps that are deployed into the App catalog will be listed in the Teams Apps > Manage Apps page. All the apps created through the system will be "custom apps" -- the easiest way to find them is to enable the "Custom App" column in the table in TAC, and then sort by that column. The screenshot above has been sorted in this way to show all the custom apps at the top.
Note that the names, logos and (in some cases) publisher and other settings may be different based on branding choices at the Reseller level.
Clicking on these apps will provide access to more detail about the App, including a link to the Permissions associated with the App.
Users
PBX and Trunk Users are updated to have
a Direct Routing phone number in Teams and to have EnterpriseVoiceEnabled set to true internally via PowerShell.
their Voice Routing Policy set to the VR policy corresponding to the gateway selected when building the user in the portal
Dial Plan policy set to the custom dial plan (when the "Assign Default Dial Plan" selection is made when building the user)
Teams "If unanswered" setting set to "Do nothing" (if the Disable Teams Voicemail is checked when building the user).
Teams Admin Center Summary
This table summarizes the modifications made to TAC items.