In Chapter 1, you saw that Dynamics 365 CE apps all share one foundation: Dataverse. But Dataverse isn't one giant, shared database that every company plugs into. Each organization gets its own separate, self-contained copy — called an environment, also known as an instance. The two words mean the same thing and are used interchangeably.
- An environment (or instance) is a self-contained copy of Dataverse
- Each one holds its own data, customizations, and security settings
- Production = where real work happens, the "road"
- Sandbox = where you build and test safely, the "garage"
- Trial environments let you explore without a paid license
An environment is more than a login screen. It's a complete, isolated container that holds:
- Its own data — your actual customer records
- Its own customizations — any fields, forms, or automations someone has built
- Its own security settings — who's allowed to see what
Two environments belonging to the same company are still two entirely separate worlds. A record created in one does not exist in the other unless someone deliberately copies or migrates it there.
The garage and the road
Quick analogy worth keeping for this course: a production environment is the road, and a sandbox environment is your garage. The road has real traffic and real consequences — you don't bolt an untested part onto your car at 60 mph. The garage is where you can pull it apart, get it wrong, and start over without affecting anyone else.
This is exactly why you never make customizations directly in production first. You build and prove them out in a sandbox, then move them across once you're confident they work.
Trial environments
Alongside sandbox and production, you'll also encounter trial environments — temporary, time-limited instances Microsoft provisions so someone can explore Dynamics 365 CE without committing to a paid license.
- Behaves like a real environment — create records, build customizations, click around freely
- Expires after a set number of days unless converted to a paid subscription
- A common way developers and learners get their first hands-on experience
We'll come back to setting one up in the final chapter of this course.
Why companies have more than one environment
It's normal, even expected, for a company to run several environments side by side, each with a specific job:
| Environment type | Purpose |
|---|---|
| Development | Where developers build and experiment with new customizations, early and often, with the least fear of breaking anything important |
| Test / UAT (User Acceptance Testing) | A more controlled sandbox where a small group of real business users tries out changes before they go live, to confirm the changes actually meet their needs |
| Production | The live environment the whole organization relies on daily — the "road" |
Not every company needs all three — some small organizations get by with just a production environment and one sandbox. The underlying reasoning stays the same: more separation between "where we experiment" and "where real business happens" means less risk that a mistake in one disrupts the other.
Any customization work you do — forms, fields, automations, plugins — should always be built and proven in a sandbox before it ever touches production.