Chat now with support
Chat with Support

Identity Manager 8.1.5 - Administration Guide for Connecting to Azure Active Directory

Managing Azure Active Directory environments Setting up synchronization with an Azure Active Directory tenant Basic data for managing an Azure Active Directory environment Azure Active Directory core directories Azure Active Directory user accounts Azure Active Directory groups Azure Active Directory administrator roles Azure Active Directory subscriptions and service plans
Azure Active Directory subscriptions Disabled Azure Active Directory service plans
Reports about Azure Active Directory objects Configuration parameters for managing an Azure Active Directory environment Default project template for Azure Active Directory

Editing search criteria for automatic employee assignment

The criteria for employee assignments are defined for the tenant. In this case, you specify which user account properties must match the employee’s properties such that the employee can be assigned to the user account. You can limit search criteria further by using format definitions. The search criterion is written in XML notation to the Search criteria for automatic employee assignment column (AccountToPersonMatchingRule) in the AADOrganization table.

Search criteria are evaluated when employees are automatically assigned to user accounts. Furthermore, you can create a suggestion list for assignments of employees to user accounts based on the search criteria and make the assignment directly.

NOTE: When the employees are assigned to user accounts on the basis of search criteria, user accounts are given the default manage level of the account definition entered in the user account's target system. You can customize user account properties depending on how the behavior of the manage level is defined.

It is not recommended to make assignments to administrative user accounts based on search criteria. Use Change master data to assign employees to administrative user accounts for the respective user account.

NOTE: One Identity Manager supplies a default mapping for employee assignment. Only carry out the following steps when you want to customize the default mapping.

To specify criteria for employee assignment

  1. Select the Azure Active Directory | Tenants category.
  2. Select the tenant in the result list.
  3. Select the Define search criteria for employee assignment task.
  4. Specify which user account properties must match with which employee so that the employee is linked to the user account.
    Table 27: Default search criteria for user accounts and contacts
    Apply to Column for employee Column for user account
    Azure Active Directory user accounts Central user account (CentralAccount) Alias (MailNickName)
  5. Save the changes.
Direct assignment of employees to user accounts based on a suggestion list

In the Assignments pane, you can create a suggestion list for assignments of employees to user accounts based on the search criteria and make the assignment directly. User accounts are grouped in different views for this.

Table 28: Manual assignment view

View

Description

Suggested assignments

This view lists all user accounts to which One Identity Manager can assign an employee. All employees are shown who were found using the search criteria and can be assigned.

Assigned user accounts

This view lists all user accounts to which an employee is assigned.

Without employee assignment

This view lists all user accounts to which no employee is assigned and for which no employee was found using the search criteria.

TIP: By double-clicking on an entry in the view, you can view the user account and employee master data.

To apply search criteria to user accounts

  • Click Reload.

    All possible assignments based on the search criteria are found in the target system for all user accounts. The three views are updated.

To assign employees directly using a suggestion list

  1. Click Suggested assignments.
    1. Check the Selection box of all the user accounts to which you want to assign the suggested employees. Multi-select is possible.
    2. Click Assign selected.
    3. Confirm the security prompt with Yes.

      The employees found using the search criteria are assigned to the selected user accounts.

    – OR –

  2. Click No employee assignment.
    1. Click the Select employee option of the user account to which you want to assign an employee. Select an employee from the menu.
    2. Check the Selection box of all the user accounts to which you want to assign the selected employees. Multi-select is possible.
    3. Click Assign selected.
    4. Confirm the security prompt with Yes.

      The employees displayed in the Employee column are assigned to the selected user accounts.

To remove assignments

  1. Click Assigned user accounts.
    1. Click the Selection box of all user accounts you want to delete the employee assignment from. Multi-select is possible.
    2. Click Remove selected.
    3. Confirm the security prompt with Yes.

      The assigned employees are removed from the selected user accounts.

For more detailed information about defining search criteria, see the One Identity Manager Target System Base Module Administration Guide.

Related topics

