Chat now with support
Chat with Support

Active Roles 8.0 LTS - Administration Guide

Introduction About Active Roles Getting Started Rule-based Administrative Views Role-based Administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based Access Rules
Rule-based AutoProvisioning and Deprovisioning
About Policy Objects Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning E-mail Alias Generation Exchange Mailbox AutoProvisioning AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 and Azure Tenant Selection User Account Deprovisioning Office 365 Licenses Retention Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Workflows
Understanding workflow Workflow activities overview Configuring a workflow
Creating a workflow definition Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configuring an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Example: Approval workflow E-mail based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic Groups Active Roles Reporting Management History
Understanding Management History Management History configuration Viewing change history
Workflow activity report sections Policy report items Active Roles internal policy report items
Examining user activity
Entitlement Profile Recycle Bin AD LDS Data Management One Identity Starling Management Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Azure AD, Office 365, and Exchange Online management
Configuring Active Roles to manage hybrid AD objects Managing Hybrid AD Users Unified provisioning policy for Azure O365 Tenant Selection, Office 365 License Selection, and Office 365 Roles Selection, and OneDrive provisioning Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Microsoft 365 Groups Managing Azure Security Groups Managing cloud-only distribution groups Managing cloud-only Azure users Managing cloud-only Azure guest users Managing cloud-only Azure contacts Changes to Active Roles policies for cloud-only Azure objects Managing room mailboxes Managing cloud-only shared mailboxes
Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
SQL Server Replication Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Active Roles integration with other One Identity and Quest products Appendix F: Active Roles integration with Duo Appendix G: Active Roles integration with Okta Active Roles Language Pack

Managing Microsoft 365 Groups

Active Roles supports CRUD (create, read, update and delete) operations for Microsoft 365 (M365) groups and also lets you specify owners and add/remove members to or from existing M365 groups in your organization.

M365 groups facilitate teamwork within an organization by providing the same set of permissions to (guest) users, allowing you to provide access efficiently to various shared resources (such as a common Microsoft Outlook inbox and calendar, a shared OneNote notebook, or other Microsoft 365 resources). For more information on M365 groups, see Overview of Microsoft 365 Groups for administrators in the Microsoft 365 documentation.

You can administer M365 groups either via the Active Roles Web Interface or through the Active Roles Management Shell.

Configuring M365 Groups with the Web Interface

You can use the Active Roles Web Interface to:

  • Create, view, modify or delete Microsoft 365 (M365) groups in your organization.

  • Assign or remove owners and members to or from existing M365 groups.

  • View the change history of existing M365 groups.

NOTE: You cannot use the Active Roles Web Interface to synchronize existing M365 groups. To synchronize M365 groups, configure an M365 synchronization schedule task with the Active Roles Console (also known as the MMC Interface). For more information, see Scheduling an Azure object synchronization task.

Creating an M365 Group with the Web Interface

You can use the Active Roles Web Interface to create and enable new Microsoft 365 (M365) groups.

For more information on M365 groups, see Overview of Microsoft 365 Groups for administrators in the Microsoft 365 documentation.

