Chat now with support
Chat with Support

Active Roles 7.5.3 - 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 One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect 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 Office 365 Groups Managing Azure Security 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 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: Enabling Federated Authentication Appendix F: Active Roles integration with other One Identity and Quest products Appendix G: Active Roles integration with Duo Appendix H: Active Roles integration with Okta

Appendix D: Active Roles and supported Azure environments

Active Roles supports 3 different Azure environment configurations: Non-federated, Synchronized identity, and Federated.

Non-federated

In a non-federated environment, 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 environments, the changes made in Active Roles are immediately replicated to Azure or Office 365 using Graph API Calls or Command-let calls. Users or Guest Users are typically created in Azure with the onmicrosoft.com UPN suffix.

Example: Non-federated environment configuration

A non-federated environment 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 user or guest 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 environments for testing purposes only, and does not recommend setting them up as a live production environment.

Synchronized identity

In a Synchronized identity environment, 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 148: Synchronized identity configuration

Synchronized Identity configuration

Example: Synchronized identity configuration

A synchronized identity environment 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 user is created in Active Roles with the ID of user001@test.local and in Azure as user001@rd4.qsftdemo.com.

Federated

In a federated environment, 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. Users and Guest Users are typically created with the UPN suffix of the selected on-premises domain.

Figure 149: Federated configuration

Federated environment configuration

Example: Federated 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 User is created in Active Roles and Azure AD with the same ID of user001@rd4.qsftdemo.com.

Azure Object Management supported in various Azure environments

This section provides information about the supported operations and methods for performing the operations for Azure objects in various Azure environments using Active Roles Web interface, such as Federated, Synchronized Identity, and Non-Federated environments.

In Active Roles Web interface, the required Azure environment configuration can be selected during the Azure tenant creation. The specified configuration can be modified later if needed by changing the Azure properties of the tenant.

Active Roles identifies the environment based on the Azure Tenant type and applies the changes to the Web interface.

 

 

Azure Object Management in Non-Federated environment

Non-federated environment is used generally for testing purposes. In non-federated environment, most of the Azure properties can be modified, other than attributes such as UserPrincipalName and ObjectId which identify the object uniquely.

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 118: Supported Azure configurations comparison chart
Object Operation Non-Federated : Method
User Create Using GRAPH API
Read Using GRAPH API and Exchange Online Command-lets
Update Using GRAPH API and Exchange Online Command-lets
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 Command-lets
Read Using GRAPH API
Update Using GRAPH API
Delete Using GRAPH API
Distribution Group Create Using Exchange Online Command-lets
Read Using GRAPH API
Update Using GRAPH API
Delete Using GRAPH API

Native Office 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 Command-lets
Read Using GRAPH API
Update Using Exchange Online Command-lets
Delete Using GRAPH API

 

NOTE: *Active Roles provides cloud-only support only for Office 365 Groups management.

Azure Object Management in Federated and Synchronized Identity environments

Synchronization methods are applicable only in Synchronized and Federated environments and AAD Connect is used to perform the synchronization. Azure non-federated environment does not require synchronization and the direct GRAPH API calls are used to make the Azure or Office 365 object management.

The following table provides information about the operations and methods of operation that can be performed on Azure Objects in Federated and Synchronized Identity environments.

Table 119: 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 Command-lets
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 Synced 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 Synced 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 Synced to Active Roles, Synced using AAD Connect
Read

 

 

 Using GRAPH API
Update

 

 

 Synced using AAD Connect
Delete

 

 

 Using GRAPH API

Native Office 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:

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

  • Synced using AAD Connect referenced in the table specifies that the object operation is initially performed on the on-premise object . After a Microsoft Azure AD Connect synchronization cycle, the object is updated in Azure AD or Office 365.

  • For more information on how to perform Back Sync operation refer Active Roles Configuration to synchronize existing Azure AD objects to Active Roles in the Active Roles Administration Guide.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating