Promote sandbox updates

Use a sandbox to safely make changes to your production tenant:

  1. Create a sandbox before making configuration changes to your tenant.

  2. Access the sandbox, and then make configuration changes to your tenant. Run the updated workflow from within the sandbox, run sandbox validations, and verify that your changes are ready for promotion.

  3. Promote configuration changes (this topic) to your production tenant.

    Tip

    You can automatically delete a sandbox using the Promote and delete sandbox option when promoting changes from a sandbox to production.

This is part three of a series of topics that describes how your brand can use sandboxes to safely make changes to your production tenant.

Note

Users who have been assigned the DataGrid Operator or DataGrid Administrator policies, and then assigned the Allow sandbox administration policy option, are allowed to create sandboxes and promote changes to production from a sandbox.

The following sections describe the steps you’ll follow when promoting changes in a sandbox to production.

Step 1.

Open the sandbox from which you want to promote configuration state changes.

Access a sandbox that is ready to promote changes.
Step 2.

A series of validations are run against updates. These validations will notify you within the sandbox when the configuration states of production and sandbox conflict.

Most of the time you should receive a validation report that does not contain a list of conflicts, similar to:

All validations passed.

Occasionally, you will receive a validation report that shows one (or more) validation errors. For example, a schema mismatch between a custom domain table in production and a custom domain table in the sandbox:

Some validations passed, but there is a schema error.

If you receive a validation report with errors, investigate each error and work to resolve the underlying issue. It is possible that resolution must be done in the production tenant before pulling updates to the sandbox. It is also possible that the resolution is done in the sandbox. It depends on the error.

Step 3.

When configuration state changes in a sandbox are ready for promotion to production, the sandbox-specific notifications will provide a link named “Ready to promote”.

Review the details for each update.
Step 4.

Review the list of Added, Changed, and/or Removed configuration state changes. Click the name of the added, changed, or removed object to review the details for the configuration state change.

Resolve validation issues, as necessary.

Review the details for each update.
Step 5.

Enter a merge message for this set of configuration state changes.

Review the details for each update.

When the sandbox is ready to be promoted, click Promote.

Tip

You can automatically delete a sandbox using the Promote and delete sandbox option when promoting changes from a sandbox to production.

Step 6.

After the updates are safely running in production, you should delete the sandbox.

Delete a sandbox after configuration state changes are promoted.