A sandbox environment in Business Central is a safe copy of your system where you can test and develop freely – without touching live data. Here is how to use one.
Business Central gives every tenant two types of environments: production and sandbox. The production environment is where your business runs. It holds your live data and your posted records. A sandbox environment is a separate space where you can test changes, build extensions, and try new features. Any change you make in a sandbox stays in that sandbox. In short, the two environments look the same but serve very different purposes. Also, switching between them is simple once you know where to look.
What Each Environment Type Does
The production environment holds all your live company data – open orders, posted invoices, customer records, and financial entries. Changes here have real effects on live records and active users. So this is the environment you treat with care.
A sandbox environment is a copy of your system that you can use freely. You can install apps, post test entries, change settings, or run extensions. None of this affects production. Furthermore, each BC tenant gets up to three sandbox environments at no extra cost. So there is no reason not to use one for any task that carries risk.
Also, a sandbox does not need to start empty. You can create one as a direct copy of your production environment. As a result, any testing or development you do in the sandbox happens against the same data you work with every day. This makes testing more realistic and reduces surprises when changes move to production. Therefore, the copy option is the most common way to set up a new sandbox.
How to Tell If You Are in a Sandbox Environment
Production and sandbox environments look the same in BC. The layout, menus, and page structure are all identical in both. This makes it easy to lose track of which one you are in. However, BC shows the environment name in the top right corner of every page. That button always reflects your current environment.
Specifically, if you are in a sandbox environment, the button shows the name you gave it when you created it. In addition, BC sometimes shows a banner at the top of the screen when you are in a sandbox. You can snooze this banner, so it may not always be visible on screen. Therefore, the environment name button in the top right is the most reliable indicator.
Therefore, it helps to give each environment a clear name when you set it up. For example, names like “Production”, “Dev”, or “Training” make the indicator easy to read at a glance. Moreover, this habit prevents most cases of working in the wrong environment by mistake.
How to Switch to a Different Sandbox Environment
To move between environments, click the environment name button in the top right. A list of all available environments appears. Click the one you want to open, select a company, and click Switch. BC loads the selected environment right away.
Furthermore, this works for both directions – you can move from a sandbox environment to production, or from production to a sandbox. Also, the list shows the type of each environment, so you can confirm your choice before switching.
The URL Trick for Viewing Only Sandboxes
There is a quick way to list only your sandbox environments. In your browser, go to the base URL for your BC tenant. This is the part that starts with businesscentral.dynamics.com and includes your tenant ID. Then add ?sandbox=true at the end and press Enter. BC shows only the sandbox environments linked to your tenant. As a result, you can be certain that every option in the list is a sandbox – not production.
This trick is most useful when you have several environments with similar names. It removes any doubt about which ones are sandboxes. Additionally, it is a fast way to get directly to your sandbox list without clicking through the full environment menu.
Moreover, this URL format works as a bookmark. You can save it in your browser and open the sandbox list directly from there. So if you switch between sandboxes often, this bookmark saves several clicks each time you need it. However, note that the URL still requires you to be signed in to your BC tenant first.
Three Reasons to Use a Sandbox Environment
There are three main reasons to work in a sandbox environment rather than production.
Development
When building a custom extension, developers always use a sandbox environment first. The sandbox holds a copy of production data. So development happens against real records. Once the extension passes testing, it then rolls out to production after hours – without disrupting live users. In this way, the sandbox keeps production stable during the build.
Troubleshooting
When a problem appears in production, copy the environment to a sandbox environment and reproduce the issue there. You can test fixes, post entries, and change settings freely. After you confirm the fix works, you apply it to production. Consequently, troubleshooting in a sandbox carries no risk to live data.
In practice, this approach is also faster. You can move quickly in a sandbox because mistakes do not matter. So you try more options and find the root cause sooner. Then, once you have a confirmed fix, the move to production is straightforward.
Testing New Features
Before enabling a new app or feature in production, try it in a sandbox environment first. Copy your production environment to a sandbox, install the feature, and test it against real data. If it works as expected, you can then install it in production with confidence. Additionally, this approach means your users do not see unexpected changes until you are ready to roll them out.
Wrapping Up: How to Use a Sandbox Environment in Business Central
A sandbox environment in Business Central gives you a safe place to develop, troubleshoot, and test. It looks identical to production, but any change you make stays isolated. Each tenant gets up to three sandboxes for free. That means you have no excuse to skip using one. So there is no reason to work directly in production when a task carries any risk. Use a sandbox first. It is free, it is fast to set up, and it keeps production safe.
In practice, two habits make all the difference. First, always check the environment name button in the top right before making changes. Second, give each environment a clear, distinct name when you create it. Together, these steps prevent most accidental changes to live data.
For more Business Central guides and tutorials, visit NAV SEAL Blog and watch more videos on our YouTube Channel.
