Chat now with support
Chat with Support

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

Managing Azure Active Directory Environments Setting Up Synchronization with an Azure Active Directory Tenant Base Data for Managing Azure Active Directory 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 Plan
Reports about Azure Active Directory Objects Appendix: Configuration Parameters for Managing Azure Active Directory Appendix: Default Project Template for Azure Active Directory

Azure Active Directory Domains

Azure Active Directory Domains

A base domain is linked to the core directory in the cloud. You can also add other user defined domains in Azure Active Directory, which you can then allocate to Microsoft cloud services. One Identity Manager only loads verified domain data into the database. It is not possible to edit data in One Identity Manager.

To obtain an overview of a domain

  1. Select the category Azure Active Directory | Verified domains.
  2. Select the domain in the result list.
  3. Select Azure Active Directory domain overview in the task view.
    Table 25: Domain Master Data

    Property

    Description

    Domain name

    Full name of the domain.

    Tenant

    Tenant entered for this domain.

    Type

    Domain type.

    Primary domain

    Specifies whether this is the primary domain for created new user accounts, for example.

    Initial domain

    Specifies whether this is the initial domain. The initial domain is create when a tenant is registered in Azure Active Directory.

    Available services

    List of service available in this domain.

Azure Active Directory user accounts

Azure Active Directory User Accounts

You manage user account in One Identity Manager with Azure Active Directory. The user requires a subscription to access a service plan in Azure Active Directory. User accounts obtain the required access rights to the resources through membership in groups.

Detailed information about this topic

Linking User Accounts to Employees

The central component of the One Identity Manager is to map employees and their master data with permissions through which they have control over different target systems. For this purpose, information about user accounts and permissions can be read from the target system into the One Identity Manager database and linked to employees. This gives an overview of the permissions for each employees in all of the connected target systems. One Identity Manager provides the possibility to manage user accounts and their permissions. You can provision modifications in the target systems. Employees are supplied with the necessary permissions in the connected target systems according to their function in the company. Regular synchronization keeps data consistent between target systems and the One Identity Manager database.

Because requirements vary between companies, the One Identity Manager offers different methods for supplying user accounts to employees. One Identity Manager supports the following method for linking employees and their user accounts.

  • Employees and user accounts can be entered manually and assigned to each other.
  • Employees can automatically obtain their account definitions using user account resources. If an employee does not have a user account in a tenant, a new user account is created. This is done by assigning account definitions to an employee using the integrated inheritance mechanism followed by process handling.

    When you manage account definitions through user accounts, you can specify the way user accounts behave when employees are enabled or deleted.

    NOTE: If employees obtain their user accounts through account definitions, they have to have a central user account and obtain their company IT data through assignment to a primary department, primary location or a primary cost center.
  • An existing employee is automatically assigned when a user account is added or a new employee is created if necessary. In this case, employee master data is created on the basis of the existing user account master data. This mechanism can be implemented if a new user account is created manually or by synchronization. This method, however, is not the One Identity Manager default method. Define criteria for finding employees for automatic employee assignment.
Related Topics

Supported User Account Types

Different types of user accounts, such as default user accounts, administrative user accounts or service accounts, can be mapped in One Identity Manager.

The following properties are used for mapping different user account types.

  • Identity (column IdentityType)

    The identity describes the type of user account.

    Table 26: Identities of User Accounts
    Identity Description Value of the column "IdentityType"
    Primary identity Employee's default user account. Primary
    Organizational identity Secondary user account used for various roles within the organization, f. ex. In sub-agreements with other functional areas. Organizational
    Personalized admin identity User account with administration rights used by one person. Admin
    Sponsored identity User account used for example for training purposes. Sponsored
    Shared identity User account with administration rights used by several people. Shared
    Service identity Service account. Service
  • Privileged user account (column IsPrivilegedAccount)

    Use this option to flag user accounts with special, privileged permissions. This includes administrative user accounts or service accounts, for example. This option is not used to flag default user accounts.

Default User Accounts

