Understanding Automatic Operating system update behaviour

Interesting to what jasonbayton and Lizzie wrote is, that I have no option (using our current MDM) to enroll an os update policy to a device using "work profile", only if i enroll it as an fully managed (work managed) device or COPE (Corporate Personall) and then i have the options mentioned by them.

I think BYOD (work profile on private device) is also the correct name for what you are coming from and COPE (company device with work profile) where you are aming for, right?

Even i don't see the difference for the work profile because if the device is company owned (COWP) or private owned (POWP) shouldn't make a difference for the work profile in general or did i miss anything @all?

Or are you talking about COPE GMenzies?

If yes, then there's no chance to wait until a device is inactive as jasonbayton already wrote with the slightly difference that even on windowed mode there shouldn't be a prompt (as far as i know). But i think (not tested yet) if you don't configure an update policy the user itself should be able to trigger the update if available.

GMenzies regarding feature requests I already poked in a different topic here it would be nice to have a section here especially for that regard but i think nothing in planing to that Lizzie ? 😉

But you could ask for those functionalitys you loose maybe someone here can help you to find a different solution for work profile or tell you why this is expected not being able to be done on a work.