- Must meet minimum Microsoft licensing requirements (E1/E3/ ( 365 License with Teams ) +Teams phone system License or E5)
- Add free Microsoft Teams Phone Resource Account for your Call Queues ( CQ ) and Auto Attendants ( AA )
- Create Vocus Teams Trunk
- Add temps Number to Vocus ( then to Teams ) for Testing and Call Queue Setup
- Add Resource accounts and then Numbers to Resource accounts ( These will then be applied to CQ and AA )
- Add Microsoft Teams Phone Resource Account Licenses to the new Resource accounts
- Good to use standard naming conventions RA
- Configure all AA and CQ
- Good to use standard naming conventions AA and CQ
- Set up Out of Hours Call Plan
- Book Number Ports
- Make sure all users have setup teams and are using it.
- User Training Booked?
- Voicemail Requirments?
- Who will update the Holidays?
- Outbound numbers and Call ID is done via Vocus Portal ( Vocus Customer Portal , View As )
- Call diverts can be done in Teams and Vocus
- International Calls needed, Default Blocked in Vocus
- Fax to Email to replace any Fax Services
- http://blog.schertz.name/2020/04/common-area-phones-in-microsoft-teams/
- http://blog.schertz.name/2019/11/managing-microsoft-teams-phone-policies/
- Licenses: Each user need a Teams calling License and a License to Use Teams. You will need “Microsoft 365 Phone System – Virtual User” for each Queue and Auto Attendant
- Vocus Teams Trunk : Create SIP & MS Teams trunks in VHV
- Pilot number for testing and call queue setup \ Assign temporary DIDs in VHV
- Book number ports with your carrier , this can take 1 Month. Port Contact Person is the engineer (1800 and 1300 numbers should NOT be ported, these numbers will stay with the current carrier. )
Call flow setup steps
PSTN number (service number) -> Resource Account -> Auto Assistant -> Call Queue
Notes:
- Service number is assigned to a resource group
- The resource group is then assigned to the AA
- CQ doesn’t need to have a phone number assigned, just need to have a resource group assigned to it
Teams Devices
There are /very/ strict requirements around what conditional access and compliance policies you can configure when you have a teams hardware device such as a Yealink phone.
If you have any policies that implement a feature in the “not supported” list, you must go through and exclude your teams devices from these. The recommended approach is device based filtering and excluding devices similar to
device.manufacturer -contains “yealink”
There is a semi reasonable blog/video on this below but it doesn’t cover all caveats and some of the intune configuration required.
This probably shouldn’t apply to your require MFA for admins conditional access policy.
Troubleshooting
Reporting
Loading...