A skipped configuration is a configuration that Configuration Resilience could not process as requested—either during a read operation (backup) or during a deployment.
Where skipped configurations are displayed
Skipped configurations are marked with a yellow clockwise arrow icon, which can appear in two places:
| Location | What it means |
|---|---|
| Next to a configuration | Configuration Resilience was unable to read that configuration. |
| Next to the Last Update badge | Configuration Resilience could not retrieve the current status during the most recent backup. |
You can’t view the property-level of a skipped configuration because the system couldn’t read it.
Monitoring page
On the Monitoring page, the “Skipped” icon appears next to the “Last update” indicator in case of skipped configurations. To see which configurations were skipped for each scope, open the Change history panel.
Change history panel
- On the Monitoring page, select a scope from the left side list.
- Click on the “Change history” icon on the blue scope bar to open the Change history panel.
- In the Change history panel, click on the record to see details of the skipped configuration.
Restore configurations, Baseline alignment and Tenant alignment pages
On the Restore configurations page, Baseline alignment page, and Tenant alignment page, you can review skipped configurations from the list of configurations.
A “Skipped” filter is available to sort skipped configurations in a single list for easier review and troubleshooting.
Deploy history panel
On the Deploy history panel, skipped writes (if any) are flagged on the deployment record lines. Select a record to view details about the skipped configuration, including the proposed change visually indicated by a grey badge.
How skipped configurations are resolved
Skipped backup
Skipped configurations usually resolve automatically at the next scheduled read. They can occur for reasons on Microsoft's side. If the same configuration is skipped for more than two backups, open a support request and include the operation ID:
- Open “Change history”
- Select the skipped property value
- Open the “Details” tab to find the operation ID
- Click on the “Copy” icon next to the ID for easier reporting
Skipped deploy
If configurations are skipped during a deploy, administrators must retry the deployment manually. If the same configuration is skipped for more than two deploys, a banner shows a possible explanation of what caused the error. Open a support request and include the operation ID:
- Open “Deploy history”
- Select the skipped property value
- Open the “Details” tab to find the operation ID
- Click on the “Copy” icon next to the ID for easier reporting