What's new: Match Production Database Configuration (2026 release wave 2)
Match Production Configuration is a new admin center button for sandbox environments, shipping in Business Central 2026 release wave 2. It temporarily matches a sandbox database to a typical production database configuration for 72 hours. It restarts the environment, can be used up to three times per tenant per calendar month, is supported in the admin center APIs, and is only available on paid license tenants, including the partner sandbox license.
- Feature overview and use cases
- Accessing the match production configuration button
- Flyout explanation and operation tracking
- Important considerations
- Limits, reversion, APIs, and licensing
- Conclusion
Overview
The video covers a sandbox feature that lets administrators temporarily match the configuration of a sandbox database to that of a typical production database. Developers and administrators can use it to see how processes run in a production-like setup, for example when developing apps, using the performance tool, or running cloud migration projects.
It shows the new “match production configuration” button in the admin center for sandbox environments and explains the flyout and how the operation is tracked. It also covers the limits: activating it restarts the environment and disconnects users, it lasts 72 hours, and it reverts automatically. It is supported through admin center APIs and requires a paid license type.
Key points
- The button is labeled match production configuration and appears in the admin center for sandbox environments only.
- Enabling it restarts the environment, so all connected users are disconnected.
- Each occurrence lasts 72 hours; the sandbox then returns to a typical sandbox configuration during the first environment update window.
- Limit: three occurrences per tenant per calendar month.
- Only available on tenants with a paid license type, including partners using the partner sandbox license.
- The operation can be tracked in the admin center like other operations, showing who started it, when, and the expected revert time.
- Admin center APIs support the operation, so it can be automated as part of development processes.
Features
| Feature | Status | At | Evidence |
|---|---|---|---|
| Match Production Configuration | generally available | 0:07 | “A new feature we’re shipping in 2026 release wave two.” (0:07) |
| Match Production Configuration Button | status not stated, demoed | 0:43 | |
| Operation Tracking for Configuration Matching | status not stated | 1:09 | |
| Admin Center APIs for Configuration Matching | status not stated | 1:59 |
Quotes
- 0:07 “A new feature we’re shipping in 2026 release wave two. With this feature administrators will be able to temporarily match the configuration of a”
- 0:23 “developers and administrators using the performance tool get developing apps or running cloud migration projects can mimic the configuration of a production database in”
- 0:56 “warns you that enabling this action will restart the environment meaning that any users that are connected to the environment at the time you”
- 1:43 “this operation is limited to three occurrences per tenant per calendar month for 72 hours at a time”
- 1:43 “Once those 72 hours end your sandbox environment automatically moves back to a typical sandbox configuration during the first environment update window”
- 2:13 “this is only available on tenants that have a paid license type, including partners that are using the partner sandbox license”