Problem Statement
Users are not being imported from Entra ID (formerly Azure AD) into Druva. Upon investigation, it has been identified that the usertype attribute is missing for these users in their Entra ID profile. Druva relies on this attribute to correctly identify and manage user licenses and access.
Cause
The usertype attribute in Entra ID defines the type of user (e.g., Member, Guest). If this attribute is not set or is missing for a user, Druva might fail to recognize and import the user during synchronization. This can occur due to various reasons, including:
Manual User Creation without Setting the Attribute: When users are created manually in Entra ID, the usertype might not have been explicitly defined.
Synchronization Issues from On-premises Active Directory: If users are synced from an on-premises Active Directory to Entra ID, the attribute might not be correctly mapped or synchronized.
Scripting or Automation Errors: Scripts or automation processes used for user provisioning might have inadvertently skipped setting the usertype.
Solution
To resolve this issue and ensure the affected users are imported into Druva, you need to ensure the usertype attribute is correctly populated for these users in Entra ID. Follow these steps:
Identify Affected Users: Determine the list of users who are not being imported into Druva and verify that they are present in Entra ID.
Verify usertype in Entra ID: For each affected user, check their profile in the Entra ID admin center:
Navigate to the Azure Active Directory admin center (entra.microsoft.com).
Go to Users and search for the specific user.
Open the user's profile.
Look for the usertype attribute. If it's blank or missing, proceed to the next step.
3. Set the usertype Attribute: You can set the usertype using the Entra ID admin center or PowerShell:
Using Entra ID Admin Center:
Edit the user's profile.
Locate the User type field.
Select the appropriate value (e.g., "Member" or "Guest").
Save the changes.
Using PowerShell:
Connect to Azure AD PowerShell:
Connect-MgGraph-Scopes"User.ReadWrite.All"
2. For a specific user, run the following command, replacing
<userPrincipalName> with the user's UPN and <usertypeValue> with either "Member" or "Guest":
Update-MgUser-UserId"<userPrincipalName>"-UserType"<usertypeValue>"
3. For example:
Update-MgUser-UserId"john.doe@yourdomain.com"-UserType"Member"
4. Initiate Druva Synchronization: Once the usertype attribute is set for the affected users in Entra ID, trigger a synchronization in Druva. This process will vary depending on your Druva configuration.
5. Verify User Import in Druva: After the synchronization completes, verify that the previously missing users have now been successfully imported into Druva.
By following these steps, you should be able to resolve the issue of users not importing into Druva due to the missing usertype attribute in Entra ID.
