Recommended limit for number of Compliance Policies in Intune to avoid performance or sync issues?

Question

Hello,

I’m looking for guidance on how many Compliance Policies it’s safe to assign to a single device or user in Microsoft Intune without degrading endpoint performance or causing synchronization failures.

Background:

• We manage dozens of Compliance Policies (BitLocker, Cisco Secure Client, biometric login, etc.) across our environment.

Recently, we observed that devices with a high number of assigned policies sometimes take significantly longer to evaluate compliance and occasionally fail to sync with Intune.

There doesn’t appear to be any official documentation from Microsoft outlining a hard limit or recommended best practice for the maximum number of policies per device/user.

Questions:

Does Microsoft publish any guidance or best-practice limits on the number of Compliance Policies that can be targeted to a single device or user?

Have other organizations observed performance degradation, longer compliance evaluation times, or sync errors when assigning large numbers of policies?

What design recommendations would you suggest to optimize policy assignments and avoid potential “overloading” effects?

Thank you in advance for any insights or links to official documentation!

Answer 1

Hi Jakub Kamrowski (J)

Longer compliance evaluation times can be encountered based on how large the Intune environment is. These recommendations focus on improving performance and reducing latency in workload assignment. They have the most impact when working in large Intune environments, like environments with >100,000 devices. The recommendations should be considered with other design aspects, like manageability, ease of use, role-based administration, and simplicity.

Performance recommendations for grouping, targeting, and filtering in large Microsoft Intune environments

Key takeaways include:

• Reuse groups: Avoid duplicating groups for different policies. Instead, reuse existing groups to reduce processing overhead.
• Use filters: Filters allow you to narrow policy scope dynamically at check-in time, reducing the need for complex group logic.
• Avoid over-targeting: Assigning too many policies to the same device or user can increase latency and evaluation time.
• Prefer virtual groups: Use built-in groups like “All devices” or “All users” when possible, as they are optimized for performance.

If you find the answer above helpful, please "Accept the answer" to help anyone in the community who might have a similar question to quickly find the solution.