Integrating Microsoft Dynamics 365 and SharePoint enhances document management and collaboration. However, the different security frameworks of these two platforms can make it difficult to maintain consistent user permissions. This inconsistency can lead to security risks and compliance issues.

To mitigate these risks and ensure a cohesive and secure environment, it is advisable to replicate the Dynamics 365 security model in SharePoint. We have compiled all the details on this permissions replication into a whitepaper.

Whitepaper Key Insights

Key insights from the “Ensuring Consistency in Security Models: Lessons learned with Microsoft Dynamics 365 and SharePoint” whitepaper are:

• The differences between the security models of Dynamics 365 and SharePoint.
• Practical steps for replication, from assessment and planning to mapping, tool selection, implementation, and validation
• The use of both custom scripts and automated solutions like Connecting Software’s CB Dynamics 365 to SharePoint Permissions Replicator
• A case study on Liebherr, a global manufacturer, demonstrates the successful replication of security models, resulting in improved document control, enhanced security, and reduced administrative burdens.

→ Download: Ensuring Consistency in Security Models: Lessons learned with Microsoft Dynamics 365 and SharePoint

Architecture Model for Automated Dynamics 365 and SharePoint Permission Replication

The automated solution described in the whitepaper to handle Microsoft Dynamics 365 and SharePoint permission replication comprises several components, as shown in the high-level architecture diagram below:

1. Dynamics 365 Solution
2. Connecting Software SaaS Portal
3. CB Dynamics 365 to SharePoint Permissions Replicator cloud service

The SaaS Portal handles configuration, subscription management, and monitoring.

The Dynamics 365 Solution contains a plugin that registers all steps that can affect permissions in Dynamics 365, namely changes in:

• Users: Creation, modification, deactivation, or reactivation of user accounts.
• Security roles: Different sets of permissions assigned to users.
• Sharing: Specific users or teams are granted access to individual records.
• Teams: Users or security roles assigned to teams, including access teams and access team templates for record access.
• Business units: Changes to users’ business units or modifications in the business unit hierarchy.
• Hierarchy security: Managers have access to records owned by their subordinates (available in CRM 2015, 2016, and Online).

When one of these occurs, the plugin will notify the cloud service, which will ensure that the correct permissions are written into SharePoint. This makes sure that the privileges in Dynamics 365 will be exactly replicated to the relevant SharePoint files and folders.

The full article was originally posted on Apr 22, 2026, on the CRM Software Blog:  Ensuring Consistency in Security Models: Lessons learned with Microsoft Dynamics 365 and SharePoint

Connecting Software is proud to be one of CRM Software Blog’s top contributors since 2019.

The post Ensuring Consistency in Security Models: Lessons learned with Microsoft Dynamics 365 and SharePoint appeared first on CRM Software Blog | Dynamics 365.