Configuration profile "Not applicable"

Copper Contributor

Hello, how are you? I hope well.

I researched many materials, but i can't find a solution.
I've done several tests and the configuration profiles are always "Not applicable".
The dns configured in Azure AD is private.
Are there any additional configurations to be done? The setting is always "Not Applicable", whether by group or not.


I have already removed the local administrator manually and also through AutoPilot through the Office 365 E3 portal, but it didn't solve it either. 
The policies and settings I tried to make manually are all "Not applicable", even using the Windows 10 Pro client.
Only those that are made by the system are applied.

I really appreciate your help.


7 Replies
Are you using only MDM? Can you provide some screenshots from a device configuration profile
How are the profiles targetted. Users Or device based?



Thanks for the answer.

Yes, only MDM.

I tried both ways





Just to be sure, are the devices windows 10 enterprise




It makes perfect sense.
I only tested it with the Pro version.
For some reason, I believed it met the requirements.
I will test with the Enterprise version and come back with the result.
Thanks a lot for the help.

Its sometimes weird why you need enterprise... but sometimes you do. You could also watch the device enterprise management event log... it would tell you you have the wrong sku or something like that





After changing the system version to Enterprise, it worked. Some apply to Pro as well, but few. Other settings for Insiders only.

Thanks a lot!



where does one find this master list for policy Vs. OS compatibilites? 


I suspect i'm in a similar boat but have yet to find a good policy feature Vs. OS comparison like provided in your screenshot.