Unchangeable configurations

There are Configuration Types and configurations where certain changes cannot be performed through Configuration Manager. 

You can identify them because their checkboxes are greyed out in Configuration Manager. 

Why this restriction?

While Configuration Manager can create, delete, and update most supported configurations, not all changes can be made to all configurations. This restriction often arises because Microsoft does not permit alterations to certain default configurations within every tenant. Configuration Manager backs up any supported configuration it can access from your tenant, but it might not have the capability to update or delete everything.

For example, some defaults cannot be deleted, even directly through Microsoft's portal. Alternatively, some configurations can have their properties changed or updated, but cannot be created or deleted in a tenant. 

In any case, hovering over the grey checkboxes will display a red warning indicating that the action of that checkbox cannot be performed, and providing further explanation regarding the limitations.

How can I hide/unhide unchangeable configurations?

To focus on configurations you can manage, Configuration Manager provides a checkbox to hide/unhide unchangeable configurations.

In the left bar, under the "By classification:" section, you will find a checkbox labeled “Unchangeable ”.                           
By enabling this checkbox, all configurations will be displayed in the comparison results list.                          
Conversely, when the checkbox is disabled, the unchangeable configurations will not be visible.

Configurations that cannot be managed: table

The table below outlines configurations that cannot be managed from the Reconcile page. These limitations are categorized into three designations: configurations that cannot be created, deleted, or updated. While these specific terms do not appear in the application interface (nor in Azure DevOps), they are used here to clearly illustrate the operational constraints of each configuration type.

• Can’t be created: configurations that cannot be created from scratch in a tenant where they’re not present, or configurations that are already available by default in every Microsoft tenant.

Example: if a baseline tenant has a configuration marked as “Can’t be created”, it cannot be imported into a downstream tenant that does not have that configuration.

• Can’t be deleted: configurations that cannot be deleted from a tenant. 

Example: if a configuration marked as "Can’t be deleted" was created directly in the M365 tenant, it cannot be removed to revert to a previous state.

• Can’t be updated: configurations that cannot be modified once they are present in Configuration Manager. 

For example,  If a configuration marked as "Can't be updated" was altered directly in the Microsoft 365 tenant, you cannot revert to the previous version.