Active Roles 8.2.1 - Installation Guide

Prerequisites

• The computer where Active Roles Configuration Center is running must already have all Azure-specific prerequisite software installed. If any of the prerequisite software required for Azure AD management are missing, install them with the following steps:

  1. Navigate to Dashboard > Azure AD Configuration.

  2. Click Install Azure-specific Prereqs.

  3. In the table that appears, install any components whose Status is not Installed.

  4. To apply your changes, click Apply.

  After all prerequisite software are installed, the Install Azure-specific Prereqs link will disappear, and the Azure AD Configuration option will appear.

• The Active Roles Administration Service must be already running. If Configuration Center indicates that the service is not running, then:

  1. In the Active Roles Configuration Center, navigate to the Administration Service page.

  2. Click Start.

• You must have the following administrator account roles and permissions at minimum:

  • Application Administrator

  • Privileged Role Administrator

  However, One Identity recommends using an Azure AD administrator account with Global Administrator permission to perform the procedure.

To configure a new Azure tenant (or tenants) and set Active Roles as a consented Azure application

1. In the Active Roles Configuration Center, on the left pane, click Azure AD Configuration.

   

2. To start configuring a new Azure tenant, click Add.

3. From the Tenant Type drop-down, select the type of domain assigned to the new Azure tenant:

   • Non-Federated Domain: When selected, on-premises domains are not registered in Azure AD , and Azure AD Connect is not configured. Azure users and Azure guest users are typically created with the onmicrosoft.com UPN suffix.

   • Federated Domain: On-premises domains are registered in Azure AD and Azure AD Connect. Also, Active Directory Federation Services (ADFS) is configured. Azure users and Azure guest users are typically created with the UPN suffix of the selected on-premises domain.

   • Synchronized Identity Domain: On-premises domains may or may not be registered in Azure AD. Azure AD Connect is configured. Azure users and Azure guest users can be created either with the selected on-premises domain, or with the onmicrosoft.com UPN suffix.

4. From the Tenant Environment Type drop-down, select the type of environment you want to configure your Azure tenant in:

   • Azure Cloud

   • Azure US Government (for GCC and GCC-H tenants)

   For the differences between Azure Cloud and Azure US Government tenants, see Compare Azure Government and global Azure in the Microsoft Azure documentation.

5. Click Next.

6. Authenticate your Azure AD administrator account.

   • If you already used one or more Azure AD administrator accounts on your PC, select your account from the Pick an account list, then provide the account password. If you do not find your account in the list, specify your account by clicking Use another account.

   • If you have not used any Azure AD administrator accounts yet on the PC (for example, because you are configuring a fresh Active Roles installation), specify your account user name in the Sign in field, then provide your password.

   Upon successful authentication, the new Azure tenant appears in the list.

   

7. To manage the Azure tenant and its contents in the Active Roles Web Interface, you must consent Active Roles as an Azure application. To do so, click Consent next to the Azure tenant.

8. Authenticate your Azure AD administration account again. Depending on the type of Microsoft pop-up that appears (Pick an account or Sign in), either select the Azure AD account you used for adding the Azure tenant, or specify its user name and password again.

   NOTE: Make sure to specify the account used for adding the Azure tenant (that is, the account name listed under the Name column of the Azure tenant). Authenticating with another account will result in an error.

9. The standard Microsoft Permissions requested pop-up appears, listing all the permissions required for configuring Active Roles as an Azure application. To finish creating the Azure application, click Accept.

   Active Roles then authenticates every Azure AD administrative operation performed in the Azure tenant with a set of generated client ID and client secret.

   NOTE: Once you click Accept, Windows may show a Security Warning pop-up with the following message:

   The current webpage is trying to open a site on your intranet. Do you want to allow this?

   In such cases, clicking either Yes or No could freeze the pop-up dialog, but consenting the Azure tenant will finish without problem.

   This issue can occur in case the computer running Active Roles has incorrect browser settings. As a workaround, to get an up-to-date status of the state of the Azure tenant, close and restart the Active Roles Configuration Center after clicking Yes in the Security Warning pop-up.

   IMPORTANT: The Active Roles Administration Service creates the Entra ID application registration for Active Roles with the following required roles and permissions:

   • Privileged Authentication Administrator role is necessary to reset password of Entra ID users and to update any additional sensitive information of Entra ID users.

   • User Administrator role is necessary to create, update and delete an Entra ID user.

   • Exchange Administrator role, and administrator-consented Exchange.ManageAsApp and full_access_as_app application permissions are necessary for EXO related operations

     • Exchange.ManageAsApp application permission is for other EXO related functionalities of Active Roles.

     • full_access_as_app application permission is for EXO EWS functionalities of Active Roles.

   • RoleManagement.ReadWrite.Directory application permission is necessary to assign role to an Entra ID user.

   • Sites.FullControl.All application permission is necessary for OneDrive site creation for Entra ID users.

   The roles and permissions added by default are required for the Active Roles Administration Service to function as expected. Modifying these default roles and permissions might result in a configuration that is outside of the scope of the Active Roles Support Model.

   You can add additional permissions to the Entra ID application or remove any of them by signing in to the Azure Portal. For more information, see the Microsoft Entra ID application management documentation.

10. If you have additional Azure tenants to add and consent, configure them as described in the previous steps of this procedure.

11. To make the configured Azure tenant(s) appear in the Active Roles Web Interface, you must restart the Administration Service. To restart the Administration Service, open the Configuration Center, click Administration Service on the left pane, then either click Restart, or first click Stop and then Start.