Azure Active Directory tenant
You must provide details about your organization the first time you register for a Microsoft cloud service. This detailed information is used to make a new Azure Active Directory directory partition. The organization represents one Azure Active Directory tenant. In One Identity Manager, you can edit the main data of each Azure Active Directory tenant. However, you cannot create new Azure Active Directory tenants in One Identity Manager.
To edit Azure Active Directory tenant main data
-
In the Manager, select the Azure Active Directory > Tenants category.
-
In the result list, select the Azure Active Directory tenant.
-
Select the Change main data task.
-
Edit the Azure Active Directory tenant's main data.
- Save the changes.
Detailed information about this topic
General main data of Azure Active Directory tenants
Enter the following data on the General tab.
Table 23: Azure Active Directory tenant main data
Display name |
The Azure Active Directory tenant’s display name. |
Account definition (initial) |
Initial account definition for creating Azure Active Directory user accounts. This account definition is used if automatic assignment of employees to user accounts is used for this Azure Active Directory tenant and user accounts should be created which are already managed (Linked configured state). The account definition's default manage level is applied.
User accounts are only linked to the employee (Linked) if no account definition is given. This is the case on initial synchronization, for example. |
Target system managers |
Application role, in which target system managers are specified for the Azure Active Directory tenant. Target system managers only edit the objects from Azure Active Directory tenants to which they are assigned. Each Azure Active Directory tenant can have a different target system manager assigned to it.
Select the One Identity Manager application role whose members are responsible for administration of this Azure Active Directory tenant. Use the button to add a new application role. |
Location |
The Azure Active Directory tenant's location. |
Street |
Street or road. |
City |
City. |
Zip code |
Zip code. |
Country |
Country. |
Synchronized by |
Type of synchronization through which the data is synchronized between the Azure Active Directory tenant and One Identity Manager. You can no longer change the synchronization type once objects for this Azure Active Directory tenant are present in One Identity Manager.
If you create an Azure Active Directory tenant with the Synchronization Editor, One Identity Manager is used.
Table 24: Permitted values
One Identity Manager |
Azure Active Directory connector |
Azure Active Directory connector |
No synchronization |
none |
none |
NOTE: If you select No synchronization, you can define custom processes to exchange data between One Identity Manager and the target system. |
Recipients (marketing notifications) |
List of recipients of marketing notifications. |
Recipient (technical notifications) |
List of recipients of technical notifications. |
Recipients (security notifications) |
List of recipients of security notifications. |
Phone numbers (security notifications) |
Phone numbers for security notifications. |
Related topics
Information about local Active Directory
The Linked tab shows information about the local Active Directory, which is linked to the Azure Active Directory tenant.
Table 25: Local Active Directory user account data
Synchronization with local Active Directory enabled |
Specifies whether synchronization with a local Active Directory is enabled. |
Last synchronization |
Time of the last Azure Active Directory tenant synchronization with the local Active Directory. |
Defining categories for the inheritance of entitlements
In One Identity Manager, user accounts can selectively inherit groups, administrator roles, subscriptions, and disabled service plans. To do this, the groups (administrator roles, subscriptions, and disabled service plans) and the user accounts are divided into categories. The categories can be freely selected and are specified using a mapping rule. Each category is given a specific position within the template. The mapping rule contains different tables. Use the user account table to specify categories for target system dependent user accounts. In the other tables, enter your categories for the groups, administrator roles, subscriptions, and disabled service plans. Each table contains the category positions position 1 to position 63.
To define a category
-
In the Manager, select the Azure Active Directory tenant in the Azure Active Directory > Tenants category.
-
Select the Change main data task.
-
Switch to the Mapping rule category tab.
-
Extend the relevant roots of a table.
-
To enable the category, double-click .
-
Enter a category name of your choice for user accounts and groups (administrator roles, subscriptions, disabled service plans) in the login language that you use.
- Save the changes.
Related topics