Personal devices enrolled into Intune despite being blocked?

[sjstronach]

I'm still fairly new to modern device management so please forgive me in advance! I've currently got several hundred devices enrolled via Autopilot successfully into MEM, but found a dozen or so that popped up as personal, despite that option having been restricted. Am I missing something that is allowing the occasional one to slip through the cracks? I did a quick search here and didn't come across a similar issue so figured I would ask.

[#2]

Since these were Autopilot enrolled I know they are actually approved corporate devices, so I've gone ahead and recommended that we update their ownership status manually, but I'm still curious to know how out of all the hundreds of devices these few were labeled as Personal. 😃

[#3]

You could be sure that with that enrollment restrictions no "personal" devices could be enrolled

For Corporate devices”. So what makes a device corporate? The device needs to be: Azure Ad joined (Autopilot/User-Driven/OOBE) or enrolled with Apple Business Manager / DEP to be marked as Corporate.(or manually changed in Intune after enrollment)

https://call4cloud.nl/2021/08/the-battle-between-aadj-and-aadr/

[#4]

Hey Rudy thanks for the reply and I just wanted to follow up here. It looks like the devices were marked as Corporate but during the OOBE a few of the end users must have selected "personally owned device" by accident which seems to have carried thru the process. If they hadn't have already been identified as corporate owned, I suspect they would have been blocked from enrolling altogether. At least it was a quick fix by going in and editing them back to Corporate ownership status. 😃

[#5]

:).. sometimes the solution is easier than you might think.. So the issue was the last part in my sentence 🙂 : (or manually changed in Intune after enrollment) . Thanx for replying back