Add a policy to prevent device unenrollment from Company portal
Companies provide devices to their employees and generally wants to make sure that these devices will always remain managed through Intune. It could be interesting to have a policy that prevent users to unenroll a device identified as a company device from the Intune company portal.
I can confirm that we have this on our plan for early in 2020/ Thanks for your patience!
Jegan Devabalan commented
We have 3000 devices about to get enrolled with Intune but its leaving a risk were user can un-enroll the device on their own. I would like microsoft to come with a solution as soon as they can . Also i want to be keep posted about this.
Darwis Fransida commented
Yes, that will work for us to control/restrict the ability to remove device from InTune Comp Portal if the device ownership is set to Corporate.
Has this been implemented?
Actually it would be great if there would be an option to the user to remove his onmicrosoft.com account from the info. I personally broke the Intune enrollment when I removed the user and added a new one within the same session.
Intune sees the device as unenrolled and even when I put back the original user the enrollment didn't recover.
This is a known issue in the way intune manages shared devices that are used by different users as so far Intune has only one possible user assigned to the device
Dan goodwin commented
Hi guys i have found a way round it if you have knox devices.
Instead of enrolling android enterprise, enrol just android.
Android enterprise- if you uninstall the company portal, knox deployment will not force the enrolment again.
Android- if you uninstall the company portal, knox deployment will force the user to go through the deployment again which involves installing and enrolling the company portal. During this time they are unable to use the back button, home button or split button.
So I think rolling out the devices as personal will ensure the devices are still managed
Disabling corporate vs personal would be an option. It may also be nice to have some sort of policy set that us as admins could deploy. As admins you could test with multiple devices and if it automatically did not allow removal of the portal app, that could hinder testing from our side. If you could deploy it as a policy set it could allow use to point this to specific groups or collections. A case for this would be that my company has some outward facing Android devices that we manage. We can not use DEP since thats iOS. There would be an administrative burden to always verify the Android devices are always imported via manual efforts to verify they are "company owned." We get in hundreds of these devices that a specific group of individuals use. The company wants these individual users to enroll vs an enrollment administrator. If you could target a policy to these people which would remove the ability in the app to be removed, it would be beneficial.
Stephen B commented
This is a very basic MDM requirement for company owned devices.
Please make this available ASAP!!
What is the point of advertising Intune as MDM if this is not a feature. AirWatch ( a MDM solution ) provides this capability.
"This policy setting is not applied if the computer is Azure Active Directory joined and auto-enrollment is enabled." As most people work this was please add Block Manual unenrollment
mark payton commented
Works for me!
Ash Hoque commented
This would certainly work for us.
Carlos Conrado commented
Hi Cathy having the disable remove device based on corp or personal device would be a good enough solution.
Rob de Roos commented
Isn't this available allready? I believe it is. Disable manual unenrollment it is called if I am not mistaken.
Rich Moore commented
That would work for us
This would work for us.
Owen Dickenson commented
That would work for us; we would want to have corporate devices managed with no choice to our end users. Those connecting personal devices - that's up to them.
Thomas Wiedenhofer commented
For me it would be nice if corporate devices are disabled from removing the device, personal owned devices could be free of choice. Thank you!
Noel Fairclough commented
Yes -being able to un-enroll based on ownership status is perfect. Corporately owned = they can't un-enroll the device without approval, or without the admin doing it for them. Personally owned = they can do what they want. We can restrict access to corporate resources based on MAM policies -so if they don't want the managed app, they can't access resources. Simple. If they don't want to use their personal device, they can apply for a corporate device but then live by our rules.