
Some environments have a few large configuration policies with a lot of settings in each. Others split almost everything into separate policies.
I’ve worked with both, and honestly, neither approach is automatically right or wrong. The important question is when settings should stay together and when it makes sense to split them.
The short version: keep settings together when they belong together, serve the same purpose and share the same assignment. Split them when one of those things changes.
For me, it’s less about how many settings a policy contains and more about how I expect to manage it later.
Topics in this post
- The policy size question
- Why large Intune policies are tempting
- So should you create many small policies instead?
- How I decide when to split a policy
- Think about assignments
- A simple rule I use
- Naming convention
- My take
- Useful links
The policy size question
This question isn’t new or unique to Intune. We have been having similar discussions for years with Group Policy, Configuration Manager and now Intune.
There are benefits to both approaches, and unfortunately there isn’t a simple answer. If you came here looking for the ultimate recommendation, I’m sorry. But hopefully we can get a bit closer to answering the question:
Should I create one large policy with many settings, or split the configuration into several smaller policies?
Why large Intune policies are tempting
Large policies mean fewer objects in Intune, fewer assignments and more settings kept in one place. They are also easier to set up when initially building the environment. But for me, this is where the trouble starts. Let me give you an example.
Let’s take Edge settings as an example. We create one large policy for Microsoft Edge that includes security settings, personalization, start page, sync options, favorites and so on. This works well until we need different settings based on persona or department.
To solve this, many customers I talk to create exclusions for the original Edge policy, duplicate the policy and then change the settings needed for that specific use case.
Do you see the problem?
The real problem isn’t just having more policies. It’s having multiple copies of the same configuration that can slowly start to drift apart. A setting gets changed in one policy but not the other, and suddenly two policies that were supposed to be almost identical no longer are.
So should you create many small policies instead?
Not always.
One benefit is that smaller policies can make things easier, especially when you are troubleshooting or need different assignments.
But I have also seen environments where this has gone too far.
You start with a good idea of separating things, and after a while you have so many policies that it becomes difficult to understand what is actually configuring the device.
Every policy becomes another object to name, assign and troubleshoot. If five settings always belong together, have the same assignment and are managed as one configuration, splitting them into five separate policies doesn’t necessarily give you anything. It can just create more objects to manage.
Personally, I don’t think there is anything wrong with having several settings in the same policy. But there is one thing that is always in the back of my mind:
Do these settings really belong together?
For me, the number of settings isn’t really the important part. It’s about finding a good balance between keeping a clear overview and having enough flexibility to adapt the configuration later.
How I decide when to split a policy
My approach is to split policies based on the purpose of the configuration. Let’s take Edge as an example again. I usually split the configuration into logical areas and then make the specific purpose clear in the name. For example:
Windows – Edge – Security – Restrictions
Windows – Edge – Security – Add-ons
Windows – Edge – Personalization – Startup
Windows – Edge – Personalization – Favorites
Windows – Edge – Personalization – Sync
By splitting the configuration like this and sticking to a consistent naming convention, it’s easier to change or duplicate a specific part when needed without affecting everything else. The policy names also become almost self-documenting.
Troubleshooting is another reason I prefer smaller, logical policies over one large policy. When something doesn’t behave as expected, one of the first things I want to know is which policy is responsible.
If all the Edge settings live in one large policy, I need to dig through it to find the setting that matters.
If the configuration is split by function, the policy name already points me in the right direction. A problem with the start page leads me to Personalization – Startup, while I can leave the security policies alone.
Think about assignments
Another thing I consider when deciding whether settings should stay together is the assignment.
If two groups of settings always target the same users or devices, keeping them together might make perfect sense. A good example could be the main security settings for Edge. But if I can already see that one part of the configuration may need a different assignment later, that’s usually a good reason for me to separate it.
For me, the assignment is often a better reason to split a policy than the number of settings in it.
Assignment filters can also help make targeting more flexible without creating additional groups. I’ve written more about how I use them in Assignment Filters in Microsoft Intune: Why They Matter More Than Ever.
A simple rule I use
When I’m deciding whether settings should stay in the same policy, I usually ask myself three questions:
1. Do they serve the same purpose?
Settings that are part of the same configuration or function usually make sense together.
2. Do they have the same assignment?
If some settings need to target different users or devices, I would normally split them.
3. Would I want to change or create an exception for them separately?
If the answer is yes, separating them now can save me from duplicating a large policy later.
That doesn’t mean I try to predict every possible exception.
If I did, I would probably end up with far too many policies. I usually separate things when there is a realistic reason why the assignment or configuration might need to change independently.
So my rule is pretty simple:
Same purpose + same assignment + managed together = keep them together.
Different purpose, assignment or exception = consider splitting them.
Naming convention
Over the years working with Intune, my view on naming conventions has changed quite a bit. And when working in customer environments, it’s not always up to me to decide how things should be named.
But one thing has always been important to me:
The name should tell us, as administrators, what the policy does without having to open it.
I normally like names that roughly follow this structure:
Platform – Product/Area – Purpose – Configuration
For example:
Windows – Edge – Security – Restrictions
Windows – Edge – Personalization – Favorites
I’m not saying this exact naming convention is right for every environment. The important part is that it is predictable.
If I have to open a policy called Windows Policy 01 to understand what it does, the name isn’t helping me very much.
This becomes even more important when you start splitting settings into smaller policies. More policies mean more names to keep track of, so a simple and predictable naming convention becomes essential.
My take
I don’t think the goal should be to have as few policies as possible, and I don’t think creating a separate policy for every setting is the answer either.
My approach is pretty simple: group settings that belong together, serve the same purpose and are likely to be managed and assigned together.
If the purpose, assignment or exception requirements change, I start thinking about splitting the policy.
There is no magic number of settings that makes an Intune policy too large. A policy with 50 settings that all belong together can make more sense than five policies with 10 settings each.
In the end, I would rather manage a few more clearly named policies than start duplicating large policies every time I need an exception.
Structure policies around how you manage them, not around how many settings they contain.
How do you structure your policies?
Leave a comment below!
Useful links
Device configuration – settings catalog – Microsoft Learn
Intune fundamentals filters overview – Microsoft Learn
Intune fundamentals filters performance-recommendations – Microsoft Learn












