Skip to main content

6 Reasons to Use Microsoft Dynamics 365 Sandbox Instances



Microsoft hosts production and non-production instances of Dynamics 365 (formerly called Dynamics CRM).  Most organizations using Dynamics 365 will benefit from having at least one sandbox instance for their solutions.

Here are the top reasons you should consider a sandbox:

  1. When you are developing solutions, the sandbox can be the development environment.  This means that you will not disrupt users who will be in the production instance.
  2. Sandboxes are great for testing before you release a solution to production.
  3. You can use sandboxes for training.  Users can add or delete whatever data the want during the training sessions without fear or harming the production system.
  4. For evaluating Dynamics solutions, a sandbox is more permanent than signing up for a trial account which will end.   
  5. Sandboxes offer some administrative controls which are not available in production instances, such as the ability to reset a sandbox instance which essentially wipes the solution and restores Dynamics 365 to default settings. 
  6. Microsoft provides Administrative Mode for sandboxes which only allows System Administrator and System customizers to log in and make changes. 
Microsoft Dynamics allows you to copy an instance in order to move a solution from production to a sandbox or vice versa. The copy instance feature allows you to determine whether to include all data, users and customizations or exclude the data.  Normally you will want to include test data in a sandbox for testing and training. 

What about subscriptions or licenses for Dynamics 365 sandboxes? The key thing to remember is that user subscriptions are based on named users and not on instances.  If you have 25 users and 3 instances (1 production, 1 development and 1 test) you only need 25 user subscriptions.  Microsoft provides a free sandbox instance for customers with 25 or more users and sells additional instances for a monthly fee. 

For more technical details, see Understanding Dynamics 365 Online Instance Management

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

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ 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 not require advan

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