One of the best blogs on CRM is the blog – Dynamics CRM in the Field and it’s written by Microsoft’s premier field Engineers, most people may not have heard of these but if you ever have a problem with CRM that you can’t resolve and raise a call with Microsoft, they will send one of these people out. This is how they describe themselves.
“If you happen to be wondering what PFE is, the Premier Field Engineering (PFE) team at Microsoft is a worldwide organization that provides proactive and reactive services to our customers. We provide technical leadership for Microsoft customers around the world, promoting health in their IT and business environments through onsite, remote and dedicated support services. The mission of the Premier Field Engineer Team is to “improve the IT and business health of our customers. Help them grow revenue, reduce cost, gain inefficiencies & improve profit, improve their customer and vendor relationships, and improve their employees’ lives.”
I have dealt with one PFE and he was very helpful and a nice chap.
The in the field blog is very useful and I would recommend you subscribe because it often has useful dates, examples and other useful information from CRM people who work for Microsoft and have insider information.
They recently published a blog with all the white papers for CRM 2013, click the link to see all of them
I have made a list of the white papers I think are most useful from the list, I have removed implementation guide, SDK, counters and other links which are useful but most people either know about or have already downloaded.
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
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.