Edit

Common questions, answers, and scenarios with policies and profiles in Microsoft Intune

  • Article

Important

On October 22, 2022, Microsoft Intune ended support for devices running Windows 8.1. Technical assistance and automatic updates on these devices aren't available.

If you currently use Windows 8.1, then we recommend moving to Windows 10/11 devices. Microsoft Intune has built-in security and device features that manage Windows 10/11 client devices.

Get answers to common questions when working with policies in Intune. This article also lists the check-in time intervals, provides more detains on conflicts, and more.

This article applies to the following policies:

  • App protection policies
  • App configuration policies
  • Compliance policies
  • Conditional access policies
  • Device configuration profiles
  • Enrollment policies

Policy refresh intervals

Intune notifies the device to check in with the Intune service. The notification times vary, including immediately up to a few hours. These notification times also vary between platforms. On Android devices, Googe Mobile Services (GMS) can affect policy refresh intervals.

If a device doesn't check in to get the policy or profile after the first notification, Intune makes three more attempts. An offline device, such as turned off, or not connected to a network, might not receive the notifications. In this case, the device gets the policy or profile on its next scheduled check-in with the Intune service. The same applies to checks for noncompliance, including devices that move from a compliant to a noncompliant state.

Estimated frequencies:

Platform Refresh cycle
Android, AOSP About every 8 hours
iOS/iPadOS About every 8 hours
macOS About every 8 hours
Windows 10/11 PCs enrolled as devices About every 8 hours
Windows 8.1 About every 8 hours

If devices recently enroll, then the compliance, noncompliance, and configuration check-in runs more frequently. The check-ins are estimated at:

Platform Frequency
Android, AOSP Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours
iOS/iPadOS Every 15 minutes for 1 hour, and then around every 8 hours
macOS Every 15 minutes for 1 hour, and then around every 8 hours
Windows 10/11 PCs enrolled as devices Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours
Windows 8.1 Every 5 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours

For app protection policy refresh intervals, go to App Protection Policy delivery timing.

At any time, users can open the Company Portal app, Devices > Check Status or Settings > Sync to immediately check for policy or profile updates. For related information about the Intune Management Extension agent or Win32 apps, see Win32 app management in Microsoft Intune.

Intune actions that immediately send a notification to a device

There are different actions that trigger a notification. For example, when a policy, profile, or app is assigned (or unassigned), updated, deleted, and so on. These action times vary between platforms.

Devices check in with Intune when they receive a notification to check in, or during the scheduled check-in. When you target a device or user with an action, then Intune immediately notifies the device to check in to receive these updates. For example, a notification happens when a lock, passcode reset, app, or policy assignment action runs.

Other changes don't cause an immediate notification to devices, including revising the contact information in the Company Portal app or updates to an .ipa file.

The settings in the policy or profile are applied at every check-in. A Windows 10 MDM policy refresh customer blog post might be a good resource.

Conflicts

Conflicts can happen when different policies update the same setting to different values. For example, you have two policies that update the copy/paste setting to different values. The conflict is handled differently depending on the type of policy.

App protection policies that conflict

Conflict values are the most restrictive settings available in an app protection policy. The exception is numeric entry fields, such as PIN attempts before reset. Numeric entry fields are set the same as the values, as if you created a MAM policy using the recommended settings option.

Conflicts happen when two profile settings are the same. For example, you configured two MAM policies that are identical except for the copy/paste setting. In this scenario, the copy/paste setting is set to the most restrictive value. The rest of the settings apply as configured.

A policy is deployed to the app and takes effect. A second policy is deployed. In this scenario, the first policy takes precedence, and stays applied. The second policy shows a conflict. If both are applied at the same time, meaning that there isn't preceding policy, then both are in conflict. Any conflicting settings are set to the most restrictive values.

Compliance and device configuration policies that conflict

