In the first article of this three part series I went though the basic configuration needed to enable end users with a Microsoft Calling Plan.

In this second video I run through some of the policy settings that can be used to customise the end user experience. I also show how to administer Reporting Labels, which allows the admin to build a logical mapping of the company’s sites to IP subnets in the cloud. This is really handy for troubleshooting and enhances the information presented within the Microsoft Teams Call Analytics tool.

Microsoft Teams policies can be applied at the organisational level via the default Global Policy or at an end user level using Custom Policies. Teams also support an Admin concept know as Policy Packages, which allows you to apply a suite (or a package) of polices to specific users. The idea is to reduce admin overhead. More recently Teams has introduce the ability to apply policies to Groups, which provides yet another administrative approach to deploying policies. Is this a topic worth creating a specific post about? Anyway, my advice is to adopt the KISS approach whenever possible.

In part 3 of this series I’ll cover an example configuration for a Tenant Auto Attendant / IVR and a couple of Call Queues (often referred to as Hunt Groups).