Environments

An environment is an isolated instance of a Dynamics 365 tenant, with its own database, users, configurations, and code. A typical setup has one production environment plus one or more sandbox environments for development, testing, training, and data refreshes. Business Central includes one production environment per tenant by default, with additional production and sandbox environments licensed as add-ons. Dynamics 365 CRM-side apps and Finance/SCM follow a similar model with their own environment SKUs. Best practice is to develop in a sandbox, test in a separate UAT sandbox, and promote releases to production through a controlled lifecycle.

In practice, "isolated" means data as well as code — a sandbox environment does not automatically see production's records, and refreshing a sandbox from a production copy is an explicit, scheduled action, not a live sync. This is what makes sandboxes safe places to test destructive changes (a bulk data fix, an extension upgrade) without any risk to live data, but it also means a sandbox can drift out of date with production over time if nobody refreshes it, which is a common source of "it worked in test" surprises.

Where confusion shows up: Dataverse-based environments and Business Central environments are conceptually similar but licensed and provisioned independently — a Power Platform environment does not automatically give a company a Business Central sandbox, and vice versa. A project spanning both Dataverse-based CE apps and Business Central needs to plan environment topology for each platform separately, even though the vocabulary ("sandbox," "production") is shared across both.