Teams Phone System deployment options ● No customization MS Calling ● Quick to deploy ● No integration into other voice systems ● Part of licensing ● Expensive Plans ● Self service (or through partner) ● New carrier relationship ● Number Portability* ● Not globally available ● Quick to deploy ● Requires carrier API and software development ● Choice of carriers limited to Tier 1’s ● Requires Integration into OSS / BSS ● Flexible commercial terms ● Requires carrier to release control to the MS Operator Should be: Application stack s Connect ● Self service provisioning ● Most of the should’s are not a reality today. e ● Partner Deployed or Customer Deployed v ● Immediate service activation ● Customer self management not possible l ● Flexibility in voice configuration ● Integration to other platforms not possible (Call ● Choice of customisable plans centre, PBX) ct So ● Meet desired outcomes of the customer Requires: ● Flexible in design and configuration ● Planning and design nne ● Support for countries outside of MS and OC ● Technical resources o Direct plans ● Infrastructure C ● Integration with legacy and alternative voice ● Customer tenancy access a Routing platforms (call centers, PBX) ● Management requires PowerShell r ● Bring your own choice of carrier outside of ● Monitoring and the known MS list ● Threshold of users before viability due to the Au ● Management within the O365 environment prohibitive cost of implementation. ● Deployment time of weeks.