You’ve created a configuration policy in Microsoft Intune.

You’ve assigned it to a group.

You wait.

And nothing happens.

This is one of the most common situations administrators encounter when working with endpoint management.

The important thing is not to start randomly changing settings.

Instead, work through the deployment logically.

1. Check the Assignment

Start with the basics.

Is the affected user or device actually targeted by the policy?

Review:

• Included groups
• Excluded groups
• User versus device targeting
• Assignment filters

A perfectly configured policy will never apply if the device isn’t included in the deployment scope.

Be especially careful with exclusions.

A device could belong to an included group while simultaneously being affected by your exclusion strategy.

2. Check the Device

Next, confirm that you are investigating the correct device object.

Review the device in Intune and verify information such as:

• Device name
• Operating system
• Ownership
• Compliance state
• Management status
• Last check-in information

In larger environments, similarly named or stale device records can make troubleshooting confusing.

3. Force a Sync

If the assignment looks correct, initiate an Intune sync.

A sync can be triggered through the managed device experience as appropriate, and users can also initiate synchronization from the Windows management interface available to them.

Give the service and endpoint time to process the request.

Repeatedly pressing sync every few seconds usually doesn’t improve troubleshooting.

4. Check the Policy Status

Now investigate the actual policy deployment status.

Depending on the policy type, you may see statuses such as:

• Succeeded
• Error
• Conflict
• Pending
• Not applicable

These states tell you where to continue your investigation.

Error : A setting attempted to apply but encountered a problem.

Conflict: Another configuration may be trying to manage the same or related setting differently.

Pending: Processing may not yet be complete.

Not applicable : Check whether the setting is compatible with the device’s Windows version, edition, configuration and management scenario.

5. Check for Conflicting Policies

Policy conflicts are easy to create.

For example:

Policy A: Disable feature = Enabled

Policy B: Disable feature = Disabled

If both target the same device, you’ve created competing configurations.

This frequently happens as an Intune environment grows.

One administrator creates a policy, another creates a second policy months later, and eventually the same Windows setting is being managed from multiple places.

Documenting your Intune policies helps avoid this.

6. Compare a Working and Non-Working Device

This is one of my favorite troubleshooting techniques.

Suppose a policy succeeds on 99 devices but fails on one.

Compare the failing endpoint with a successful endpoint.

Look at:

• Windows build
• Windows edition
• Group membership
• Enrollment method
• Assignment filters
• Installed software
• Existing configuration
• User versus device context

This can narrow down the problem quickly.

If the exact same policy works on hundreds of devices, completely redesigning the policy probably shouldn’t be your first troubleshooting step.

7. Check Endpoint Logs

When the Intune portal isn’t giving you enough information, move closer to the endpoint.

For applicable workloads, review Intune Management Extension logs and relevant Windows Event Viewer information.

Logs are particularly useful when troubleshooting:

PowerShell scripts
Win32 apps
Remediations
Management Extension behavior

Don’t just search for the word Error.

Work out what the device was doing immediately before the failure.

An error message without context can easily send troubleshooting in the wrong direction.

My Troubleshooting Flow

When an Intune policy doesn’t apply, I use this general order:

Assignment → Device → Sync → Deployment status → Conflict → Endpoint → Logs → Root cause

Following a consistent process prevents wasted time.

Final Thoughts

An Intune policy not applying doesn’t automatically mean there’s a problem with Microsoft Intune.

It could simply be:

Incorrect targeting
An exclusion
A compatibility issue
A configuration conflict
A device that hasn’t checked in
A local Windows problem

Successful Intune troubleshooting is about narrowing down the problem one layer at a time. Avoid changing five settings simultaneously. Change one thing, test it, observe the result, and continue from there.