For many organizations I have spoken with over the past few years, I have noticed 2 specific trends when it comes to SharePoint:
1. “We’re really into the idea of the cloud, how do we do it?”
2. “The cloud is Evil, we’re never doing it, quit bringing it up.”
And actually, the more I think about it, #2 probably came from me, as well, about five years ago. But the fact of the matter is – especially when it concerns Web-based applications – that the cloud is really where you’re going to get the most value for your organization for these applications. I’m a big believer that this goes double for SharePoint.
Why Is The Cloud So Good For SharePoint?
About a year ago, Microsoft got themselves in a bit of hot water for essentially saying that they didn’t see any future in the on-premise edition of SharePoint, and there was some indication that they would make SharePoint 2016 the last version that would be deployed for On-Premises. This caused many virtual riots; some Admins tore up their autographed Bill Gates photographs, and there were many tears shed by Ninjacats riding Unicorns*.
Fast forward a year, and Microsoft completely reversed that course and has wholeheartedly committed to continuing supporting new versions of On-Premise SharePoint in perpetuity. But as I have seen so far with what they have shown for SharePoint 2016, “wholeheartedly” may be a bit optimistic. I don’t want to say that On-Premise is underwhelming, but…no actually, that’s exactly correct. It is.
However, if you look at the development of SharePoint on Office 365, it’s a completely different story. Microsoft has truly committed itself to expand and refining the functionality of SharePoint in Office 365. But they are doing this by building new and exciting products on top of SharePoint; Delve, Next-Gen Portals, Power BI and even Yammer are all products that can be woven into SharePoint quickly and easily through Office 365.
Can’t We Just Do Hybrid If We Want All That Functionality?
Sure you can, and that has really been the one big feature that has really been promoted with SharePoint 2016. But does it really make sense to create a fully redundant, high performance, SharePoint 2016 farm and then add on an entire Office 365 tenant? For very large organizations that have established 2013 Farms, and petabytes of content, I would say yes. But what if you’re a small to mid-size organization, with very limited support resources?
SharePoint is a very powerful platform that can perform a LOT of different functions. I have seen many large organizations struggle to support the platform with decent sized IT staffs. Saddling your company with two SharePoint environments may be a terrible choice if you want to see real value from SharePoint over the long term.
Okay, But What If I Don’t Care About All That Extra Functionality, And Still Just Want To Do On-Prem?
This is just my opinion, but I think one of the big reasons Microsoft really pushed away from wanting to continue SharePoint on-premises is due to the bad rap the platform has gotten over the years – and I’ve seen my fair share of bad SharePoint implementations. In my earlier years, I probably helped contribute to some of those bad implementations, as well. I think what Office 365 can help your organization with is saving your SharePoint from bad practices, bad implementations and horribly bad upgrade activities.
Let’s face it: There is one absolute with having an On-Prem SharePoint environment, and it’s the fact that you WILL have to upgrade it eventually, and it most likely WILL be a painful process the longer between versions you wait. Right now, companies who are still on SharePoint 2003 are nodding their heads in agreement. I see Microsoft making a very good effort at trying to take as much of the pain away as possible, and just letting the users keep collaborating.
But What About Security? What About The Hackers?
Microsoft spends millions on intrusion detection, has large teams of people monitoring real-time connections and uses advanced Machine Learning models to detect possible threats.
*NOTE: None of these things “may” have happened…
This article was originally published on LinkedIn.