Chat now with support
Chat mit Support

Active Roles 8.2 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Configuring rule-based autoprovisioning and deprovisioning
Configuring Provisioning Policy Objects
User Logon Name Generation E-mail Alias Generation Exchange Mailbox AutoProvisioning Group Membership AutoProvisioning Home Folder AutoProvisioning Property Generation and Validation Script Execution O365 and Azure Tenant Selection AutoProvisioning in SaaS products
Configuring Deprovisioning Policy Objects
User Account Deprovisioning Group Membership Removal User Account Relocation Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Permanent Deletion Office 365 Licenses Retention Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Script Execution Notification Distribution Report Distribution
Configuring entry types Configuring a Container Deletion Prevention policy Configuring picture management rules Managing Policy Objects Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Configuring policy extensions
Using rule-based and role-based tools for granular administration Workflows
About workflow processes Workflow processing overview Workflow activities overview Configuring a workflow
Creating a workflow definition for a workflow 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
Approval workflow Email-based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic groups Active Roles Reporting Management History Entitlement profile Recycle Bin AD LDS data management One Identity Starling Join and configuration through Active Roles Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Migrating Active Roles configuration with the Configuration Transfer Wizard Managing Skype for Business Server with Active Roles
About Skype for Business Server User Management Active Directory topologies supported by Skype for Business Server User Management User Management policy for Skype for Business Server User Management Master Account Management policy for Skype for Business Server User Management Access Templates for Skype for Business Server Configuring the Skype for Business Server User Management feature Managing Skype for Business Server users
Exchanging provisioning information with Active Roles SPML Provider Monitoring Active Roles with Management Pack for SCOM Configuring Active Roles for AWS Managed Microsoft AD Azure AD, Microsoft 365, and Exchange Online Management
Azure tenant types and environment types supported by Active Roles Using Active Roles to manage Azure AD objects Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Changes to Active Roles policies for cloud-only Azure objects
Managing the configuration of Active Roles
Connecting to the Administration Service 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 Using regular expressions Administrative Template Configuring federated authentication Communication ports and URLs used by Active Roles Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Azure AD, Microsoft 365, and Exchange Online Management

Active Roles facilitates the administration and provisioning of Active Directory (AD), Exchange, and Azure AD resources in on-premises, cloud-only and hybrid environments as well. You can manage all these resources through the Active Roles Web Interface.

  • In an on-premises environment, when you create new AD objects (users, guest users, groups, contacts, and so on), Active Roles creates and stores these new objects in the local infrastructure of your organization.

  • In a cloud-only environment, when you create new AD objects (users, guest users, groups, contacts, and so on), Active Roles creates and stores these new objects in the Azure Cloud.

  • In hybrid environments, when you create new AD objects (users, guest users, contacts, and so on) Active Roles synchronizes the on-premises AD objects and their properties to the AD cloud. This synchronization is performed by the Active Roles Synchronization Service between Active Roles and Microsoft Microsoft 365, whenever you configure an AD object with the Active Roles Web Interface.

NOTE: Active Roles Web Interface supports AD-related operations only on sites based on the Administrators template. While some of the configuration procedures described in this document are also supported through the Active Roles Management Shell, they are all described with using the Active Roles Web Interface.

Fore more information about the management of Azure AD, Microsoft 365, and Exchange Online objects, see Managing Azure AD, Microsoft 365, and Exchange Online objects in the Active Roles Web Interface User Guide.

Azure tenant types and environment types supported by Active Roles

Active Roles supports 3 Azure tenant types:

  • Non-federated

  • Synchronized identity

  • Federated

In addition, Active Roles supports 2 Azure tenant environment types for all 3 supported Azure tenant types:

  • Azure Cloud

  • Azure US Government

For more details on the supported tenant environment types, see Compare Azure Government and global Azure in the Microsoft Azure documentation.

Non-federated tenants

