The challenge of using DTAP in your Dynamics CRM deployment process

When planning a new Microsoft Dynamics CRM solution, one of the first decisions a solution architect needs to make is around the setup of the right combination of development, test, and production environments to ensure the delivery of a system that works as expected.

In the enterprise segment, it is common to use the so-called 'DTAP' model, which is short for development, test, acceptance and production, and requires managing multiple environments during an implementation.

DTAP basics

The development environment is strictly for building your application. Common tasks here involve customizations like front- and back-end coding.

The test environment is the place where (preferably) a dedicated tester checks whether the functionality is built according to your requirements.


Requires FREE Membership to View

Become a Member Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Sandor Schellenberg

Sandor Schellenberg is the owner and founder of friendlyITsolutions, which mainly focuses on Microsoft Dynamics CRM and related software in the Microsoft stack. He is a Senior Microsoft Dynamics CRM Consultant/Solution Architect and is specialized in data migration & integration. In autumn 2009 his work was recognised and rewarded with a invitation to Scribe Software MVP Program. 

His roots in Microsoft-based Internet technologies go back more than twelve years, and since 2005 he has specialized in Microsoft Dynamics CRM. Starting with his first guest post on the blog of Menno te Koppele, he decided to start his own blog, Friendly Microsoft CRM Monster, a blog with a wink. The blog is widely read in the Dynamics CRM community and focused mainly on Microsoft Dynamics CRM technical and integration/migration topics.

Read full bio...