{"id":2327,"date":"2015-10-15T06:05:54","date_gmt":"2015-10-15T06:05:54","guid":{"rendered":"https:\/\/cm-edgetun.pages.dev\/en-us\/innovation\/blog\/ms-industry\/crm-implementation-and-deployment-best-practices\/"},"modified":"2026-04-15T15:24:20","modified_gmt":"2026-04-15T22:24:20","slug":"crm-implementation-and-deployment-best-practices","status":"publish","type":"ms-industry","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/microsoft-cloud\/blog\/financial-services\/2015\/10\/15\/crm-implementation-and-deployment-best-practices\/","title":{"rendered":"CRM implementation and deployment best practices"},"content":{"rendered":"\n

As a Global Program Manager for Financial Services, I often hear variations on a theme in my conversations with our prospects and customers: can you share some best practices with us for an implementation or deployment of a Microsoft Dynamics CRM based solution?<\/p>\n\n\n\n

The answer I give depends on the deployments you choose, as there are different considerations for each. As an overview, with Microsoft Dynamics CRM On Premises you would have to install, configure and maintain your CRM infrastructure along with its integration points. Azure-Hosted Microsoft Dynamics CRM Infrastructure means you can run a Dynamics CRM infrastructure on Microsoft Azure Infrastructure Services (IaaS) with Azure Premium Storage for production workloads. Microsoft Dynamics CRM Online lets you take full advantage of Microsoft cloud speed, scale and economics as well as frequent product release and updates bringing you more innovation and business relevance each time.<\/p>\n\n\n\n

Now let\u2019s take a deeper look at each options.<\/p>\n\n\n\n

On Premises Deployment<\/h2>\n\n\n\n

There are a couple of key things to remember when deploying Microsoft Dynamics CRM in your environment.<\/p>\n\n\n\n

You\u2019ll need to properly size the architecture of your solution: know where you\u2019re going with your solution so that your IT team knows what to prepare for. Will it be a business critical application or can you tolerate some downtime during the year? Do you need to integrate with multiple different systems? Do you need to access the solution from outside your company network? Do you need a mobility approach? Which clients are you looking to use (Web, Outlook, Mobile, Custom)? Will\/can you share your infrastructure with other business teams in your organization?…<\/p>\n\n\n\n

Your architecture will change depending on your key workload and your infrastructure may need to have specifics outputs or integrations points. For instance, a call center would need a highly responsive environment with multiple points of integration; while a sales team with mobility needs will require access to a secured mobile environment.<\/p>\n\n\n\n

Planning for your application lifecycle management approach is a must: typically, in large organizations, we often see the following environments to support the lifecycle of the application: development environment, integration environment, test environment, production environment.<\/p>\n\n\n\n

You will want to plan for the deployment. Can you go for a big bang approach? Or do you need to start with a couple of pilots first in order to adjust the infrastructure?<\/p>\n\n\n\n

You need to make sure your IT staff is properly trained on this new technology in order to fully benefit from your solution. Even though the solution can look very familiar, there are still a lot of specificities that need proper training to master.<\/p>\n\n\n\n

Test, test, test! Performance tests help stress the environment to their limits and ensure that you have properly set up your various components. I have seen a SQL Server \u201cproperly installed\u201d but not to the standards need by a large end-users base many times.<\/p>\n\n\n\n

Recommended resources:<\/p>\n\n\n\n