Share via

Scalable Security Modeling with Microsoft Dynamics CRM 2013

  • Article

 

Applies To: Dynamics CRM 2013

Author: Roger Gilchrist

Published: October 2013

Summary

Microsoft Dynamics CRM 2013 offers a wide range of security modeling features, and it is important to choose the most appropriate approach to implementing a particular solution. This paper describes how security modeling features in Microsoft Dynamics CRM 2013 related to for authorization work at scale, the associated implications, and guidance on common and recommended usage patterns for modeling Microsoft Dynamics CRM 2013 security at scale, incorporating teams as appropriate.

Applies To

  • Microsoft Dynamics CRM 2013

Microsoft Dynamics CRM 2013 offers a wide range of security modeling features, and it is important to choose the most appropriate approach to implementing a particular solution. Each feature offers a combination of characteristics that provide a balance between granularity of access control, administrative ease, and impact on scalability. Having an understanding of the underlying mechanisms supporting each security modeling feature can be useful when selecting the best approach to solving a particular challenge, especially when planning to develop a large volume system.

Granting a user access to the system can be broken out into:

  • Authentication, which determines who users are and confirms that they are who they say they are

  • Authorization, which determines whether the authenticated users are entitled to access the system and what within the system they are permitted to see or do

Authentication in Microsoft Dynamics CRM 2013 is handled using platform features such as Integrated Windows Authentication or Claims Based Authentication with an identity provider such as Active Directory Federation Services. These all determine the user identity requesting access to the system. The deployment and scalability of the technologies supporting authentication is best described by resources focused specifically on those technologies and is therefore out of the scope of this document.

After a user has been identified, information recorded about the user within the Microsoft Dynamics CRM 2013 system itself, such as their security roles and team memberships, is used to determine whether they are allowed to use the system and what they are allowed to see and do within the system, or what they are authorized to do.

This paper describes how these security modeling features in Microsoft Dynamics CRM 2013 for authorization work at scale, the implications associated with these features functioning at high volumes, and guidance on common and recommended usage patterns for modeling Microsoft Dynamics CRM 2013 security at scale, incorporating teams as appropriate.

Download Scalable Security Modeling with Microsoft Dynamics CRM 2013 from the Microsoft Download Center.

Additional Information

Author Bio

© 2016 Microsoft Corporation. All rights reserved. Copyright