Microsoft release some excellent white papers, usually one of the trickiest problems is knowing about it, which is where the CRM Dymanics community comes in.
I was told about the white paper by one of Ciber’s excellent CRM consultants, so I thought I would pass on the information to the greater CRM community via my blog.
You can find the white paper here
http://www.microsoft.com/en-us/download/details.aspx?id=40861
I will let Microsoft describe the white paper for me
This paper describes how 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.
and in more detail
- 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 provides 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. This paper describes how the 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.
The good news for people using CRM 2011 is most of the paper is applicable to CRM 2011 as well as CRM 2013 because the functionality has not changed apart from the new Access Team functionality in CRM 2013.
What is really useful about the white paper is it discusses the potential performance impart a number of different security solutions. Microsoft security model offers lots of flexibility but can be confusing sometimes, particularly when trying to explain to customers and where the various security components overlap (business units, security roles, teams).
The document is useful because you can give it to a customer to help them get used to the terminology of the security concepts and tools in CRM and with the scenarios it will help customers consider how they can setup security in CRM to suit their organisation.
Hosk's Dynamic Blog 