When I told people I was writing a blog about SharePoint, I got a lot of interesting responses. As the title of this document might suggest, most responses were firmly in the negative. Here are some examples:
You get the idea.
While this sounds heavy-handed, this policy can be the only thing standing between you and an expensive data breach. One way to enforce this policy is through the use of a modern intranet.
In today’s post, we’re going to look at some of the best preparatory practices for migrating to SharePoint 2016 to help ensure your move to the latest version of the platform is a success.
As most of the SharePoint world may have heard by now; SharePoint 2016 is available as of May 4th, 2016 for purchase commercially; via MSDN; and through software assurance and volume licensing agreements you may have established with Microsoft. As tends to be the cycle over the past decade, this means many of us will be scrambling to understand what SharePoint 2016 offers; and to begin the upgrade "pitch" to your stakeholders to upgrade from your current version of SharePoint to the latest/greatest iteration of the platform.
CRM & SharePoint Integration
If you are familiar with the very powerful interface which allows a CRM (Customer Relationship Management) user to attach seamlessly documents to a given entity (account, contact, opportunity, etc.) using the CRM/SharePoint integration, you may also be aware of a potentially dangerous gap in the security model.
I have found that the out-of-box integration is well designed, intuitive, and easy to use. I can take any document and with a few clicks of the mouse, associate it to a CRM entity while saving it in a SharePoint library. This interface gives users the best of both worlds: CRM for field level data and SharePoint for document management. The possibilities are seemingly endless.