To create a new M365 group

  1. Navigate to Directory Management > Tree > Azure > <azure-tenant-name> > Microsoft 365 Groups.

    The list of existing M365 groups in the selected Azure tenant appears.

    NOTE: When opening the list of Microsoft 365 Groups the first time, Active Roles checks and fetches all existing M365 groups that may exist in the Azure cloud. This action is performed automatically and may take a few minutes to complete.

  2. In the right-side pane, click New Group.

    The New Group in Microsoft 365 Groups window appears.

  3. Specify the Group Azure Display Name of the configured group.

    TIP: You can configure multiple groups with the same Group Azure Display Name in the same Azure tenant.

  4. Specify the Exchange Online Alias of the M365 group. This value is used for naming the SharePoint site URL of the M365 group, and will also name the primary email address of the shared mailbox associated with the M365 group.

    TIP: The Alias of the M365 group must be unique within the Azure tenant.

  5. Provide a short Description for the group.

  6. Configure the Membership type of the group:

    • Assigned: When selected, you can add or remove members to or from the group manually later. For more information, see Adding or removing members from an M365 Group with the Web Interface.

    • Dynamic Members: When selected, Active Roles sets up the group as a dynamic membership group, and will automatically update group membership based on the configured Dynamic membership rule syntax.

    TIP: Consider the following when configuring the Membership type:

    • Select Dynamic Members to quickly configure a group based on a certain membership logic. For example, if you need to set up a group for employees from the same geographical location, business unit, or functional area, One Identity recommends configuring the group with Dynamic Members.

    • If you select Dynamic Members, you will not be able to manually add or remove members to or from the M365 group, unless you change its Membership type to Assigned later. However, you can still manually configure the owner(s) for a dynamic M365 group, as described in Adding or removing owners from an M365 Group with the Web Interface.

    • You can always change the Membership type later by navigating to the following option of the Active Roles Web Interface:

      Directory Management > Tree > Azure > <azure-tenant-name> > Microsoft 365 Groups > <m365-group-name> > Azure Properties > General.

    • Changing the Membership type from Dynamic Members to Assigned later will keep the last set of members that were dynamically assigned to the group.

  7. If you set the Membership type to Dynamic Members, specify the Dynamic membership rule syntax. Active Roles will send the logic configured in this field to Azure to automatically assign or remove members to or from the group later.

    NOTE: Consider the following when using the Dynamic membership rule syntax setting:

    • This setting is enabled only if Membership type is set to Dynamic Members. However, in that case, it is mandatory and cannot be empty.

    • The specified dynamic membership rule must meet all rule syntax requirements, otherwise the window will return an error. For more information on the available membership rule properties, operators and values, see Dynamic membership rules for groups in Azure Active Directory in the Microsoft 365 documentation.

    • Whenever you modify the dynamic membership rule of a dynamic M365 group, it can take several minutes for Azure to update the list of group members in the Directory Management > Tree > Azure > <azure-tenant-name> > Microsoft 365 Groups > <m365-group-name> > Dynamic Members window.

  8. To complete the configuration of the new M365 group, click Finish.

    The new M365 group will appear under the Directory Management > Tree > Azure > <azure-tenant-name> > Microsoft 365 Groups node.

Modifying an M365 Group with the Web Interface

You can use the Active Roles Web Interface to modify the Azure properties of existing Microsoft 365 (M365) groups in your Azure tenant. This is typically useful if you must:

  • Modify the display name of the M365 group, for example because of an organizational change.

  • Change the configured membership type (manually assigned or dynamic) of the M365 group.

NOTE: You cannot change the Exchange Online alias of an existing M365 group.

To modify the Azure properties of an M365 group

  1. Navigate to Directory Management > Tree > Azure > <azure-tenant-name> > Microsoft 365 Groups.

    The list of existing M365 groups in the selected Azure tenant appears.

    NOTE: When opening the list of Microsoft 365 Groups the first time, Active Roles checks and fetches all existing M365 groups that may exist in the Azure cloud. This action is performed automatically and may take a few minutes to complete.

  2. Select the group that you want to configure.

  3. In the right-side pane, click Azure Properties.

  4. In the left-side pane of the Azure Properties window, click Properties.

  5. (Optional) Specify the Group Azure Display Name of the configured group.

    TIP: You can configure multiple groups with the same Group Azure Display Name in the same Azure tenant.

  6. (Optional) Provide a short Description for the group.

  7. (Optional) Configure the Membership type of the group:

    • Assigned: When selected, you can add or remove members to or from the group manually later. For more information, see Adding or removing members from an M365 Group with the Web Interface.

    • Dynamic Members: When selected, Active Roles sets up the group as a dynamic membership group, and will automatically update group membership based on the configured Dynamic membership rule syntax.

    TIP: Consider the following when configuring the Membership type:

    • Select Dynamic Members to quickly configure a group based on a certain membership logic. For example, if you need to set up a group for employees from the same geographical location, business unit, or functional area, One Identity recommends configuring the group with Dynamic Members.

    • If you select Dynamic Members, you will not be able to manually add or remove members to or from the M365 group, unless you change its Membership type to Assigned later. However, you can still manually configure the owner(s) for a dynamic M365 group, as described in Adding or removing owners from an M365 Group with the Web Interface.

    • Changing the Membership type from Dynamic Members to Assigned later will keep the last set of members that were dynamically assigned to the group.

  8. (Optional) If you set the Membership type to Dynamic Members, specify the Dynamic membership rule syntax. Active Roles will send the logic configured in this field to Azure to automatically assign or remove members to or from the group later. For more information on how to specify a membership rule, see Dynamic membership rules for groups in Azure Active Directory in the Microsoft 365 documentation.

  9. To apply your changes, click Save.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating