Missing Users Import Due to Null UserType Attribute

During user synchronization via Azure AD (Entra ID) integration, certain users may not be imported into inSync. This issue occurs because the userType attribute for the affected users is set to null, causing them to be excluded from group filtering and the subsequent mapping process.
​

The userType field returns a null value when the property has not been defined in Azure AD or has not synchronized correctly. Since the integration relies on this attribute to identify user roles, a null value results in a failed import.

Example API Request & Response:

​GET https://graph.microsoft.com/v1.0/users/{user-id}?$select=id,displayName,userType

{

"id": "ae28b7ff-60f7-493a-8cb9-cc4e39eab393",

"displayName": "John Doe",

"userType": null

}
​

Follow these steps to troubleshoot and resolve the missing user import issue.

Verify that your API requests are correctly formatted. If using the Microsoft Graph API to update user attributes, ensure the payload is correct.

Example PATCH Request:

PATCH https://graph.microsoft.com/v1.0/users/{userId}

Content-Type: application/json

{

"userType": "Member"

}

Note: Replace {userId} with the actual Azure object ID.
​

You can manually set the userType using the Microsoft Graph PowerShell module.

# Install and Connect

Install-Module Microsoft.Graph -Scope CurrentUser

Connect-MgGraph -Scopes "User.ReadWrite.All"

# Update the User

Update-MgUser -UserId {User-ID} -UserType "Member"
​

Confirm the changes by querying the user object again:

GET https://graph.microsoft.com/v1.0/users/{user-id}?$select=userType

# Expected Response

{

"userType": "Member"

}
​

Once the attribute is updated in Azure AD:

The missing users should now appear in the import logs and be successfully added to the system.