Skip to content
Bitta Apps
Operations, performance & upgrades

Business Central Sandbox vs Production: Make It Obvious

Environment naming, company badges, access groups, copied-sandbox hygiene, and a color bar that names the environment on every page

Two matching app windows, one with a lime top bar and one with an ink and grey striped top bar, with a cursor over the lime window.
On this page

Posting a test invoice in the live company is rarely a skills problem. It is a visibility problem. A sandbox copied from production carries the same companies, customers, and open documents, so the page a tester sees in one browser tab can look identical to the page an accountant sees in another. The answer to Business Central sandbox vs production should never depend on someone reading a URL carefully. This article covers the built-in signals, the access controls, the cleanup Microsoft applies to copied environments, and a checklist.

Why the two environments look the same

Microsoft describes production and sandbox environments as built for different jobs. Production is where a business runs its daily work, on performance tiers with automatic, frequent backups. Sandboxes are for development, testing, and training, and can be deleted at will. Under the surface they differ: the debugging endpoint is open by default in a sandbox, and sandbox databases can't be exported.

None of that is visible to a user. When an administrator copies an environment, the new environment contains the source data plus every per-tenant extension and Marketplace extension installed and published in the original. The role center, the customer list, and the open sales orders all match. Only a few small signals differ.

What Business Central already shows

The environment name in the top bar and the URL

Business Central displays the environment name in the top bar. Microsoft's sandbox environments article notes that users can't change the name or switch environments from there; an administrator renames the environment or shares a link to another one.

The name is also part of the address. The web client URL syntax places the environment name after the host name and optional tenant ID: https://businesscentral.dynamics.com/<tenant>/<environmentname>/. A user who opens a saved bookmark lands where the bookmark points. A user who follows a link pasted into Teams lands wherever the sender was working.

Company badges

On the Company Information page, the Company Badge FastTab replaces the standard company icon with a custom badge, set per company. After saving, refresh the browser with Ctrl+F5. Microsoft's company information documentation states that the badge appears in the browser tab and in page links copied into Word, Outlook, and Teams. Its shape also signals the environment type: a round badge means production, a square badge means sandbox.

The badge also shows in the company switcher (Ctrl+O), which lists every company in every environment a user can access, as described in Switching to Another Company or Environment. The shape follows the environment type automatically, but the badge itself is set per company on the Company Information page. After every copy, open the sandbox and adjust its badges so they differ from production.

Name environments so the URL tells the truth

The environment name is embedded in every bookmark, deep link, and integration. Microsoft's guidance on renaming environments lists what a rename affects: bookmarked web client URLs, deep links shared in email and Teams, web services URLs used by OData and SOAP integrations, the Outlook and Excel add-ins, Power BI reports, Power Apps and Power Automate connections, launch.json files in AL projects, and CI/CD pipelines. Links created before the rename stop working, and the rename itself restarts the environment. Naming is a day-one decision.

The admin center API reference sets the rules: fewer than 30 characters, starting with a letter, using only letters, numbers, underscores, or hyphens, and not a reserved value. A practical convention inside those rules:

  • Keep one name that reads unmistakably as live, such as Production.

  • Name every sandbox by purpose: UAT, Dev, Training.

  • Add the copy date to short-lived copies, such as UAT-2026-10-28, so stale copies are easy to spot.

  • Never put "prod" in a sandbox name.

Restrict who can reach production

Visual cues reduce mistakes. Access rules remove a whole class of them. In the Business Central administration center, an administrator can assign a Microsoft Entra group to an environment. All licensed users are still added to the environment, but only direct and indirect members of the group can sign in. Two limits apply: the restriction doesn't cover internal administrators, and a change can take a while before access is actually revoked.

Consultants are governed by a separate control. The Partner access setting decides whether delegated administrators and multitenant apps can reach an environment, and from which partner tenants, up to 10 per environment. Only internal global administrators can change it, and the setting is preserved when an environment is copied or restored.

A workable pattern: a production group limited to people who transact, a sandbox group for testers and consultants, and Partner access on production granted only to the partners who support it. Inside each environment, permission sets still govern what each user can do.

Copied-sandbox hygiene

Microsoft applies a documented set of precautions whenever an environment is created as a copy:

  • Job queue tasks stop. Only tasks marked as belonging to the current environment can run. Restart them selectively from the Scheduled Tasks page.

  • Agents are turned off. They are copied with their tasks and must be enabled deliberately on the Agents page.

  • Outbound HTTP calls from extensions are blocked with the message "The request was blocked by the runtime to prevent accidental use of production services." Each extension, including libraries, needs Allow HttpClient Requests selected on its Extension Settings page.

  • Integration setups are disabled or cleared. The list includes Graph Mail Setup, CRM Connection Setup, CDS Connection Setup, all webhooks, and all Service Connection records. Email accounts of the Microsoft 365 and Current User types are deleted, and SMTP server details are cleared.

  • The Application Insights connection string is copied. The sandbox sends telemetry to the same resource as production until someone changes it.

  • Privacy actions don't carry over. Anything done in production to comply with privacy regulations has to be repeated in the copy.

