Unified Endpoint Management solution (it can be Knox Mobile Management, Intune or Mobile Iron) must instruct the device to start using that mode and can provide to the device configs and apps over Android API system.
Example of policy which can be delivered by UEM is Network Config.
-and from this point on, my device’s Wi-Fi module starts automatically/ spontaneously (irregularly):

-IT department on trial removed the “corporatemobile” wifi connection on Android, and the automatic connection disappeared
-by trial/error I have come to the conclusion that the connection problem is generated by the MS Intune environment – can you please help me where to change the MS Intune settings ?

Note, I have also encountered that using a PO profile you aren’t technically supported to push Outlook app config, just app protection policies. Very disappointing. I seem to recall Airwatch, ahem, VMware, telling me the same thing in their platform ~1 year go, but I’m not convinced.

Hi all, I was testing the same thing today and found this tutorial because I was getting a fully managed enrollment every time. I did 2 things different from this tutorial.

1. I selected “Let MDM choose to enroll as a Device Owner or Profile Owner”. After this it immediately enrolled to COPE.
2. I selected “Disable system applications” because I noticed that this settings applies to the “Work” section and not the “private” section and I don’t need the system apps there as well.

Thanks for posting this, well documented!

Hi Alex,

you are right. We experienced the same! COPE in Intune is broken at the moment. For us the only way is Samsung Knox Portal + COPE Token and then skip private Gmail account in the setup assistent.

I’m not completely sure what this setting exactly does. But I’ve set it to “Force Device Owner Enrollment” and that works fine for me.

Yes I am absolutely sure. What I found is the part in the following article:
https://docs.samsungknox.com/admin/knox-mobile-enrollment/create-profiles.htm#Configur

If I understand it correctly:
“Force Device Owner Enrollment” sets the device as Fully Managed.
And “Let MDM choose to enroll as a Device Owner or Profile Owner” would enroll the device as COPE if supported. Do you see it the same way?

Hi Alex,

That’s not my experience.
As you can see in my previous article related to COPE it shows as “Android (corporate-owned work profile)”.

The article is found here https://inthecloud247.com/how-to-configure-android-corporate-owned-personally-enabled-user-devices-with-microsoft-intune/

Are you sure you took the right token for enrollment which you added to the enrollment profile and assigned to the right MDM Profile in the KME portal?