Chat now with support
Chat with Support

Identity Manager 9.3 - Administration Guide for Connecting to Microsoft Entra ID

Managing Microsoft Entra ID environments Synchronizing a Microsoft Entra ID environment
Setting up initial synchronization with a Microsoft Entra ID tenant Adjusting the synchronization configuration for Microsoft Entra ID environments Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization Pausing handling of target system specific processes (Offline mode)
Managing Microsoft Entra ID user accounts and identities Managing memberships in Microsoft Entra ID groups Managing Microsoft Entra ID administrator roles assignments Managing Microsoft Entra ID subscription and Microsoft Entra ID service plan assignments
Displaying enabled and disabled Microsoft Entra ID service plans forMicrosoft Entra ID user accounts and Microsoft Entra ID groups Assigning Microsoft Entra ID subscriptions to Microsoft Entra ID user accounts Assigning disabled Microsoft Entra ID service plans to Microsoft Entra ID user accounts Inheriting Microsoft Entra ID subscriptions based on categories Inheritance of disabled Microsoft Entra ID service plans based on categories
Login credentials for Microsoft Entra ID user accounts Microsoft Entra ID role management
Microsoft Entra ID role management tenants Enabling new Microsoft Entra ID role management features Microsoft Entra ID role main data Main data of Microsoft Entra ID role settings Displaying Microsoft Entra ID role settings main data Assigning temporary access passes to Microsoft Entra ID user accounts Displaying Microsoft Entra ID scoped role assignments Displaying scoped role eligibilities for Microsoft Entra ID roles Overview of Microsoft Entra ID scoped role assignments Main data of Microsoft Entra ID scoped role assignments Managing Microsoft Entra ID scoped role assignments Adding Microsoft Entra ID scoped role assignments Editing Microsoft Entra ID scoped role assignments Deleting Microsoft Entra ID scoped role assignments Assigning Microsoft Entra ID scoped role assignments Assigning Microsoft Entra ID scoped role assignments to Microsoft Entra ID user accounts Assigning Microsoft Entra ID scoped role assignments to Microsoft Entra ID groups Assigning Microsoft Entra ID scoped role assignments to Microsoft Entra ID service principals Assigning Microsoft Entra ID system roles to scopes through role assignments Assigning Microsoft Entra ID business roles to scopes though role assignments Assigning Microsoft Entra ID organizations to scopes through role assignments Overview of Microsoft Entra ID scoped role eligibilities Main data of Microsoft Entra ID scoped role eligibilities Managing Microsoft Entra ID scoped role eligibilities Adding Microsoft Entra ID scoped role eligibilities Editing Microsoft Entra ID scoped role eligibilities Deleting Microsoft Entra ID scoped role eligibilities Assigning Microsoft Entra ID scoped role eligibilities Assigning Microsoft Entra ID scoped role eligibilities to Microsoft Entra ID user accounts Assigning Microsoft Entra ID scoped role eligibilities to Microsoft Entra ID groups Assigning Microsoft Entra ID scoped role eligibilities to Microsoft Entra ID service principals Assigning Microsoft Entra ID system roles to scopes through role eligibilities Assigning Microsoft Entra ID business roles to scopes though role eligibilities Assigning Microsoft Entra ID organizations to scopes through role eligibilities
Mapping Microsoft Entra ID objects in One Identity Manager
Microsoft Entra ID core directories Microsoft Entra ID user accounts Microsoft Entra ID user identities Microsoft Entra ID groups Microsoft Entra ID administrator roles Microsoft Entra ID administrative units Microsoft Entra ID subscriptions and Microsoft Entra ID service principals Disabled Microsoft Entra ID service plans Microsoft Entra ID app registrations and Microsoft Entra ID service principals Reports about Microsoft Entra ID objects Managing Microsoft Entra ID security attributes
Handling of Microsoft Entra ID objects in the Web Portal Recommendations for federations Basic data for managing a Microsoft Entra ID environment Troubleshooting Configuration parameters for managing a Microsoft Entra ID environment Default project template for Microsoft Entra ID Editing Microsoft Entra ID system objects Microsoft Entra ID connector settings