Normally, each employee obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the employee. The effect of the link and the scope of the employee’s inherited properties on the user accounts can be configured through an account definition and its manage levels.

To create default user accounts through account definitions

  1. Create an account definition and assign the manage level "Unmanaged" or "Full managed" to it.
  2. Specify the effect of temporarily or permanently disabling, deleting or the security risk of an employee on its user accounts and group memberships for each manage level.
  3. Create a formatting rule for IT operating data.

    An account definition specifies which rules are used to generate the IT operating data for example, whether the container for a user account is made up of the employee's department, cost center, location or business role and which default values will be used if no IT operating data can be found through the employee's primary roles.

    Which IT operating data is required, depends on the target system. The following setting are recommended for default user accounts:

    • Use the default value "1" in the formatting rule for the column IsGroupAccount and set the option Always use default value.
    • Use the default value "primary" in the formatting rule for the column IdentityType and set the option Always use default value.
  4. Enter the effective IT operating data for the target system. Select the concrete target system under Effects on.

    Specify in the departments, cost centers, locations or business roles, which IT operating data should apply when you set up a user account.

  5. Assign the account definition to employees.

    When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.

Administrative User Accounts

An administrative user account must be used for certain administrative tasks. Administrative user accounts are normally predefined in the target system and have fixed identifiers and login names, for example, "Administrator".

Administrative user accounts are loaded through synchronization into the One Identity Manager. To assign a manager to administrative user accounts, assign an employee to the user account in One Identity Manager.

NOTE: You can automatically label administrative user accounts as privileged user accounts. To do this, set the schedule "Mark selected user accounts as privileged" in the Designer.

Privileged User Accounts

Privileged user accounts are used to provide employees with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are marked with the property Privileged user account (IsPrivilegedAccount).

NOTE: The criteria used to label user accounts automatically as privileged, are defined as extensions to the view definition (ViewAddOn) on the table TSBVAccountIsPrivDetectRule (table type "Union"). The evaluation is done in the script TSB_SetIsPrivilegedAccount.

To create privileged users through account definitions

  1. Create an account definition. Create a new manage level for privileged user accounts and assign this manage level to the account definition.
  2. If you want to prevent properties for privileged user accounts being overwritten, set the property IT operating data overwrites for the manage level, to the value "Only initially". In this case, the properties are populated just once when the user accounts is created.
  3. Specify the effect of temporarily or permanently disabling, deleting or the security risk of an employee on its user accounts and group memberships for each manage level.
  4. Create a formatting rule for IT operating data.

    An account definition specifies which rules are used to generate the IT operating data for example, whether the container for a user account is made up of the employee's department, cost center, location or business role and which default values will be used if no IT operating data can be found through the employee's primary roles.

    Which IT operating data is required, depends on the target system. The following settings are recommended for privileged user accounts:

    • Use the default value "1" in the formatting rule for the column IsPrivilegedAccount and set the option Always use default value.
    • You can also specify a formatting rule for the column IdentityType. The column owns different permitted values, which represent user accounts.
    • To prevent privileged user accounts inheriting default user groups, define a template for the column IsGroupAccount with the default value "0" and set the option Always use default value.
  5. Enter the effective IT operating data for the target system.

    Specify in the departments, cost centers, locations or business roles, which IT operating data should apply when you set up a user account.

  6. Assign the account definition directly to employees who work with privileged user accounts.

    When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.

NOTE: Specify a formatting rule for a naming schema if it is required by the company for privileged user account login names.

To use a prefix with a login name, set the configuration parameter "TargetSystem\AzureAD\Accounts\PrivilegedAccount\AccountName_Prefix" in the Designer. To use a postfix with a login name, set the configuration parameter "TargetSystem\AzureAD\Accounts\PrivilegedAccount\AccountName_Postfix" in the Designer.

These configuration parameters are evaluated in the default installation, if a user account is marked with the property Privileged user account (IsPrivilegedAccount). The user account login names are renamed according to the formatting rules. This also takes place if the user accounts are labeled as privileged by the schedule "Mark selected user accounts as privileged".

Related Documents