alt Hacker NewsMy org went all in on Teams over 6 years ago. Removed all PBX systems and desk phones. Pulled out Cisco phones from 20 offices. Ported all numbers to MS. By all accounts it was unremarkable to the end users, and when WFH mandates started it was seamless. Definitely a lot less IT support for configuring and troubleshooting a phone system too. There is far less downtime because Teams will ring through to your cell phone if the office internet is down or your laptop is off. That was not possible when the Cisco routers and CallManager in the office were running the DIDs and local extensions
Replies
The hot takes are from people that have haven't touched Teams in 6 years.
Like everything Microsoft it was shit for the first few years, they slowly sorted it out, and now it's fine. Most non-tech-bro businesses successfully run the majority of their comms through it.
The main problem now is that it works fine, and the project managers on Teams need to create work for themselves, so just mess around with stuff that wasn't broken.
It was, in fact, even with existing Microsoft products (Lync/Skype for Business). It was even possible if you had paid for those features for UCM from Cisco. Teams was simply the cheaper option (although they tried to keep charging my org Lync prices, and we had to threaten to uproot MS products and go to Cisco before they gave us the new pricing).
> That was not possible when the Cisco routers and CallManager in the office were running the DIDs and local extensions
You could do it with other software hosted outside the office though. There are definitely options here.