Adding Microsoft Entra ID groups automatically to the IT Shop

The following steps can be used to automatically add Microsoft Entra ID groups to the IT Shop. Synchronization ensures that the Microsoft Entra ID groups are added to the IT Shop. If necessary, you can manually start synchronization with the Synchronization Editor. New Microsoft Entra ID groups created in One Identity Manager also are added automatically to the IT Shop.

To add Microsoft Entra ID groups automatically to the IT Shop

  1. In the Designer, set the QER | ITShop | AutoPublish | AADGroup configuration parameter.

  2. In order not to add Microsoft Entra ID groups to the IT Shop automatically, in the Designer, set the QER | ITShop | AutoPublish | AADGroup | ExcludeList configuration parameter.

    This configuration parameter contains a listing of all Microsoft Entra ID groups that should not be allocated to the IT Shop automatically. You can extend this list if required. To do this, enter the names of the groups in the configuration parameter. Names are listed in a pipe (|) delimited list. Regular expressions are supported.

  3. Compile the database.

The Microsoft Entra ID groups are added automatically to the IT Shop from now on.

The following steps are run to add a Microsoft Entra ID group to the IT Shop.

  1. A service item is determined for the Microsoft Entra ID group.

    The service item is tested for each Microsoft Entra ID group and modified if necessary. The name of the service item corresponds to the name of the Microsoft Entra ID group.

    • The service item is modified for Microsoft Entra ID groups with service items.

    • Microsoft Entra ID groups without service items are allocated new service items.

  2. The service item is assigned to either the Microsoft Entra ID groups | Security groups default service category or the Microsoft Entra ID groups | Distribution groups default service category.

  3. An application role for product owners is determined and assigned to the service item.

    Product owners can approve requests for membership in these Microsoft Entra ID groups. The default product owner is the Microsoft Entra ID group's owner.

    NOTE: The application role for the product owner must be added under the Request & Fulfillment | IT Shop | Product owner application role.

    • If the owner of the Microsoft Entra ID group is already a member of an application role for product owners, this application role is assigned to the service item. Therefore, all members of this application role become product owners of the Microsoft Entra ID group.

    • If the owner of the Microsoft Entra ID group is not yet a member of an application role for product owners, a new application role is created. The name of the application corresponds to the name of the owner.

      • If the owner is a user account, the user account's identity is added to the application role.

      • If it is a group of owners, the identities of all this group's user accounts are added to the application role.

  4. The Microsoft Entra ID group is labeled with the IT Shop option and assigned to the IT Shop groups Microsoft Entra ID shelf in the Identity & Access Lifecycle shop.

Then the shop customers can use the Microsoft Entra ID to request memberships in Web Portal groups.

NOTE: If a Microsoft Entra ID group is irrevocably deleted from the One Identity Manager database, the associated service item is also deleted.

For more information about configuring the One Identity Manager IT Shop Administration Guide, see the IT Shop. For more information about requesting access requests in the Web Portal, see the One Identity Manager Web Portal User Guide.

Related topics

Assigning Microsoft Entra ID user accounts directly to Microsoft Entra ID groups

To react quickly to special requests, you can assign groups directly to user accounts. You cannot directly assign groups that have the Only use in IT Shop option.

NOTE: User accounts cannot be manually added to dynamic groups.

To assign user accounts directly to a group

  1. In the Manager, select the Microsoft Entra ID > Groups category.

  2. Select the group in the result list.

  3. Select the Assign user accounts task.

  4. In the Add assignments pane, assign the user accounts.

    TIP: In the Remove assignments pane, you can remove assigned user accounts.

    To remove an assignment

    • Select the user account and double-click .

  5. Save the changes.
Related topics

Assigning Microsoft Entra ID groups directly to Microsoft Entra ID user accounts

