
Microsoft Intune environments tend to grow and become more complex over time. Policies are added, security requirements change, exceptions are created, and sometimes configurations stay around simply because they still work. But working does not always mean that the configuration still makes sense.
When I review an existing Intune environment, there are a few areas I think are always worth another look. Let’s dive in!
Topics in the post:
- Device compliance
- Security baselines
- Assignments
- Windows Update
- Local administrator access
- My take
- Quick Review Checklist
- Useful links
Before We Start
Intune is not something you configure once and then forget about. Microsoft keeps adding capabilities, security requirements change, and the organization itself changes.
A configuration that made perfect sense two years ago may not be the choice you would make today.
A simple question I like to ask is:
“If we were building this Intune environment today, would we configure it the same way?”
If the answer is no, it might be time to revisit it.
1. Device Compliance
Start with a simple question: What does a compliant device actually mean in your environment?
Review what makes a device compliant or non-compliant and whether those requirements still match what you expect from a managed device.
I would also look at how compliance is used with Conditional Access. A compliance setting can look perfectly reasonable in Intune, but once it affects access to Microsoft 365 and other resources, the impact can be much bigger.
Think about the complete flow:
Device → Compliance → Conditional Access → User
And don’t forget the user experience. If a device becomes non-compliant, does the user understand what happened and what they need to do?
Related: Client driven compliance evaluation
2. Security Baselines
I like security baselines and see them as a good starting point for securing Windows devices. But they should not be something you deploy and then forget about.
Look at which baseline you are using, what you have changed from Microsoft’s defaults, and why. Most importantly, are those exceptions still needed?
Are some of the same settings also configured through Settings Catalog or other Endpoint Security policies?
As I discussed in my Windows 11 26H2 Security Baseline article, I don’t think the important question is whether security baselines are good or bad. It is whether you understand what they are changing and why.
3. Assignments
Assignments can become surprisingly complicated over time.
Groups get added, exclusions are created and policies that originally targeted a small number of devices suddenly have several different assignments.
This is where I would review:
- User vs. device assignments
- Old groups and exclusions
- Broad assignments
- Assignment filters
- Policies targeting the same devices
One question usually tells you quite a lot:
Can you easily explain why a specific device receives a specific policy? If the answer requires investigating several groups, exclusions and overlapping policies, there may be room to simplify.
Check my post Assignment Filters in Microsoft Intune: Why They Matter More Than Ever – EndpointExperience for a deep dive.
4. Windows Update
Windows Update is another area I would revisit regularly.
Do you still need all your deployment rings?
Do the deadlines make sense?
Is your pilot group actually being used as a pilot, or has it simply become another deployment ring?
And if you’re maintaining a complex update configuration manually, is there a reason not to consider Windows Autopatch?
Keeping devices updated and secure is important, but users should also have a predictable update and restart experience.
5. Local Administrator Access
Finally, I would review local administrator access.
Do you still have users with local administrator rights, and if so, why? Could Windows LAPS or Endpoint Privilege Management help you reduce the need for permanent local administrator rights?
There may be completely valid reasons, but do those reasons still exist today? Don’t be afraid to challenge old exceptions. If the reason is simply “this application needs local admin”, it might be worth testing whether that is still actually true.
Look at the Environment as a Whole
This is probably the most important part.
Don’t review these areas completely independently.
Security baselines, configuration profiles, compliance, Conditional Access and Windows Update all come together on the same device.
Individually, every policy might look perfectly reasonable. Together, they may create unnecessary complexity or a poor user experience.
For me, good endpoint management is about finding the right balance between security, manageability and user experience.
My take
I don’t recommend changing configurations just because Microsoft introduces a newer way of doing something.
If something works and there is a good reason for it, keep it.
But revisit the decisions behind your configuration from time to time. Remove exceptions that are no longer needed, simplify assignments where possible, and document why important decisions have been made.
You should be able to explain not only what is configured in Intune, but also why. And from time to time, it’s worth challenging whether those decisions still make sense.
Quick Review Checklist:
✅Device compliance: Do compliance requirements still define a trusted device?
✅Security baselines: Are exceptions still justified?
✅Assignments: Can you explain why each device receives its policies?
✅Windows Update: Are rings, deadlines and pilots still serving a purpose?
✅Local administrator access: Is permanent administrator access still necessary?






















