CRM 2016 On-Premise to SharePoint Online Gotcha’s

CRM 2016 On-Premise to SharePoint Online

Recently, I was asked to setup server-based authentication from Dynamics CRM 2016 to SharePoint Online.

Step 1, read through the TechNet article and make sure all the prerequisite stuff was complete on the CRM installation.

Microsoft Dynamics CRM

  • System Administrator security role. This is required to run the Enable Server-based SharePoint Integration wizard in Microsoft Dynamics CRM.
  • If you are using a self-signed certificate for evaluation purposes, you must have local Administrators group membership on the computer where Microsoft Dynamics CRM Server is running

SharePoint Online

  • Office 365 Global Administrators membership. This is required for administrative-level access to the Office 365 subscription and to run the Microsoft Azure PowerShell cmdlets

Step 2, using the TechNet article start making the changes on the CRM server, until as usual something goes wrong! 🙂 The article, while generally easy to follow, I found myself getting tripped up on the SharePoint Integration Wizard steps (in CRM 2016), getting errors on the validation steps.

Error 1

This error is caused by the CRM Account not having an email address associated with it

Error 2

The second error was caused by the certificate permissions needing to be reapplied. It also has a nasty side affect of effectively bringing down CRM authentication until the permissions are reapplied. Locate the certificate, Right click | All Tasks | Manage Private Keys …


Once permissions were reapplied the process continued without any issues.

Related Post

One thought on “CRM 2016 On-Premise to SharePoint Online Gotcha’s

  1. This is fantastic as it’s solved a problem that I have been working to fix for months. My issue was that the app service account that CRM was running under was NETWORKSERVICE and this had no read access to the private key.

    Once I added the permission and restarted the services, it all sprung into action.

    Thanks again!

Leave a Reply

Your email address will not be published. Required fields are marked *