To react quickly to special requests, you can assign groups directly to user accounts. You cannot directly assign groups that have the Only use in IT Shop option.

NOTE: User accounts cannot be manually added to dynamic groups.

To assign groups directly to user accounts

  1. In the Manager, select the Microsoft Entra ID > User accounts category.

  2. Select the user account in the result list.

  3. Select the Assign groups task.

  4. In the Add assignments pane, assign the groups.

    TIP: In the Remove assignments pane, you can remove the assignment of groups.

    To remove an assignment

    • Select the group and double-click .

  5. Save the changes.
Related topics

Effectiveness of group memberships

When groups are assigned to user accounts an identity may obtain two or more groups, which are not permitted in this combination. To prevent this, you can declare mutually exclusive groups. To do this, you specify which of the two groups should apply to the user accounts if both are assigned.

It is possible to assign an excluded group at any time either directly, indirectly, or with an IT Shop request. One Identity Manager determines whether the assignment is effective.

NOTE:

  • You cannot define a pair of mutually exclusive groups. That means, the definition "Group A excludes group B" AND "Group B excludes groups A" is not permitted.
  • You must declare each group to be excluded from a group separately. Exclusion definitions cannot be inherited.
  • One Identity Manager does not check if membership of an excluded group is permitted in another group ( table).

The effectiveness of the assignments is mapped in the AADUserInGroup and AADBaseTreeHasGroup tables by the XIsInEffect column.

Example: The effect of group memberships
  • Group A is defined with permissions for triggering requests in a tenant. A group B is authorized to make payments. A group C is authorized to check invoices.
  • Group A is assigned through the "Marketing" department, group B through "Finance", and group C through the "Control group" business role.

Jo User1 has a user account in this tenant. They primarily belong to the "Marketing" department. The "Control group" business role and the "Finance" department are assigned to them secondarily. Without an exclusion definition, the user account obtains all the permissions of groups A, B, and C.

By using suitable controls, you want to prevent an identity from being able to trigger a request and to pay invoices. That means, groups A, B, and C are mutually exclusive. An identity that checks invoices may not be able to make invoice payments as well. That means, groups B and C are mutually exclusive.

Table 14: Specifying excluded groups (AADGroupExclusion table)

Effective group

Excluded group

Group A

Group B

Group A

Group C

Group B

Table 15: Effective assignments

Identity

Member in role

Effective group

Pat Identity1

Marketing

Group A

Jan User3

Marketing, finance

Group B

Jo User1

Marketing, finance, control group

Group C

Chris User2

Marketing, control group

Group A, Group C

Only the group C assignment is in effect for Jo User1. It is published in the target system. If Jo User1 leaves the "control group" business role at a later date, group B also takes effect.

The groups A and C are in effect for Chris User2 because the groups are not defined as mutually exclusive. That means that the identity is authorized to trigger requests and to check invoices. If this should not be allowed, define further exclusion for group C.

Table 16: Excluded groups and effective assignments

Identity

Member in role

Assigned group

Excluded group

Effective group

Chris User2

 

Marketing

Group A

 

Group C

 

Control group

Group C

 Group B

Group A

Prerequisites

  • The QER | Structures | Inherite | GroupExclusion configuration parameter is set.

    In the Designer, set the configuration parameter and compile the database.

    NOTE: If you disable the configuration parameter at a later date, model components and scripts that are no longer required, are disabled. SQL procedures and triggers are still carried out. For more information about the behavior of preprocessor relevant configuration parameters and conditional compiling, see the One Identity Manager Configuration Guide.

  • Mutually exclusive groups belong to the same tenant.

To exclude a group

  1. In the Manager, select the Microsoft Entra ID > Groups category.

  2. Select a group in the result list.

  3. Select the Exclude groups task.

  4. In the Add assignments pane, assign the groups that are mutually exclusive to the selected group.

    - OR -

    In the Remove assignments pane, remove the groups that are no longer mutually exclusive.

  5. Save the changes.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating