Forum Discussion
Why our users are getting local admin access on devices when the device runs through Autopilot profi
Why our users are getting local admin access on devices when the device runs through Autopilot profile and Azure AD joined devices even after we have selected Standard user in the Autopilot profile? ...
Where I can check whether it has the template assigned on it as I have seen devices being enrolled via Autopilot profile and added in all the locations like Intune, Autopilot, Entra ID and Defender as well but this is what happening.
1. Check if the profile is assigned to the devices
https://learn.microsoft.com/en-us/autopilot/profiles
If the device is enrolled and the user isn't a regular user but admin... check if the device also has the same naming template you configured in the same autopilot profile. If the device didn't got the autopilot profile (due a lot of possible reasons) the user isn't admin and the device still has the old name
https://learn.microsoft.com/en-us/autopilot/profiles
If the device is enrolled and the user isn't a regular user but admin... check if the device also has the same naming template you configured in the same autopilot profile. If the device didn't got the autopilot profile (due a lot of possible reasons) the user isn't admin and the device still has the old name
Here is says this
And name templates but in our case we kept few characters - and device serial number but it works when device goes through OOBE via Autopilot and not the Entra ID joined method
- Yep… thats why i mentioned it… autopilot is just nothing more than streamlining thr enrollment… (a bit more but to make it clear) the device needs to go through the oobe to enroll with autopilot … at that point the autopilot profile will be downloaded and applied . This will not happen with a regular entra join
So what is the solution on this or this is expected for all devices to get local admin access via AAD local device admin role?