In a non-federated tenant, the on-premises domains are not registered in Azure AD, and neither Azure AD Connect nor any third-party synchronization tools are configured in the domain for synchronization. In non-federated tenants, the changes made in Active Roles are immediately replicated to Azure or Microsoft 365 using Graph API calls or cmdlet calls. Azure users or guest users are typically created with the onmicrosoft.com UPN suffix.

Example: Non-federated tenant configuration

A non-federated tenant may have the following settings:

  • On-premises domain: test.local

  • Azure AD Domain: ARSAzure.onmicrosoft.com

  • Azure AD Connect is not configured for synchronization.

The on-premises domain is not registered in Azure. The Azure user is created in Active Roles with the ID of user001@test.local and in Azure as user001@ARSAzure.onmicrosoft.com. The user is created in Azure simultaneously when it is created in Active Roles using a Graph API call.

NOTE:One Identity recommends using non-federated tenants for testing purposes only, and does not recommend setting them up as a live production environment.

For the supported Azure operations and methods, see Azure object management in non-federated Azure tenants.

Synchronized identity tenants

In a synchronized identity tenant, the on-premises domain is optionally registered in Azure AD, while Azure AD Connect is configured to synchronize the local AD objects to Azure. Azure users or guest users are typically created either with the selected on-premises domain or with the onmicrosoft.com UPN suffix.

Figure 150: Synchronized identity configuration

Synchronized Identity configuration

Example: Synchronized identity tenant configuration

A synchronized identity tenant may have the following settings:

  • On-premises domain: test.local

  • Azure AD Domain: rd4.qsftdemo.com

  • Azure AD Connect is configured for synchronization.

The on-premises domain is optionally registered in Azure. The Azure user is created in Active Roles with the ID of user001@test.local and in Azure as user001@rd4.qsftdemo.com.

For the supported Azure operations and methods, see Azure object management in Federated and Synchronized Identity Azure tenants.

Federated tenants

In a federated tenant, the on-premises domain is always registered in Azure AD, while Azure AD Connect and Active Directory Federation Services (ADFS) are configured to facilitate synchronization. Azure users and guest users are typically created with the onmicrosoft.com UPN suffix of the selected on-premises domain.

Figure 151: Federated configuration

Federated environment configuration

Example: Federated tenant configuration

A federated configuration may have the following settings:

  • On-premises domain: rd4.qsftdemo.com

  • Azure AD Domain: rd4.qsftdemo.com

  • Azure AD Connect and ADFS are configured for synchronization.

The on-premises domain is registered and verified in Azure. The Azure user is created in Active Roles and Azure AD with the same ID of user001@rd4.qsftdemo.com.

For the supported Azure operations and methods, see Azure object management in Federated and Synchronized Identity Azure tenants.

Azure object management in non-federated Azure tenants

In a non-federated Azure tenant, you can modify most Azure properties of Azure objects, with the exception of attributes that uniquely identify the object (such as UserPrincipalName and ObjectId).

NOTE:One Identity recommends using non-federated tenants for testing purposes only, and does not recommend setting them up as a live production environment.

The following table provides information about the operations and methods of operation that can be performed on Azure objects in a Non-federated environment.

Table 79: Supported Azure configurations comparison chart
Object Operation Non-Federated : Method

User

Create Using Graph API
Read Using Graph API and Exchange Online cmdlets
Update Using Graph API and Exchange Online cmdlets
Delete Using Graph API

Guest User

Create Using Graph API
Read Using Graph API
Update Using Graph API
Delete Using Graph API

Security Group

Create Using Graph API
Read Using Graph API
Update Using Graph API
Delete Using Graph API

Mail Enabled Security Group

Create Using Exchange Online cmdlets
Read Using Graph API
Update Using Graph API
Delete Using Graph API

Distribution Group

Create Using Exchange Online cmdlets
Read Using Graph API
Update Using Graph API
Delete Using Graph API

Native Microsoft 365 Group (Cloud-only)

