Microsoft Dynamics 365 employs a robust, role-based security model to control access to data and functionality within the system. Since it’s a SaaS services hosted within Microsoft Azure datacenters, it is designed for providing performance, scalability, security, management capabilities and service levels.
This model ensures that users can only access the information and perform the actions necessary for their roles, adhering to the principle of least privilege.
Through this blog, let’s explore the key concepts of the Microsoft Dynamics 365 security model and understand how it ensures data security.
Key concepts in D365 Security
1: Security roles
A security role is a collection of privileges that define the tasks a user can perform and the data they can access. Roles are assigned to users or teams, and they determine the level of access across the system. For example:
- Sales manager role: Can view and edit all sales records.
- Customer Service representative role: Can only view and edit cases assigned to them.
2: Duties
A duty is a group of privileges that represent a specific task or responsibility. Duties are reusable components that can be included in multiple roles. For example:
- Maintain customer records duty: Includes privileges to create, read, update, and delete customer records.
- Generate invoices duty: Includes privileges to create and post invoices.
3: Privileges
A privilege is the most granular level of access control. It defines the ability to perform a specific action on a specific type of record. Privileges are grouped into duties, which are then assigned to roles. Examples of privileges include:
- Read: View a record.
- Write: Edit a record.
- Delete: Remove a record.
