Skip to main content

Microsoft Dynamics CRM 2015 Upgrade: Time to Consider Deployment Change

If you are upgrading to Microsoft Dynamics CRM 2015, now is a good time to examine your deployment model as well. 

Moving from on premise to the cloud or vice versa may require architectural changes and programming, so an upgrade is the best time to make these changes since you will be doing some re-architecting of your solution anyway.

You can choose from four deployment models:

1. On premise -- traditional deployment in your data center
2. Dynamics CRM Online -- in the Microsoft cloud
3. Run Dynamics CRM on Microsoft Azure cloud infrastructure
3. Third party hosting -- hosted by another provider

The deployment model also affects your product licensing strategy.  Microsoft offers flexibility which may help with moving from one deployment model to another.  For instance, Dynamics CRM Online subscriptions may be used to cover on-premise licensing while you migrate from on premise to cloud deployment.   The InfoStrat Dynamics CRM cost calculator provides licensing and subscription costs for on premise and CRM Online.

If you are upgrading from Dynamics CRM 2011 (or 4.0), you will likely be rewriting code that is no longer supported in 2015, allowing you to optimize performance for a cloud deployment.   Microsoft provides insights on this topic in What's New for Developers.

Cloud deployment offers different approaches to integration than on premise.  You also have different ways to tune performance in cloud deployment than conventional on premise deployment. 

Tackling deployment options along with your upgrade is a great way to save time and money in the long run.




Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do