Last month at Microsoft Ignite we introduced a new vision for intelligent communications, which includes Microsoft Teams becoming the primary client for communication and collaboration in Office 365....
Updated Jan 26, 2021
Version 15.0
Blog Post
2 MIN READ
Roadmap for Skype for Business capabilities coming to Microsoft Teams now available
I found this https://docs.microsoft.com/en-us/microsoftteams/audio-conferencingand in it there is a statement "...Teams does not support 3rd-party Audio Conferencing Providers (ACPs)."
Here is my position:
I am upset with the tactic which forces us to use Microsoft Audio Conferencing for Teams PSTN dial in capabilities . With Skype for Business, I could integrate a 3rd party audio conference provider. All my existing conferencing numbers would work. The Global Network Architecture created for us could remain in place. No workflow changes to end/users.
In Teams, I will be forced to use the MS Audio Conferencing service if I want that PSTN dial in capability. This means new numbers at minimum. And gaps in Toll-Free or Local coverage.
Additionally, I fear the "all eggs in one basket" scenario that will put us in . For a global enterprise in 180 locations, we value diversity, in this case carrier diversity. One could conclude that if the Office365 service is unavailable, a large enterprise cannot conduct business. At least with separate carrier paths, either Teams failing or My 3rd party failing is not a lights out issue. Both failing simultaneously is unlikely.
I encourage you to voice your opinion on this with Microsoft. It is bad for us.