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

You can create a new employee for a user account with an identity of type Organizational identity, Personalized administrator identity, Sponsored identity, Shared identity, or Service identity. To do this, click next to the input field and enter the required employee main data. Which login data is required depends on the selected identity type.

Specifies whether the user account is intentionally not assigned an employee. The option is automatically set if a user account is included in the exclusion list for automatic employee assignment or a corresponding attestation is carried out. You can set the option manually. Enable the option if the user account does not need to be linked with an employee (for example, if several employees use the user account).

If attestation approves these user accounts, these user accounts will not be submitted for attestation in the future. In the Web Portal, user accounts that are not linked to an employee can be filtered according to various criteria.

Indicates why the No link to an employee required option is enabled for this user account. Possible values:

• By administrator: The option was set manually by the administrator.

• By attestation: The user account was attested.

• By exclusion criterion: The user account is not associated with an employee due to an exclusion criterion. For example, the user account is included in the exclude list for automatic employee assignment (configuration parameter PersonExcludeList).

Account definition through which the user account was created.

Use the account definition to automatically fill user account main data and to specify a manage level for the user account. One Identity Manager finds the IT operating data of the assigned employee and enters it in the corresponding fields in the user account.

Azure Active Directory user account's tenant.

Type of user account. Depending on the user type, other mandatory input is required.

Permitted values are:

• Member: Normal Azure Active Directory user account.

• Guest: User account for guest users. The Azure Active Directory connector creates a user account for guest users and ensures that an invitation is sent by email to the given email address.

  Further configuration of guest users is required in the synchronization project. For more information, see Customizing synchronization projects to invite guest users.

(Only for the Guest user type) Acceptance status of the guest's invitation.

Permitted values are:

• Pending acceptance: The user has not accepted the invitation yet.
• Accepted: The user has accepted the invitation.
• Empty: Guest user without invitation.

(Only for the Guest user type) Time at which the invitation status was changed.

User account's domain.

Location where this user account is in use. In the One Identity Manager, if you assign Azure Active Directory subscriptions, a location is required.

The user's date of birth

The user's age group. Permitted values are Minor, Teenager, and Adult.

Specifies whether consent must be given for minors. Permitted values are Obtained, Not obtained, and Not required.

User account login name. The user's login name is made up of the alias and the domain. User login names that are formatted like this correspond to the User Principal Name (UPN) in Azure Active Directory.

User account display name.

Email alias for the user account.

User account's email address.

User's preferred language, for example, en-US.

Password for the user account. The employee’s central password can be mapped to the user account password. For detailed information about an employee’s central password, see One Identity Manager Identity Management Base Module Administration Guide.

If you use a random generated initial password for the user accounts, it is automatically entered when a user account is created.

The password is deleted from the database after publishing to the target system.

Reconfirm password.

Specifies whether the user must change their password the next time they log in.

Policies, which only apply to the user account. The available options are: No restrictions, Password never expires, and Allow weak passwords.

Data of last password change. The date is read in from the Azure Active Directory system and cannot be changed.

Maximum risk index value of all assigned groups. The property is only visible if the QER | CalculateRiskIndex configuration parameter is set. For detailed information, see the One Identity Manager Risk Assessment Administration Guide.

Categories for the inheritance of groups by the user account. Groups can be selectively inherited by user accounts. To do this, groups and user accounts or contacts are divided into categories. Select one or more categories from the menu.

User account's identity type Permitted values are:

• Primary identity: Employee's default user account.

• Organizational identity: Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.

• Personalized administrator identity: User account with administrative permissions, used by one employee.

• Sponsored identity: User account to use for a specific purpose. Training, for example.

• Shared identity: User account with administrative permissions, used by several employees. Assign all employees that use this user account.

• Service identity: Service account.

Specifies whether this is a privileged user account.

Specifies whether the user account can inherit disabled Azure Active Directory service plans through the employee. If this option is set, the user account inherits disabled service plans through hierarchical roles or IT Shop requests.

• If you add an employee with a user account to a department, for example, and you have assigned disabled service plans to this department, the user account inherits these disabled service plans.

• If an employee has requested a disabled service plan in the IT Shop and the request is granted approval, the employee's user account only inherits the disabled service plan if the option is set.

Specifies whether the user account can inherit Azure Active Directory subscriptions through the employee. If this option is set, the user account inherits Azure Active Directory subscriptions through hierarchical roles or IT Shop requests.

• If you add an employee with a user account to a department, for example, and you have assigned Azure Active Directory subscriptions to this department, the user account inherits these Azure Active Directory subscriptions.

• If an employee has requested an Azure Active Directory subscription in the IT Shop and the request is granted approval, the employee's user account only inherits the Azure Active Directory subscription if the option is set.

Specifies whether the user account can inherit Azure Active Directory administrator roles through the employee If this option is set, the user account inherits administrator roles through hierarchical roles or IT Shop requests.

• If you add an employee with a user account to a department, for example, and you have assigned administrator roles to this department, the user account inherits these administrator roles.

• If an employee has requested an administrator role in the IT Shop and the request is granted approval, the employee's user account only inherits the administrator role if the option is set.

Specifies whether the user account can inherit groups through the linked employee. If the option is set, the user account inherits groups through hierarchical roles, in which the employee is a member, or through IT Shop requests.

• If you add an employee with a user account to a department, for example, and you have assigned groups to this department, the user account inherits these groups.

• If an employee has requested group membership in the IT Shop and the request is granted approval, the employee's user account only inherits the group if the option is set.

Specifies whether the user account can inherit Office 365 groups through the linked employee. If the option is set, the user account inherits Office 365 groups through hierarchical roles, in which the employee is a member, or through IT Shop requests.

• If you add an employee with a user account to a department, for example, and you have assigned Office 365 groups to this department, the Azure Active Directory user account inherits these Office 365 groups.

• If an employee has requested group membership in the IT Shop and the request is granted approval, the employee's Azure Active Directory user account only inherits the Office 365 group if the option is set.

For detailed information about Office 365 groups, see the One Identity Manager Administration Guide for Connecting to Exchange Online.

Specifies whether the user account is disabled. If a user account is not required for a period of time, you can temporarily disable the user account by using the "User account is disabled" option.