I'm not sure that they're not just a feature. Even if MS teams sucks compared to Slack, the MS salesman can talk to the CIO of Megacorp and say they'll add it in for half of what Slack costs. They see X million in savings and suddenly the entire organization is using MS Teams instead of Slack.
Why do you make it sound like some shady back-door deal? Our grey-beard entirely Linux using ops staff would drop Slack for MS teams at the drop of a hat to get that money back in the budget. You can only waste so much money when the entire office demands Office.
Dropbox is also one the chopping block to be replaced by OneDrive. Until someone can break hard dependency people have on Office products MS suite will always come out cheaper than Office + $other_thing.
Can confirm. Desktop Linux-using ops staff here, we're moving from dropbox to onedrive in the next ~month, and I'd switch from Slack to Teams if it didn't suffer from the same problem all MS IM products (UWP/Chromium Skype- & Lync-based alike) seem to face: intermittent failures to push notifications.
We route alerts through IM primarily, and are remote-first. I get that some folks here complain about their inability to ignore chat notifications, but there's a decent chunk of us that need to find our uninterrupted time where we can, not when we want.
> Dropbox is also one the chopping block to be replaced by OneDrive.
A few weeks ago the startup I work for started using NextCloud as a stop-gap till we get O365 and OneDrive. It is ridiculously simple for us at-least to just copy over our entire Dropbox folder to the NextCloud one.
I hear that. I wish I could deploy Nextcloud at my company. We have plenty of resources and storage. Not paying per user per month would be so so so nice.
My company is already paying for Teams as part of our O365 Installation. We won't use it, simply because of the network effect the Shared Channels have created.
We have shared channels with Integration Partners, Suppliers, Enterprise Customers... These are extremely valuable ways of communication once setup, especially with simple file-transfer thrown in, etc.
Leaving Slack would mean slamming the door in the face of these entities, something we're simply not ready to do for the cost-savings that ditching Slack would mean.
I don’t know a single enterprise client that enables external Slack users. People are far too careless with what they share in IM (like private SSH keys and IP addresses), and Slack history is a juicy target for hackers diving for secrets.
Enterprise users usually just use it for internal messaging.
If that's what's best for your company, great. For others, competing against MS Teams means that they will face an uphill battle on the sales side - to put it mildly. In terms of the cost savings aspect once MS reaches feature parity-ish, there will be significant pressure on the CIO to consider a migration away from Slack. Both of these pressures raise valid questions about the valuation and future of Slack.
Microsoft isn’t Oracle. They put Teams in the bundle and slowly break whatever they are replacing. In this case Skype.
If you’re big enough for Microsoft to care about you, you already have embedded SEs compensated based on OneDrive and Teams adoption. Your IT middle management pushes teams.
Your CIO is getting the cyber pitch based in the insecurity of your O365 implementation. The fix is to buy Azure AD or the next bundle (EMS), or maybe the E5 O365/Windows subscription.
I'm not sure that they're not just a feature. Even if MS teams sucks compared to Slack, the MS salesman can talk to the CIO of Megacorp and say they'll add it in for half of what Slack costs. They see X million in savings and suddenly the entire organization is using MS Teams instead of Slack.