โ† Windows & Intune
๐Ÿ“ฑ Intune

Add a User or Group to Local Admin Using Intune

Use an Account Protection policy in Intune to add an Entra ID user or security group to the local Administrators group on Windows 10 and Windows 11 devices โ€” no scripts required.

โ„น๏ธ
What this does: Adds an Entra ID user or security group to the local Administrators group on Intune-managed Windows devices โ€” without touching existing members. Works on Windows 10 and Windows 11, both Entra-joined and hybrid-joined.
Identify the User or Group

Decide whether you want to add an individual Entra ID user account or an Entra security group. Using a security group is recommended for scale โ€” add users to the group and the policy applies automatically.

Make sure the account exists in Entra ID (Azure AD) before proceeding. Note the exact display name or UPN โ€” you'll need it when selecting in the policy.


Create an Account Protection Policy

Navigate to the Intune admin center and create a new Account Protection policy targeting the Local user group membership profile.

2.1
Open Account Protection
Sign in to endpoint.microsoft.com โ†’ Endpoint Security โ†’ Account protection โ†’ click Create Policy.
2.2
Select Platform and Profile
Platform: Windows
Profile: Local user group membership
Click Create.
2.3
Basics Tab
Give the policy a clear Name and Description โ€” e.g. LocalAdmin-Add-Helpdesk. Click Next.
2.4
Configuration Settings
Set the following values:

Local group: Administrators
Group or user action: Add (Update)
User selection type: Users/Groups
Selected users/groups: Click Select users/groups and choose the Entra ID user or security group you want to add.
๐Ÿ’ก
Add (Update) โ€” adds the selected members without touching any existing group members. This is the safest option.

Add (Replace) โ€” replaces the entire group membership with only the members you specify. Use with caution.

Remove (Update) โ€” removes specific members from the local admin group without affecting others.
2.5
Scope Tags (Optional)
Add scope tags if your organisation uses RBAC to limit admin visibility. Skip if not applicable and click Next.
2.6
Assignments
Assign the policy to the Entra security group that contains the target devices. Best practice: pilot with a small test group first, then expand once confirmed working.
2.7
Review + Create
Review the summary and click Create. The policy is now live and will apply at the next device check-in.

Sync Intune Policies to the Device

Policy delivery isn't instant. To speed it up on a test device, trigger a manual sync using one of these methods:

โ†’
From the device โ€” Settings app
Settings โ†’ Accounts โ†’ Access work or school โ†’ click your account โ†’ Info โ†’ Sync
โ†’
From the device โ€” PowerShell
Run as admin to immediately trigger the Intune Management Extension check-in:
Get-ScheduledTask | Where-Object {$_.TaskName -like "*PushLaunch*"} | Start-ScheduledTask
โ†’
Remotely โ€” from Intune admin center
Devices โ†’ All Devices โ†’ select the device โ†’ Sync. Or simply restart the device to trigger check-in.

Monitor Deployment Status

Check that the policy applied successfully before verifying on the device.

โ†’
Open the policy in Intune
Endpoint Security โ†’ Account Protection โ†’ click the policy you created.
โ†’
Check device check-in status
Under Device and user check-in status, confirm the device shows Succeeded. Click Device assignment status or Per setting status for more detail if the status isn't as expected.

Verify on the Device

Confirm the user or group has been added to the local Administrators group directly on the target device.

โ†’
Open Computer Management
Press Start โ†’ search for Computer Management โ†’ open it.
โ†’
Check the Administrators group
Local Users and Groups โ†’ Groups โ†’ double-click Administrators. The Entra ID user or group should appear in the members list.
๐Ÿ’ก
You can also verify quickly via PowerShell on the device:
Get-LocalGroupMember -Group "Administrators"