Create

 Using Graph API

Read

 Using Graph API

Update

 Using Graph API

Delete

 Using Graph API

Contacts

Create Using Exchange Online cmdlets
Read Using Graph API
Update Using Exchange Online cmdlets
Delete Using Graph API

NOTE: Active Roles provides cloud-only support only for Native Microsoft 365 Groups management.

Azure object management in Federated and Synchronized Identity Azure tenants

The following synchronization methods are applicable only to synchronized identity and federated Azure tenants, with Azure AD Connect used to perform the synchronization.

NOTE: Non-federated Azure tenants do not require synchronization. In such tenants, Active Roles uses direct Graph API calls to perform Azure AD or Microsoft 365 object management.

Table 80: Supported Azure configurations comparison chart
Object Operation

Commands

Tabs

 Federated/Synchronized : Method
User Create

 

 

 Created by Graph API
Read

 

 

 Using Graph API and Exchange Online cmdlets
Update Azure properties

Identity

Synced using AAD Connect

Settings

Using Graph API

Job Info

Synced using AAD Connect

Contact Info

Synced using AAD Connect

Licenses

Using Graph API

O365 Admin Roles

Using Graph API

OneDrive

Created by OneDrive Policy using PowerShell commands

Exchange Online properties

Mail Flow Settings

Using Exchange Online cmdlets

Delegation

Using Exchange Online cmdlets

E-mail Address

Synced using AAD Connect

Mailbox Features

Using Exchange Online cmdlets

Mailbox Settings

Using Exchange Online cmdlets

Delete

 

 

 Using Graph API

Guest Users

Create

Invite Guest

 

 Created by Graph API

Read

 

 

 Using Graph API

Update

Azure properties

Identity

Synced using AAD Connect

Settings

Using Graph API

Job Info

Synced using AAD Connect

Contact Info

Synced using AAD Connect

Licenses

Using Graph API

O365 Admin Roles

Using Graph API

Exchange Online properties

Mail Flow Settings

Using Exchange Online cmdlets

Delegation

Using Exchange Online cmdlets

E-mail Address

Synced using AAD Connect

Mailbox Features

Using Exchange Online cmdlets

Mailbox Settings

Using Exchange Online cmdlets

Delete

 

 

Using Graph API

Security Group Create

 

 

  • Created in Azure.

  • Back synchronized to Active Roles.

  • Synced using AAD Connect.

Read

 

 

 Using Graph API
Update

 

 

 Synced using AAD Connect
Delete

 

 

 Using Graph API
Mail Enabled Security Group Create

 

 

  • Created in Azure.

  • Back synchronized to Active Roles.

  • Synced using AAD Connect.

Read

 

 

 Using Graph API
Update

 

 

 Synced using AAD Connect
Delete

 

 

 Using Graph API
Distribution Group Create

 

 

  • Created in Azure.

  • Back synchronized to Active Roles.

  • Synced using AAD Connect.

Read

 

 

 Using Graph API
Update

 

 

 Synced using AAD Connect
Delete

 

 

 Using Graph API

Native Microsoft 365 Group (Cloud-only)

Create

 

 

Using Graph API

Read

 

 

Using Graph API

Update

 

 

Using Graph API

Delete

 

 

Using Graph API

Contacts Create

 

 

 Synced using AAD Connect
Read

 

 

 Using Graph API
Update

 

 

 Synced using AAD Connect
Delete

 

 

 Using Graph API

NOTE: Consider the following when using federated and synchronized identity Azure tenants:

  • Active Roles provides cloud-only support only for Native Microsoft 365 Group management.

  • "Synced using AAD Connect" in the table means that the object operation is initially performed on the on-premises object. Once the Microsoft Azure AD Connect synchronization cycle is completed, the object is updated in Azure AD or Microsoft 365.

  • For more information on how to perform back synchronization, see Configuring Active Roles to synchronize existing Azure AD objects.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen