What's new: Match Production Database Configuration

This video covers a new admin center action in 2026 release wave two that temporarily matches a sandbox database configuration to that of a typical production database. It is meant for developers and administrators who want to check performance or run cloud migration projects under production-like conditions. The video shows the new button, the flyout warning about a restart, and how to track the operation. It then lists the limits: three uses per tenant per calendar month, 72 hours each, an automatic revert, admin center API support, and a paid license requirement.

Watch: https://www.youtube.com/watch?v=HixajKEd-A4 (2:43). Area: Admin and platform. Audience: admin, developer, partner. Presenters as heard: not introduced by name.

Chapters

• 0:00 Overview: matching sandbox to production configuration (1 min)
• 0:43 Admin center button, flyout and operation tracking (1 min)
• 1:29 Limits: three times per month, 72 hours each (1 min)
• 1:59 Automatic revert, admin center API and license requirement (0 min)
• 2:24 Wrap-up (0 min)

Features in this video

• Match production configuration - GA - 0:07 to 0:56, demo 0:43 to 0:56 - Administrators can temporarily match a sandbox database configuration to a typical production database.
• Restart warning flyout - GA - 0:56 to 1:09, demo 0:56 to 1:09 - The admin center button opens a flyout explaining the action and warning that the environment restarts.
• Automatic revert after 72 hours - GA - 1:09 to 2:13 - The environment reverts to a typical sandbox configuration after 72 hours.
• Match production operation tracking - GA - 1:09 to 1:29, demo 1:09 to 1:29 - The operation can be tracked like other admin center operations.
• Match production usage limit - GA - 1:43 to 1:59 - The operation is limited to three occurrences per tenant per calendar month, each lasting 72 hours.
• Match production in admin center API - GA - 1:59 to 2:24 - The match production configuration operation is supported in the admin center APIs.
• Match production paid license requirement - GA - 2:13 to 2:24 - The feature is only available on tenants with a paid license type.

Quotes

• 0:07 "A new feature we're shipping in 2026 release wave two." - Places the feature in the 2026 release wave two timeline.
• 0:23 "can mimic the configuration of a production database in their sandbox environment to evaluate how processes would run in a typical production environment" - States the core purpose: testing production-like behavior in a sandbox.
• 0:56 "any users that are connected to the environment at the time you do this will be disconnected" - Warns that running the action disrupts connected users.
• 1:09 "your environment will automatically revert back to a typical sandbox configuration after 72 hours" - The production-like configuration is temporary, with a fixed 72-hour duration.
• 1:43 "this operation is limited to three occurrences per tenant per calendar month for 72 hours at a time" - Gives the hard usage limit that affects how teams plan their testing.
• 1:59 "during the first environment update window after those 72 hours end" - The revert happens at the next update window, not exactly at the 72-hour mark.
• 1:59 "this operation is also supported in the admin center APIs, so for developers that are automating" - Developers can script the operation in their pipelines.
• 2:13 "this is only available on tenants that have a paid license type, including partners that are using the partner sandbox license." - Sets the license prerequisite, including for partners.

Disclaimers and status moments

• 0:07 other: "A new feature we're shipping in 2026 release wave two."

Documented features matched

• none of the features in this video matched an item in the documented features baseline