Intune Local User Group Membership Not Working with 65000 Error? Here’s the Fix

Recently, I deployed a few accounts to the Local Administrators group on end-user devices through Intune.

The path I used was:
Endpoint Security → Account Protection → Local User Group Membership


Since I only needed to add specific accounts without removing existing ones, I chose the “Add (Update)” option under Group and user action.








However, on all Hybrid Azure AD Joined devices, the policy failed with error code 65000.




Here’s why it happened—and how to fix it. πŸ‘‡


Why Does the Error Happen

When selecting users or groups directly from Intune’s "Select users/groups" option, the system maps them in the following format:

AzureAD\test2@ccmlab.space, AzureAD\admin@ccmlab.space




This format doesn’t establish a proper mapping between the user accounts and their security identifiers (SIDs) on hybrid-joined devices, causing the policy to fail.

You can check the event logs end user device

Event Viewer → Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider (Admin)


How to Fix It

Instead of using the built-in “Select users/groups” option, manually enter the users using their User Principal Names (UPNs) in the correct format.




When configured this way, the event logs will show the accounts added successfully, and the policy will apply without any error

 

Now, accounts will successfully add as below










Popular Posts

Windows 11 24H2 Upgrade using Intune Feature Updates Policy

Remove CCMCache, Windows.old, and Temp folders using Powershell script

Deploying a Script through Intune to a Linux PC

SCCM Feature Upgrade Failure on HP Computers: Insufficient System Partition Disk Space (Error 0xC1900200 / -1047526912)