Use the settings catalog to configure settings on Windows, iOS/iPadOS, and macOS devices

Settings catalog lists all the settings you can configure, and all in one place. This feature simplifies how you create a policy, and how you see all the available settings. For example, you can use the settings catalog to create a BitLocker policy with all BitLocker settings.

You can also use Microsoft Copilot in Intune. When you use the Copilot features with the settings catalog, you can use Copilot to:

  • Learn more about each setting, get impact What If analysis, and find potential conflicts.
  • Summarize existing policies and get impact analysis on users and security.

If you prefer to configure settings at a granular level, similar to on-premises Group Policy Objects (GPOs), then the settings catalog is a natural transition to cloud-based policy.

When you create the policy, you start from scratch. You add only the settings you want to control and manage.

To manage and secure devices in your organization, use the settings catalog as part of your mobile device management (MDM) solution. More settings are continually being added to the settings catalog. For a list of the settings, go to the IntunePMFiles / DeviceConfig GitHub repository.

This feature applies to:

  • iOS/iPadOS

    Includes device settings that are directly generated from Apple Profile-Specific Payload Keys. More settings and keys are continually being added. To learn more about profile-specific payload keys, go to Profile-Specific Payload Keys (opens Apple's website).

    Apple's declarative device management (DDM) is built into the settings catalog. When you configure settings from the settings catalog on iOS/iPadOS 15+ devices enrolled using User Enrollment, you're automatically using DDM. If DDM doesn't work for any reason, then these devices use Apple's standard MDM protocol. All other iOS/iPadOS devices continue to use Apple's standard MDM protocol.

  • macOS

    Includes device settings that are directly generated from Apple Profile-Specific Payload Keys. More settings and keys are continually being added. To learn more about profile-specific payload keys, go to Profile-Specific Payload Keys (opens Apple's website).

    Apple's declarative device management (DDM) is available in the settings catalog. You can use DDM to manage software updates, passcode restrictions, and more.

  • Windows 10/11

    There are thousands of settings, including settings that weren't previously available. These settings are directly generated from the Windows configuration service providers (CSPs). You can also configure Administrative Templates, and have more Administrative Template settings available. As Windows adds or exposes more settings to MDM providers, these settings are added quicker to Microsoft Intune for you to configure.

Tip

This article lists the steps to create a policy, shows how to search and filter the settings in Intune, and shows how to use Copilot.

When you create the policy, it creates a device configuration profile. You can then assign or deploy this profile to devices in your organization.

For information on some features you can configure using the settings catalog, go to Tasks you can complete using the Settings Catalog in Intune.

Create the policy

You can create the policy using the settings catalog profile type.

  1. Sign in to the Microsoft Intune admin center.

  2. Select Devices > Configuration > Create.

  3. Enter the following properties:

    • Platform: Select iOS/iPadOS, macOS, or Windows 10 and later.
    • Profile type: Select Settings catalog.
  4. Select Create.

  5. In Basics, enter the following properties:

    • Name: Enter a descriptive name for the profile. Name your profiles so you can easily identify them later. For example, a good profile name is macOS: MSFT Edge settings or Win10: BitLocker settings for all Win10 devices.
    • Description: Enter a description for the profile. This setting is optional, but recommended.
  6. Select Next.

  7. In Configuration settings, select Add settings. In the settings picker, select a category to see all the available settings.

    For example, select Windows 10 and later, then select Authentication to see all the settings in this category:

    Screenshot that shows the Settings Catalog when you select Windows and Authentication in Microsoft Intune and Intune admin center.

    For example, select macOS. The Microsoft Edge - All category lists all the settings you can configure, including any new settings. The other categories include settings that are obsolete, or settings that apply to older versions:

    Screenshot that shows the Settings Catalog when you select macOS and select a feature or category in Microsoft Intune and Intune admin center.

    Tip

    • On macOS, the categories are temporarily removed. To find a specific setting, use the Microsoft Edge - All category, or search for the setting name. For a list of the setting names, go to Microsoft Edge - Policies.

    • Use the Learn more link in the tooltip to see if a setting is obsolete, and to see the supported versions.

  8. Select any setting you want to configure. Or, choose Select all these settings:

    Screenshot that shows the settings when you select all these settings in Microsoft Intune and Intune admin center.

    After you add your settings, close the settings picker. All the settings are shown, and configured with a default value, such as Block or Allow. These defaults values are the same default values in the OS. If you don't want to configure a setting, then select the minus:

    Screenshot that shows the Settings Catalog and that the default values in Microsoft Intune and Intune admin center are the same as the OS default values.

    When you select the minus (-):

    • Intune doesn't change or update this setting. The minus is the same as Not configured. When set to Not configured, the setting is no longer managed.
    • The setting is removed from the policy. The next time you open your policy, the setting isn't shown. You can add it again.
    • The next time devices check in, the setting is no longer locked. Another policy or device user can change the policy.

    Tip

    • In the Windows setting tooltips, Learn more links to the CSP.

    • When a setting allows multiple values, it's recommended to add each value separately.

      For example, you can enter multiple values in the Bluetooth > Services Allowed List setting. Enter each value on a separate line: Screenshot that shows a setting with multiple values on a separate line in the Settings Catalog in Microsoft Intune and the Intune admin center

      You can add multiple values in a single field, but you may experience a character limit.

  9. Select Next.

  10. In Scope tags (optional), assign a tag to filter the profile to specific IT groups, such as US-NC IT Team or JohnGlenn_ITDepartment. For more information about scope tags, see Use RBAC roles and scope tags for distributed IT.

    Select Next.

  11. In Assignments, select the users or groups that will receive your profile. For more information on assigning profiles, see Assign user and device profiles.

    Select Next.

  12. In Review + create, review your settings. When you select Create, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.

The next time the device checks for configuration updates, the settings you configured are applied.

Find some settings and learn more about each setting

There are thousands of settings available in the settings catalog. To help find the settings you want, you can use the search and filter features in the settings catalog.

If you use Copilot, then you can get AI generated information about each setting.

When you create a new policy or update an existing policy, there are built-in search and filter features to help you find settings.

  • In your policy, to find specific settings, you can use Add settings > Search. You can search by category, such as browser, search for a keyword, such as office or google, and search for specific settings.

    For example, search for internet explorer. All the settings with internet explorer are shown. Select a category to see the available settings:

    Screenshot that shows the Settings Catalog when you search for Internet Explorer to see all the IE settings in Microsoft Intune and Intune admin center.

  • In your policy, use Add settings > Add filter. Select the key, operator, and value.

    When you filter on OS Edition, you can filter the settings that apply to specific Windows editions:

    Screenshot that shows the Settings Catalog when you filter the settings list by Windows edition in Microsoft Intune and Intune admin center.

    Note

    For the Edge, Office, and OneDrive settings, the OS version or edition doesn't determine if the settings apply. So, if you filter to a specific edition, like Windows Professional, then the Edge, Office, and OneDrive settings aren't shown.

    You can also filter the settings by device or user scope. For more information on user scope and device scope, go to Device scope vs. user scope settings (in this article):

    Screenshot that shows the user and device scope filter in the settings catalog in Microsoft Intune and Intune admin center.

Copy a profile

Select Duplicate to create a copy of an existing profile. Duplicating is useful when you need a profile that's similar yet distinct from the original one.

The copy contains the same setting configurations and scope tags as the original profile, but doesn't have assignments attached to it. After you give the new profile a name, you can edit the profile to adjust the settings and add assignments.

  1. Go to Devices > Configuration.
  2. Find the profile that you want to copy. Right-click the profile or select the ellipses context menu ().
  3. Select Duplicate.
  4. Enter a new name and description for the policy.
  5. Save your changes.

Import and export a profile

This feature applies to:

  • Windows 10 and later

When you create a settings catalog policy, you can export the policy to a .json file. You can then import this file to create a new policy. This feature is useful if you want to create a policy that's similar to an existing policy. For example, you export a policy, import it to create a new policy, and then make changes to the new policy.

  1. Go to Devices > Configuration.

  2. To export an existing policy, select the profile > select the ellipsis context menu () > Export JSON:

    Screenshot that shows how to export a settings catalog policy as JSON in Microsoft Intune and Intune admin center.

  3. To import a previously exported settings catalog policy, select Create > Import policy:

    Screenshot that shows how to import an existing settings catalog policy in Microsoft Intune and Intune admin center.

    Select the JSON file you exported and name your new policy. Save your changes.

Conflicts and reporting

Conflicts happen when the same setting is updated to different values, including policies configured using the settings catalog. In the Intune admin center, you can check the status of your existing policies. The data refreshes automatically, and operates in near real time.

There are built-in features that can help you troubleshoot conflicts, including per-setting status reporting.

If you use Copilot, then you can use some built-in prompts to get more information on existing policies, including their impact.

In the Intune admin center, you can use the built-in reporting features to help find and resolve conflicts.

  1. In the Intune admin center, select Devices > Configuration. In the list, select the policy you created using the Settings Catalog. The Profile type column shows Settings Catalog:

    Screenshot that shows how to open the settings catalog in Microsoft Intune and Intune admin center.

  2. When you select the policy, the device status shows. It shows a summary of your policy state and the policy properties. You can also change or update your policy in the Configuration settings section:

    Screenshot that shows how to select the settings catalog policy to see the device status, policy state, and properties in Microsoft Intune and Intune admin center.

  3. Select View report. The report shows detailed information, including the device name, the policy status, and more. You can also filter on the deployment status, and Export the report to a .csv file:

    Screenshot that shows how to see detailed report information in Microsoft Intune and Intune admin center, including device name, policy status, and more.

  4. You can also look at the states of each setting using the per-setting status. This status shows the total number of devices affected by each setting in the policy.

    You can:

    • See the number of devices with the setting successfully applied, in conflict, or in error.
    • Select the number of devices in compliance, conflict, or error. And, see a list of users or devices in that state.
    • Search, sort, filter, export, and go to the next and previous pages.
  5. In the admin center, select Devices > Monitor > Assignment failures. If your Settings Catalog policy failed to deploy because of an error or conflict, it shows in this list. You can also Export to a .csv file.

  6. Select the policy to see the devices. Then, select a specific device to see the setting that failed, and a possible error code.

Tip

Intune reports is a great resource, and describes all the reporting features you can use. For information on all the reporting data you can view, go to Intune reports.

For more information on conflict resolution, go to:

Settings catalog vs. templates

When you create the policy, you have two policy types: Settings catalog and Templates:

Screenshot that shows when you create a Windows or macOS policy, select settings catalog or templates in Microsoft Intune and Intune admin center.

The Templates include a logical group of settings, such as kiosk, VPN, Wi-Fi, and more. Use this option if you want to use these groupings to configure your settings.

The Settings catalog lists all the available settings. If you want to see all the available Firewall settings, or all the available BitLocker settings, then use this option. Also, use this option if you're looking for specific settings.

Device scope vs. user scope settings

When you select a setting, some settings have a (User) tag or (Device) tag in the setting name, such as Allow EAP Cert SSO (User) or Grouping (Device). When you see these tags, the policy only affects the user scope or the device scope.

For more information on user scope and device scope, see the Policy CSP.

Device and user groups are used when you assign your policies. Device and user scopes describe how a policy is enforced.

Scope assignment behavior

When deploying policy from Intune, you can assign user scope or device scope to any type of target group. Behavior of the policy per user depends on the scope of the setting:

  • User scoped policy writes to HKEY_CURRENT_USER (HKCU).
  • Device scoped policy writes to HKEY_LOCAL_MACHINE (HKLM).

When a device checks in to Intune, the device always presents a deviceID. The device might or might not present a userID, depending on the check-in timing and if a user is signed in.

The following list includes some possible combinations of scope, assignment, and the expected behavior:

  • If a device scope policy is assigned to a device, then all users on that device have that setting applied.
  • If a device scoped policy is assigned to a user, once that user signs in and an Intune sync occurs, then the device scope settings apply to all users on the device.
  • If a user scope policy is assigned to a device, then all users on that device have that setting applied. This behavior is like a loopback set to merge.
  • If a user scoped policy is assigned to a user, then only that user has that setting applied.
  • There are some settings that are available in the user scope and the device scope. If one of these settings is assigned to both user and device scope, then user scope takes precedence over device scope.

If there isn't a user hive during initial check-ins, then you can see some user scope settings marked as not applicable. This behavior happens in the early moments of a device before a user is present.

Next steps