CRM Services

Microsoft Dynamics CRM 2011 consists of a number of service roles that can be run on separate servers to provide better performance and to offer improved fault tolerance. The following table introduces these roles, giving a description of the service's role and listing the server group to which the role belongs.

Table : CRM Service Roles

Server Role


Server Group

Discovery Web Service

Finds the organization that a user belongs to in a multi-tenant deployment.

Front-end Server

Organization Web Service

Supports running applications that use the methods described in the Microsoft Dynamics CRM Software Development Kit.

Front-end Server

Web application Server

Runs the Web application Server that is used to connect users to Microsoft Dynamics CRM data. The Web application Server role requires the Organization Web Service role.

Front-end Server

Help Server

Makes Microsoft Dynamics CRM Help available to users.

Front-end Server

Asynchronous Service

Processes queued asynchronous events, such as workflows, bulk email, or data import.

Back-end Server

Sandbox Processing Service

Enables an isolated environment to allow for the execution of custom code, such as plug-ins. This isolated environment reduces the possibility of custom code affecting the operation of the organizations.

Back-end Server

Deployment Web Service

Manages the deployment by using the methods described in the Microsoft Dynamics CRM 2011 Deployment Software Development Kit.

Deployment Administration Server

Service providers intending to offer hosted Microsoft Dynamics CRM 2011 services may opt to deploy the services through use of the Server Groups. However, separating the services across an architecture designed for high availability may entail further separation of the roles. Consider providing redundancy for these service roles in particular as you design your implementation:

  • Web application Server
  • Asynchronous Service
  • Sandbox Processing Service

    The CRM service accounts should have limited access in the domain, restricting them to only the necessary resources in the related CRM deployment group. If you plan to have more than one deployment group, consider establishing an account-naming scheme that is helpful in identifying relationships.