Use this section to compare the current configuration state of your target tenant against a selected reference tenant and determine what to align.
You cannot start a new deployment while the tenant status is “Pending approval”, “Running deploy”, or “Propagating”. Wait until the current deployment is completed or cleared.
Which tenants you can compare
The tenants you can view and compare depend on the CoreView user you are signed in with:
- If you are signed in as an administrator of a child tenant only, the parent tenant is not listed, and you can't align your tenant to it.
- If you are signed in as an administrator in the parent tenant, you can visualize and align every child tenant.
View differences
Select a configuration and click “View” to open its details, including its properties and their values.
The information shown depends on the alignment state:
| Alignment status | What you see |
|---|---|
| Conflicting | All properties are shown. For properties that have changed, both the reference and current values are displayed. Turn on the “Show differences” toggle to highlight the changes in color, or turn it off to view all properties without highlighting. Use the “Select all” buttons to highlight every difference in the list at once. |
| Only in reference | Only the property values from the reference tenant are shown. |
| Aligned | The properties and their current values are shown. |
| Only in target tenant | Only the current property values are shown. |
Alignment actions
Alignment actions allow you to bring your tenant's configurations in the same state as the reference tenant.
The available actions depend on the alignment state of the configuration:
Conflicting
You can conform configurations whose values differ from the reference tenant. Use “Align” to make the current values in line with the reference tenant.
Only in reference
You can align configurations that exist in the reference tenant but are not present in the current state of your tenant. Use “Add” to add the configurations to your tenant.
Only in target tenant
You can remove configurations that exist in the current state of your tenant but are not present in the reference tenant. Use “Remove” to delete the configurations from the tenant.
When the “Unchangeable” label is is displayed, alignment isn’t supported because Microsoft’s APIs don’t allow changes to this configuration. To align it, you must use the Microsoft portal.
Review selected changes and deploy
When you select an alignment action, the change is added to a preview area together with any other pending changes.
You can select and deploy alignment actions for one scope at a time. If you switch between scopes, the changes preview will clear up.
Nothing is applied automatically, and no changes are written to the tenant at this stage. Selected changes:
- Stay in the preview area until you confirm them by clicking “Deploy”.
- Are applied to the tenant only after an administrator approves them.
Review property by property
Click the expand icon to open the preview area and see exactly what will change.
Select a Configuration Type from the left sidebar, then select a configuration to review its changes at property level. Each property value is marked to show the requested change:
- Adding: the value that will be added.
- Removing: the value that will be removed.
- Changing: the current value, shown as “Old value”, and the new value, shown as “New value”.
For each selected change, Configuration Resilience checks whether the configuration has dependencies. If any are found, it flags them. These dependencies will be included in the deployment and cannot be excluded.
Add a note
Before submitting, click the clipboard icon to add an optional note for the administrator who will approve the changes, for example to explain why the change is needed.
Discard the changes
Select “Clear all” to remove all changes from the preview area.
Deploy
Click “Deploy” to submit the changes for approval.
The tenant status changes to “Pending approval”, and the approving administrator receives an email notification to approve or discard the changes. The changes are applied to the tenant only after approval.
After approval
When a deployment is approved, the tenant status changes to “Running Deploy”.
Processing time varies according to the dependency count and the number of configuration changes included in the deployment. When processing finishes, the tenant status changes to “Ready”.