When two or more policies are assigned to the same user or device, then the setting that applies happens at the individual setting level:

  • If you use custom compliance policies to set device settings, then the settings within the custom compliance policy take precedence over the same setting within device configuration policies. Compliance policy settings always have precedence over configuration profile settings.

  • If a compliance policy evaluates against the same setting in another compliance policy, then the most restrictive compliance policy setting applies.

  • If a configuration policy setting conflicts with a setting in another configuration policy, this conflict is shown in Intune. Manually resolve these conflicts.

In the Intune admin center, there are a few places you can create configuration policies, including Group Policy analytics, endpoint security, security baselines, and more. If there's a conflict and you have multiple policies, then check all the places you configured policies. Also, the built-in reporting features can help with conflicts. For more information on the available reports, go to Intune reports.

Custom iOS/iPadOS or macOS policies that conflict

Intune doesn't evaluate the payload of Apple Configuration files or a custom Open Mobile Alliance Uniform Resource Identifier (OMA-URI) policy. It merely serves as the delivery mechanism.

When you assign a custom policy, confirm that the configured settings don't conflict with compliance, configuration, or other custom policies. If a custom policy and its settings conflict, then Apple randomly applies the settings.

The built-in reporting features can help with conflicts. For more information on the available reports, go to Intune reports.

A profile is deleted or no longer applicable

When you delete a profile, or remove a device from a group that's assigned the profile, then the profile and settings are removed from the device. Specifically, they're removed as described in the following list:

  • Wi-Fi, VPN, certificate, and email profiles: These profiles are removed from all supported enrolled devices.

  • All other profile types:

    • Android devices: Settings aren't removed from the device.

    • iOS/iPadOS: All settings are removed, except:

      • Allow voice roaming
      • Allow data roaming
      • Allow automatic synchronization while roaming

    • Windows devices: After you remove or unassign the profile, have the Microsoft Entra user sign in to the device, and sync with the Intune service.

      Intune settings are based on the Windows configuration service provider (CSPs). The behavior depends on the CSP. Some CSPs remove the setting, and some CSPs keep the setting, also called tattooing.

  • A profile applies to a user group. Later, a user is removed from the group. For the settings to be removed from that user, it can take up to 7 hours or more for:

    • The profile to be removed from the policy assignment in the Intune admin center
    • The device to sync with the Intune object using the platform-specific policy refresh cycle (in this article)

I changed a device restriction profile, but the changes haven't taken effect

To apply a less restrictive profile, some devices might need to be retired and re-enrolled in to Intune. For example, you might have to retire and re-enroll Android, iOS/iPadOS, and Windows client devices.

Some settings in a Windows 10/11 profile return "Not Applicable"

Some settings on Windows client devices can show as Not Applicable. When this situation happens, that specific setting isn't supported on the Windows version or edition running on the device. This message can occur for the following reasons:

  • The setting is only available for newer versions of Windows, and not the current operating system (OS) version on the device.
  • The setting is only available for specific Windows editions or specific SKUs, such as Home, Professional, Enterprise, and Education.

To learn more about the version and edition requirements for the different settings, see the Configuration Service Provider (CSP) reference.

When devices enroll, there's a delay in applying apps and policies assigned to dynamic device groups

During enrollment, you can use Microsoft Entra dynamic device groups. For example, you can create a dynamic device group based on a device's name or enrollment profile.

The enrollment profile is applied to the device record during initial device setup. Microsoft Entra dynamic grouping isn't instant. The device might not be in the dynamic group for some time, possibly minutes to hours depending on other changes being made in your tenant.

If the device isn't added to the group, then your apps and policies aren't assigned to the device during the initial Intune check-in. The policies might not apply until the next scheduled check-in.

If fast delivery of apps and policies is important to your setup/enrollment scenario, then assign your apps and policies to user groups, not dynamic device groups. User groups are pre-populated with members before device setup and don't have this delay.

For more information on dynamic groups, go to:

Next steps