When a user submits changes from Configuration Resilience, the changes are not applied to the tenant until an administrator approves them.
As an administrator, you can:
- Review the pending changes.
- Approve or discard the changes.
- Check the result of the deployment.
Setup email to receive notifications
You can enable email notifications whenever the tenant status changes to “Pending approval”:
- Log into CoreView
- Browse through Settings (left sidebar) > Organization settings > Configuration resilience
- Turn on the “Send pending approval emails” toggle
- Add your email address. Use a comma (,) between email addresses to enter multiple recipients
- Click “Save”
Open the review page
When changes are submitted, the tenant status changes to “Pending approval” and you receive an email notification.
While changes are “Pending approval”, no other deployment can be submitted on the tenant.
To open the review page, click “Review changes” in the email. The review page shows a summary of all the proposed changes.
Check who requested the changes
In the Details section, you can see who submitted the changes and read the note they added, if any. The note usually explains why the changes are needed.
Approve or discard the changes
You can handle the proposed changes in one of the following ways:
| Action | Description |
|---|---|
| Approve all changes | Click “Approve and deploy” to approve and deploy all changes at once, without reviewing them individually. |
| Review changes individually | Review each change and choose which ones to keep and which ones to discard. |
| Discard all changes | Click “Discard changes” to reject all the proposed changes. Discarded changes are listed in the “Discarded changes” section. To restore a discarded change, hover over the configuration and click the Restore icon (a clockwise circular arrow). |
After approval
- Once you approve the changes, the tenant status changes to “Running deploy”. The deployment can take from a few minutes to a few hours, depending on the number of changes and dependencies involved. For example, changing many Conditional Access Policies at once in a large tenant takes longer. Deployments are expected to complete within 24 hours: if the tenant status remains in Running Deploy for more than 24 hours, open a support request and include the operation ID.
- The tenant status then changes to "Propagating", meaning that Microsoft 365 is applying changes with eventual consistency. The update may take some time to become visible. If the “Propagating” status exceeds these estimated times, open a support request and include the operation ID.
- When the propagation is complete, the tenant status returns to “Ready”.
Check the deployment result
The result of each deployment is recorded in Deploy history, which is separate from Change history:
| History | What it records |
|---|---|
| Change history | Changes detected by Configuration Resilience reads, made directly in the tenant, for example from the Microsoft 365 admin center or through an Azure pipeline. |
| Deploy history | Changes deployed from CoreView by CoreView users. |
Deploy history uses the same status icons as the rest of Configuration Resilience. Changes are tracked in three separate categories:
- Add: a configuration was added to the tenant.
- Remove: a configuration was removed from the tenant.
- Change: one or more property values of an existing configuration were modified.
A yellow clockwise arrow icon indicates a skipped write: one or more changes in the deployment could not be completed by Microsoft, while others may have succeeded. Select the item to see the intended change and whether it was an Add, a Remove, or a Change. You can retry it later.