Business Central environments and sandboxes
How environments work in Business Central SaaS — production vs sandbox, capacity, copies, and lifecycle management.
In Business Central SaaS, an environment is an isolated instance of the application with its own database, users, configuration, and installed extensions. Every Microsoft 365 tenant that licenses Business Central gets one production environment included; additional environments are bought as add-ons.
Environment types. Production environments hold real business data, have stricter update controls (a customer-defined update window), and are backed up automatically with point-in-time restore for 28 days. Sandbox environments are intended for development, testing, training, and demos. Sandboxes are free to create (up to a configurable limit) but live on lower-priority infrastructure, so they may pause, throttle, or update sooner than production.
Capacity and storage. Each Business Central licence contributes a small amount of database capacity and file storage to the tenant. Sandboxes count separately. When the tenant runs low, customers buy storage add-ons. Capacity is monitored from the Business Central admin centre — the canonical place to manage environments.
Copying environments. From the admin centre you can copy a production environment to a sandbox (most common, for safe testing with real data) or a sandbox to a sandbox. Copies preserve installed extensions and configuration but generate a new connection identity, so tenant integrations don't fire automatically against the copy.
Updates. Microsoft schedules every environment for major version updates twice a year (Wave 1 in April, Wave 2 in October). Customers can shift the update by a small number of weeks via the admin centre, and can ask Microsoft to update a sandbox first so they can validate before production.
Restore. The admin centre offers a self-service point-in-time restore to any moment in the past 28 days. The restored environment lands as a new environment — the live tenant continues running until you switch over.
Lifecycle pattern. A healthy lifecycle has at least three environments — Dev (sandbox), UAT (sandbox), Production — with extensions promoted dev → UAT → prod through AppSource or PTE deployments.
Related guides
- Application areas in Business CentralHow Application Areas in Business Central control which features users see — Basic, Essential, Premium, and how customisations can extend the application area system.
- Batch posting in Business CentralHow Business Central handles batch posting of journals, orders, and documents — performance, background processing, and the trade-offs against single posting.
- Business Central feature managementHow Business Central's Feature Management page lets administrators preview, opt-in to, or delay new features within a release wave.
- Business Central integrations with the Power Platform and Microsoft 365How Business Central plugs into Power Apps, Power Automate, Power BI, Excel, Outlook, Teams, and Copilot.
- Business Central licensing and pricingHow Business Central is licensed — Essentials vs Premium, Team Members, External Accountants, and what really drives total cost.