Microsoft Dynamics 365 Business Central and multiple cloud sandboxes

The new April 2019 release for Dynamics 365 Business Central introduced lots of new features and one of the most interesting is for sure the possibility to have more than one online sandbox.


With this new release (platform 14) you will be able to create up to three sandbox environments at a time per tenant (with different names) and:

  • You can choose to create a sandbox based on the current release or on the preview of the next release.
  • You can choose to have a sandbox with copy of the production data or not.
  • Sandbox environments created as a copy of your production environment will be created on the same version as the production environment.
  • At the moment, multiple sandboxes are still be free but this will change in the future.

Related to extensions development and management, now:

  • When you create a sandbox environment as a copy of your production environment, per-tenant and AppSource extensions are now also copied to the new sandbox environment.
  • When sandbox environments are upgraded, both per-tenant and AppSource extensions are upgraded with the sandbox environment (no more need to re-install the extensions after the upgrade).
  • You can now upload per-tenant extensions using Extension Management in a sandbox environment, with the option to target the current version, the next minor version, or the next major version.

I often see many people that develop extensions directly by using the online sandbox from Visual Studio Code. This is a way of work that personally I don’t love too much and that I never recommend (I prefer to develop locally and then use the online sandbox for final testing and for customer’s testing), but if you’re doing that remember that actually,  also if you have multiple sandboxes, you cannot connect from Visual Studio Code to the sandbox environment you want, but only to the  main one (which is /sandbox as url).

In the future, you will be able to specify the sandbox name to connect from Visual Studio Code by using a new sandboxName parameter in your launch.json configuration file:



A final last consideration: please don’t abuse on sandboxes, use them when you really need them and avoid to recreate N sandboxes every day.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.