The risk sits in the step after the copy. Someone re-enables a job queue entry or grants an extension HTTP access to make a test pass, and the sandbox starts calling a real bank, carrier, or customer endpoint. Before re-enabling anything, point it at a test endpoint and record who approved it. The job queue support handoff describes how to assign a recovery owner, and the webhook renewal and recovery checklist covers subscriptions that a copy disables.

Bitta Theme: a larger visual layer

The built-in signals are small: a name in the top bar, a badge shape, a segment of the URL. Bitta Theme for Business Central, a free Chrome extension from Bitta Apps, adds a larger one. It places a colored bar across the top of every Business Central page that names the environment and company, for example PRODUCTION and CRONUS USA. By default, production environments are red and all other environments are green. Each environment can have its own color, set from the extension's toolbar popup, and the bar can be switched off at any time. The extension also offers Dark, Dim, and High contrast themes, covered in the Bitta Theme introduction.

Bitta Theme works with Business Central online at businesscentral.dynamics.com. It changes only how pages look in the user's own browser, and each user sets colors in their own popup. It doesn't restrict access, and it doesn't change Business Central data or configuration. It sits alongside security groups and company badges as one more layer, not instead of them. It is available from the Chrome Web Store and on the Bitta Apps free tools page.

To see the environment bar on real Business Central pages, watch the one-minute Bitta Theme overview video on YouTube. The bar appears at 0:34.

The checklist

  1. Naming convention. Production reads as live. Every sandbox is named by purpose, short-lived copies carry an ISO date, and no sandbox name contains "prod". Rename early, before integrations and bookmarks depend on the name.

  2. Company badges. Set a badge on every company in every environment. After each production copy, check and adjust the badges in the sandbox, then refresh with Ctrl+F5. Train users that round means production and square means sandbox.

  3. Bitta Theme bar colors. Agree on one color per environment, such as red for production, green for sandboxes, and a third color for UAT. Ask each user to open each environment once and set the agreed color.

  4. Permissions. Assign a Microsoft Entra group to production, review Partner access per environment, and remember that internal administrators bypass the group.

  5. Copied-sandbox hygiene. Review the Scheduled Tasks page and Extension Settings before restarting anything. Change the Application Insights connection string. Re-enable email, webhooks, and HTTP access only against test endpoints, with a named approver.

Environment counts tend to grow over time: a UAT copy for an upgrade, a training sandbox, a preview environment, an agent pilot. Each one is another browser tab that can pass for production. Settling names, badges, colors, and access once, then repeating the hygiene steps on every copy, keeps that growth from turning into a posting error. A Business Central Environment Snapshot is a practical starting point for inventorying what a tenant has today.

FAQ

Frequently asked questions

How can I tell whether I am in a Business Central sandbox or production?

Check the environment name in the top bar and in the URL. If a company badge is set, its shape tells you the environment type: round for production, square for sandbox. Bitta Theme adds a colored bar that names the environment and company on every page.

What happens to job queues when production is copied to a sandbox?

Job queue tasks are stopped automatically in the copy. Only tasks marked as belonging to the current environment can run, and you restart them from the Scheduled Tasks page.

Can I stop users from signing in to production while they keep sandbox access?

Yes. Assign a Microsoft Entra group to the production environment in the Business Central administration center. Only direct and indirect members can sign in. Internal administrators are not restricted by the group.

Is it safe to rename a Business Central environment?

Renaming changes the environment URL. Bookmarks, shared deep links, web services URLs, add-ins, Power BI reports, Power Automate connections, and AL launch.json files that use the old name stop working, and the rename restarts the environment. Plan it and notify users first.

Does Bitta Theme replace company badges or access control?

No. Bitta Theme changes only how pages look in each user's own browser. It does not restrict access or change Business Central data or configuration, so it works alongside badges and security groups.

Sources

Claims in this article were checked against the following on Nov 4, 2026.

  1. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/environment-types
  2. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-environments-copy
  3. learn.microsoft.com/en-us/dynamics365/business-central/admin-company-information
  4. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-manage-access
  5. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-environments-rename
  6. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/administration-center-api_environments
  7. learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-web-client-urls
  8. learn.microsoft.com/en-us/dynamics365/business-central/admin-sandbox-environments
  9. learn.microsoft.com/en-us/dynamics365/business-central/ui-organization-switch
  10. chromewebstore.google.com/detail/ogninhbhhbifjfioabijebglgkhneemk

Written by

Mohammad Nour Itani

Founder & Senior Business Central Developer

Related services

Work with Bitta Apps on this

Next step

Talk to a senior Business Central consultant, not a sales rep.

Fixed-price proposal in writing within five business days of discovery.