Salesforce Signs Definitive Agreement to Acquire Slack

Re:Salesforce Signs Definitive Agreement to Acquire Slack by homarp on Tuesday December 01, 2020 @04:38PM (#25270290)

First, you start with Office 365, then you put some stuff on One Drive, you add a little list in SharePoint online, then you use Teams to access all that. You move to Azure AD.

And then you want to automate or do some nice charts, and there is Power platform just around the corner...

and then you find yourself limited so you go Azure Functions... and then start one VM on Azure...

[ Parent | on HN ]

Re:Salesforce Signs Definitive Agreement to Acquire Slack by syshum on Tuesday December 01, 2020 @08:00PM (#25272110)

The jump from Power Platform to Azure Functions and a VM is likely not to be the same people

Power Platform is for "power users" to be able to "no code" things, this is targeted (MS Claims) as non-IT Users, as is the Rest of the office/Microsoft 365 stack

Azure (including Azure AD) however is targeted at IT Staff, dev's,sysadmins, etc. There is a clear line in how the tools are marketed, deployed, licensed and utilized

[ Parent | on HN ]

Re:Salesforce Signs Definitive Agreement to Acquire Slack by freetanga on Wednesday December 02, 2020 @02:04AM (#25273916)

Next after that is running VDIs on either a small Citrix farm on Azure or as Desktop as a Service, since AD, SSO, 2FA ,Productivity tools and user file storage is there.

After that, you already have some firewalling and VPNs in place so adding the odd server is just a step away.

Adding dedicated lines and firewalls and rules and all bella and whistles with all four big players (AMZ, IBM, MSFT, GOOG) plus 2 ISPs adds cost fast, so you typically pick 2. MSFTbis already there for O365 so yeah, they have a head start

[ Parent | on HN ]