License requirements to disable Copilot & disable 'Enable Dev Drive'

[james-prince]

Hi, trying to apply 2 of your policies to my tenant, and getting errors activating these due to what i believe is a licensing restriction.
Having trouble finding information in the docs, and wondered if perhaps a warning should be added to these as you have done with other policies. Happy to raise individual issues for these if needed.

Win - OIB - SC - Windows User Experience - D - Feature Configuration - v3.1

Administrative Templates
System > Filesystem
Enable dev drive: Disabled

The rest of the policy applied OK, but not the disable dev drive setting.
Appears to have applied OK on all kiosk devices (no license assigned) and devices where users have F3 licenses, but failed on all business premium user's devices.

From the event log:

Event ID: 827
MDM PolicyManager: Policy is rejected by licensing, Policy: (EnableDevDrive), Area: (FileSystem), Result:(0x82B00006) Unknown Win32 Error code: 0x82b00006.

Win - OIB - SC - Windows User Experience - U - Copilot - v3.6

Windows AI
Turn Off Copilot in Windows (User) - Disable Copilot

This policy has applied sucessfully for my users with F3 licenses, but not for those with Business Premium licenses.

From the event log:

Event ID: 827
MDM PolicyManager: Policy is rejected by licensing, Policy: (TurnOffWindowsCopilot), Area: (WindowsAI), Result:(0x82B00006) Unknown Win32 Error code: 0x82b00006

Mixture of devices running Windows 11 24H2 + 25H2 (All Pro).
Not sure if some of these are supposed to be enterprise only? Either way they have applied OK for our F3 users.

Thanks

[james-prince]

From a bit of digging after posting this, seems to be a somewhat ongoing issue with Microsoft 'forgetting' to include Windows 11 Business in their applicability filters for some settings, where Windows Pro has been included.

And all of our business premium users automatically get moved from Pro to Business (to what benefit, i'm unsure).

https://www.reddit.com/r/Intune/comments/14lqjj9/configuration_profiles_on_windows_1011_business/

Not sure what the best route forward is for this problem, make noise to MS to fix? Might be worth dropping in a warning for BP users.
Should i manually remove these from the OIB policies, or just live with the errors?

[SkipToTheEndpoint]

Oh wow, I haven't seen this issue for a while!

So Windows Business isn't a proper SKU. All it does is change some words and branding in the OS. That's it.
Honestly, the last time I dealt with this (which was a while ago) I just ended up turning off the Windows Business sub-license as part of the BP and leave devices at Pro.

That aside, Dev Drive is such a niche thing, not applying that policy won't hurt, and the policy for Copilot was to do with the old Copilot application that MS pushed out a year ago, and the policy itself is deprecated.

[james-prince]

I actually removed the dev-drive option already, as i figured it wasn't a big deal, was just more curious about why it wasn't working.
Good to know the copilot stuff is deprecated too!

Do you remember the process of 'turning off the Windows Business sub-license'? I had a quick search but couldn't find anything.
Is it a tenant setting, or a configuration i would apply to the devices?

Seems like a good option to turn it off if possible, no idea why MS have added it on other than for some weird branding for business premium users?