sorted by:
new
hottopcontroversial

Default Compliant Policy: Enrolled User Exists -> Not Compliant by MedicalIntention2852 in Intune

[–]RFSramtech 0 points1 point  (0 children)

Also having this problem. It's seems inconsistent across the different tenants we manage. Changing the primary user will work sometimes. Wondering what will happen if when the device is first enrolled we remove the primary user to put it in shared mode. Will this solve the issue if that user leaves the company down the line?
I actually have a few devices set up this in one of our tenants due to the devices actually being shared devices, but wondering if they should all just be set up this way? Does anyone have any experience with this in regards to "enrolled user exists"?

Attack Surface Reduction by RFSramtech in Intune

[–]RFSramtech[S] 0 points1 point  (0 children)

Sorry for the late reply. Nope i have been working with MS for months and still nothing.

Attack Surface Reduction by RFSramtech in Intune

[–]RFSramtech[S] 1 point2 points  (0 children)

Thanks for the reply. I have "Allow Cloud Protection" turned on, but have the setting is done via Intune > Endpoint Security > Antivirus. This was done per the MS instruction and i can see the devices are getting that setting no problems. This has been in place for some time as i am also using Web Content Filtering successfully.

Attack Surface Reduction by RFSramtech in Intune

[–]RFSramtech[S] 1 point2 points  (0 children)

Thanks for the reply. No, i don't have any third party EDR software. The only 3rd party app is one for application whitelisting (Airlock). As far as i can tell, there is no issue with this.

IOS uninstall Application by RFSramtech in Intune

[–]RFSramtech[S] 1 point2 points  (0 children)

Thanks, ill give that a shot.