Disabling Azure Active Directory user accounts

The way you disable user accounts depends on how they are managed.

Scenario:

  • The user account is linked to employees and is managed through account definitions.

User accounts managed through account definitions are disabled when the employee is temporarily or permanently disabled. The behavior depends on the user account manage level. Accounts with the Full managed manage level are disabled depending on the account definition settings. For user accounts with a manage level, configure the required behavior using the template in the AADUser.AccountDisabled column.

Scenario:

  • The user accounts are linked to employees. No account definition is applied.

User accounts managed through user account definitions are disabled when the employee is temporarily or permanently disabled. The behavior depends on the QER | Person | TemporaryDeactivation configuration parameter

  • If the configuration parameter is set, the employee’s user accounts are disabled when the employee is permanently or temporarily disabled.

  • If the configuration parameter is not set, the employee’s properties do not have any effect on the associated user accounts.

To disable the user account when the configuration parameter is disabled

  1. In the Manager, select the Azure Active Directory | User accounts category.

  2. Select the user account in the result list.

  3. Select the Change master data task.

  4. On the General tab, set the Account is disabled option.

  5. Save the changes.
Scenario:
  • User accounts not linked to employees.

To disable a user account that is no longer linked to an employee

  1. In the Manager, select the Azure Active Directory | User accounts category.

  2. Select the user account in the result list.

  3. Select the Change master data task.

  4. On the General tab, set the Account is disabled option.

  5. Save the changes.
Related topics

Deleting and restoring Azure Active Directory user accounts

NOTE: As long as an account definition for an employee is valid, the employee retains the user account that was created by it. If the assignment of an account definition is removed, the user account that was created from this account definition is deleted.

To delete a user account

  1. Select the Azure Active Directory | User accounts category.
  2. Select the user account in the result list.
  3. Delete the user account.
  4. Confirm the security prompt with Yes.

To restore a user account

  1. Select the Azure Active Directory | User accounts category.
  2. Select the user account in the result list.
  3. Click Undo delete in the result list toolbar.
Configuring deferred deletion

By default, user accounts are finally deleted from the database after 30 days.The user accounts are initially disabled. You can reenable the user accounts until deferred deletion is run. After deferred deletion is run, the user accounts are deleted from the database and cannot be restored anymore.In the Designer, you can set an alternative delay on the AADUser table.

Related topics

Azure Active Directory groups

Azure Active Directory recognizes several group types into which you can organize users and groups to regulate access to resources or email distribution, for example.

Groups are loaded into One Identity Manager by synchronization. You can edit individual master data of the group and you can create new security groups in One Identity Manager. However, you cannot create more group types in One Identity Manager.

To add users to groups, you assign the groups directly to users. This can be assignments of groups to departments, cost centers, locations, business roles, or the IT Shop.

The group types supported in One Identity Manager are listed below.

Table 29: Support groups types

Group type

Description

Security group

Resource permissions are distributed through security groups. User accounts and other groups are added to security groups, which makes administration easier.

Security groups are loaded into One Identity Manager by synchronization. You can edit security groups in One Identity Manager and also create new ones.

Office 365 group

Office 365 groups are loaded into One Identity Manager by synchronization. You can edit Office 365 groups in One Identity Manager but you cannot create new ones in One Identity Manager.

Distribution group

Distribution groups are used to send emails to group members. Distribution groups are loaded into One Identity Manager by synchronization. You can edit distribution groups in One Identity Manager but you cannot create them in One Identity Manager.

Mail-enabled security groups

Mail-enabled security groups are security groups that are used as distribution groups.

Mail-enabled security groups are loaded into One Identity Manager by synchronization. You can edit mail-enabled security groups in One Identity Manager but You cannot create new mail-enabled security groups in One Identity Manager.

Dynamic group

Members of a dynamic group are not strictly assigned, but determined through defined rules. Dynamic groups are loaded into One Identity Manager by synchronization. You can change dynamic groups in One Identity Manager. You cannot create new dynamic groups in One Identity Manager.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating