This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 95%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Judging by some Google results, I'm not the only one who has experienced this error but no one seems to have had it in the same way I have.
So we have a number of Win10 Intune Configuration Profiles (we use Win10 Business 20H2), and 1 is to change desktop wallpaper and another is to start a program at user logon time. If we enroll a device (I've been doing it as an OOBE), enroll it using a standard user which results in the device being associated to them as the primary and enrolled user, all the policies get assigned to the user/device and the wallpaper is set and the program starts at logon. Perfect.
If a second user then logons on to the device those 2 polices get the event 827 "Policy is rejected by licensing" logged in the Device-Management-Enterprise-Diagnostics-Provider log even though the users have the same permissions/memberships. The issue also occurs if you change the primary user of the device to the second user ID.
If you reset the device to factory defaults and re-enroll it as the second user, the policies get assigned and work correctly.
Is this supposed to be the way it works? There doesn't seem to be any user or device reason as to why it shouldn't work for multiple users so its either a coded software restriction by MS or its a bug. I'm hoping its a bug and will be fixed at some stage.
Would like to try and get some official word or see if others experience the same issue and I'm not Robinson Crusoe
Cheers
From memory, the "business" SKU for Windows is a weird, one-off SKU that requires special handling and thus was not enabled for many/some of the CSPs behind these policies when we recently enabled them for the Pro SKU as up until earlier this year, some CSPs only worked on the Enterprise Windows SKU. Also from memory, this is set to be fixed "soonish", but I don't have or know details off-hand of when this will be.
It sort of seems as though if you assign a O365 Business Premium license to a user it sets their OS to Win 10 Business.
Can't prove it though
O365 licensing gives no Windows use rights; however, for M365 Business license types, you are probably correct. That doesn't change the core technical issue here that this isn't a Windows SKU that isn't widespread and is a bit different from other Windows SKUs is nature and thus was missed as noted above.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 97%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECW%3C/text%3E%3C/svg%3E)
I have been referred to this thread by product support.
I'm seeing the exact same thing. Computers were purchased with Windows 10 Pro. Users are licensed with Microsoft 365 Business Premium.
The identified product is now Windows 10 Business and policies are failing to apply.
Is there an open case I can refer product support to because I imagine every needs to know how to resolve this.
The actual policies affected don't even seem to be consistent from one device to another.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 46%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECP%3C/text%3E%3C/svg%3E)
It's been about a year and I'm still having this issue, was a fix ever implemented?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 21%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
@Jason Sandys it's two years later, and I'm also having the exact same problem here - a bunch of CSPs won't work when I try to assign them to devices running Windows 11 Business via the Microsoft 365 Business Premium license. The event log on each device shows "Policy is rejected by licensing".
Are you able to kindly check and find out if/when Microsoft plans to fix this?
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 13%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Hi @DevZero Thanks for posting in our Q&A.
For better troubleshooting, could you please provide more details such as configuration profile settings. We will do a similar experiment to test whether this is a common issue and give feedback here.
Best Regards,
Jarvis
Hi @Jarvis Sun-MSFT and thanks for the quick response, and apologies for my late one.
The CSP is a pretty basic one for setting a wallpaper as per the screenshot
@Jarvis Sun-MSFT One other thing that has just occurred which is puzzeling.
The Intune Wallpaper policy was working for the primary user as I mentioned in my original post. I then wanted to change the wallpaper to another jpg located on the device so changed the Intune policy to the new filename and I now just get a solid black coloured background and eventid 827 (rejected by licensing), ID 810 and ID 404 in Event Viewer.
Weird and troubling that licensing restrictions just seem to occur based on an update to an existing policy that was working.
Hope to hear back from you soon.
Cheers
@DevZero I guess it all depends on which Windows 10 build version you are using. A lot of settings aren’t supported on Windows 10 20H2 in combination with Business licenses. A lot of these settings catalog features will only be available in 21H2.
