Overview
This article discusses the difference between Manual Entra ID import and Entra ID mapping, even though both are part of the Entra ID deployment method.
Manual Entra ID import
Consider the following:
For manually importing the users from Azure one by one, the M365 app connection status should be connected status.
Using the Import Users from Entra ID option, you can quickly import and add user (s) as needed.
Only user accounts with the 'Member' type will be imported. Guest accounts will not be included in the import process.
Before you begin
Before you add users by importing information from Entra ID, ensure the following:
You or an administrator created the profile you want to assign to the user.
The storage where you want inSync to back up the user data is present.
Procedure
On the inSync Management Console menu bar, click Users.
Click Import > Import Users from Entra ID. The Import Users window appears.
In the Import Users window, enter the following details:
Email Address: Search and enter the email address of the user(s) that you want to import.
Profile: Select a profile that you want to assign to the users that you import using Entra ID.
Storage: Select storage where the users' data should be backed up.
Default Quota: Provide a default storage quota per user as per your requirement. The default value is zero, which is unlimited storage.
Send activation email to newly added users: Select this check box to notify the newly added users via email. By default, this option is selected.
Click Save.
The end-user account is created instantaneously.
Perform the steps for each user account that is present on the Azure. This method is preferred if there is an urgent new user account present on Azure and has to be imported urgently.
Entra ID mappings
Consider the following:
Microsoft 365 app on the inSync console has to be in a connected state. If the Microsoft 365 app isn't configured then follow the steps to Configure inSync for Microsoft 365.
Entra ID mappings are a part of the Entra ID deployment method. This will allow the customers to provision the users on the Druva console from the Entra ID in bulk.
Unlike the Manual Entra ID import method, Entra ID mapping will help the admin to import all the users from the Azure side which falls under the filter parameter that you specify while creating Entra ID mapping.
To create Entra ID mapping
For detailed instructions see, Create Entra ID Mapping.
Using Entra ID mapping you can select to import all users from the Azure side by specifying the filter users option to “Allow any user”
Also Entra ID mapping you can segregate users on the basis of the Entra ID attribute value
For example, you can mention on the Entra ID mapping only the users which have Entra ID attribute value department=engineering should only be provisioned to the Druva console.
Attributes for Entra ID mapping
For detailed instructions, see Attributes for Entra ID mapping.
You can create multiple Entra ID mappings and define the profile settings and storage region to which the bulk users are going to be assigned rather than manually select storage profile settings for each and every individual user account like the Manual Entra ID import method.
However, the end-user accounts aren’t created instantaneously like the Manual Entra ID import method.
Once you create an Entra ID mapping, inSync automatically scans your Entra ID.
📝NOTE:
User imports are processed on a scheduled basis. After users are added to Entra ID, they are typically imported within 24 hours. If a delay occurs due to system factors, the import will automatically occur during the next scheduled cycle.