Chat now with support
Chat with Support

Active Roles 8.1.2 - Administration Guide

Introduction 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
Provisioning Policy Objects Deprovisioning Policy Objects How Policy Objects work Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning Exchange Mailbox AutoProvisioning AutoProvisioning in SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Microsoft 365 and Azure Tenant Selection E-mail Alias Generation 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
Using rule-based and role-based tools for granular administration Workflows
Key workflow features and definitions 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 Configure 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 Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Managing Hybrid AD users
Creating a new Azure AD user with the Web Interface Viewing or updating the Azure AD user properties with the Web Interface Viewing or modifying the manager of a hybrid Azure user Disabling an Azure AD user Enabling an Azure AD user Deprovisioning of an Azure AD user Undo deprovisioning of an Azure AD user Adding an Azure AD user to a group Removing an Azure AD user from a group View the change history and user activity for an Azure AD user Deleting an Azure AD user with the Web Interface Creating a new hybrid Azure user with the Active Roles Web Interface Converting an on-premises user with an Exchange mailbox to a hybrid Azure user Licensing a hybrid Azure user for an Exchange Online mailbox Viewing or modifying the Exchange Online properties of a hybrid Azure user Creating a new Azure AD user with Management Shell Updating the Azure AD user properties with the Management Shell Viewing the Azure AD user properties with the Management Shell Delete an Azure AD user with the Management Shell Assigning Microsoft 365 licenses to new hybrid users Assigning Microsoft 365 licenses to existing hybrid users Modifying or removing Microsoft 365 licenses assigned to hybrid users Updating Microsoft 365 licenses display names
Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Microsoft 365 roles management for hybrid environment users Managing Microsoft 365 contacts Managing Hybrid AD groups Managing Microsoft 365 Groups Managing cloud-only distribution groups Managing cloud-only dynamic distribution 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 cloud-only shared mailboxes
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 Communication ports Active Roles and supported Azure environments Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Access to Active Roles Web Interface

To access the Active Roles Web Interface through a firewall, open the following ports:

  • Port 80 (Default HTTP) TCP Inbound/Outbound

  • Port 443 (Default HTTPS) TCP Inbound/Outbound

The Web Interface normally runs over port 80, or over port 443 if SSL is enabled (off by default).

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 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 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 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 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 266: 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 Azure 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. Azure users and guest users are typically created with the onmicrosoft.com UPN suffix of the selected on-premises domain.

Figure 267: 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 Azure 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 Azure object operations and methods in various Azure environments using the Active Roles Web Interface. Active Roles supports Non-federated, Federated and Synchronized Identity environments.

You can select the Azure environment configuration type in the Active Roles Configuration Center when creating the Azure tenant, as described in Configuring a new Azure tenant and consenting Active Roles as an Azure application. You can modify the configuration type later by changing the Azure properties of the tenant.

Active Roles identifies the environment based on the Azure tenant type and applies the changes accordingly.

Azure object management in a Non-Federated environment

A Non-federated environment is typically used for testing purposes. In a Non-federated environment, most of the Azure properties can be modified, with the exception of attributes that uniquely identify the object (such as UserPrincipalName and ObjectId).

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 143: 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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating