Active Roles 7.4.1 - Administration Guide

Add an Azure AD tenant using Mgt Shell

Add an Azure AD Tenant

You can use the Active Roles Management Shell to add an Azure AD tenant.

To add an Azure AD tenant

On the Management Shell interface, run the New-QADAzureConfigObject cmdlet.

Synopsis

This cmdlet enables you to add an Azure AD tenant to Active Directory.

Syntax

New-QADAzureConfigObject -type 'AzureTenant' -name 'Azuretenantname' -AzureTenantId 'AzureTenantGUID' -AzureTenantDescription 'AzureTenantDescription' -AzureAdminUserID 'AzureGlobalAdminUserID' -AzureAdminPassword 'AzureGlobalIDPassword' -AzureADTenantType 'AzureTenantType'

Description

Use this cmdlet to add an Azure AD tenant using the tenant ID provided by Microsoft for the default tenant created at the time of Microsoft Azure subscription.

Parameters

• type (string)

  Use this parameter to specify the object class of the directory object to be created. This is the name of a schema class object, such as User or Group. The cmdlet creates a directory object of the object class specified by the value of this parameter.

• name (string)

  Use this parameter to set the 'name' attribute to this parameter value on the new object created by this cmdlet in the directory.

• AzureTenantId (string)

  Use this parameter to enter the Azure AD tenant ID obtained from the default tenant created after subscribing for Microsoft Azure.

• AzureTenantDescription

  Use this parameter to specify the required description for the Azure AD tenant.

• AzureAdminUserID

  Use this parameter to specify the administrative user name for Microsoft Azure AD.

• AzureAdminPassword

  Use this parameter to specify the administrative user name for Microsoft Azure AD.

Example

Connect to any available domain controller with the credentials of the locally logged on user, and create a new Azure AD tenant:

C:\PS> New-QADAzureConfigObject -type 'AzureTenant' -name 'CompanyAzuretenant' -AzureTenantId 'CompanyAzureTenantID' -AzureTenantDescription 'Azure tenant for Company' -AzureAdminUserID 'AzureAdminUser1' -AzureAdminPassword 'AzureAdminPassword1’ -AzureADTenantType 'AzureTenantType'

Example

Connect to the local Administration Service with the credentials of a specific user, create a new Azure AD tenant and then disconnect:

C:\PS> $pw = read-host "Enter password" -AsSecureString

C:\PS> connect-qadService -service 'localhost' -proxy -ConnectionAccount 'company\administrator' -ConnectionPassword $pw

C:\PS> New-QADAzureConfigObject -type 'AzureTenant' -name 'CompanyAzuretenant' -AzureTenantId 'CompanyAzureTenantID' -AzureTenantDescription 'Azure tenant for Company' -AzureAdminUserID 'AzureAdminUser1' -AzureAdminPassword 'AzureAdminPassword1’ -AzureADTenantType 'AzureTenantType'

C:\PS> disconnect-qadService

Add an Azure AD Application

You can use the Active Roles Management Shell to add an Azure AD application to the Azure AD tenant.

To add an Azure AD application

On the Management Shell interface, run the New-QADConfigObject cmdlet.

Synopsis

This cmdlet enables you to add an Azure AD application to the Azure AD tenant.

Syntax

New-QADAzureConfigObject -type 'AzureApplication' -name 'AzureApplication' -DisplayName 'ApplicationDisplayName' -AzureTenantId 'AzureTenantGUID' -AzureAppPermissions 'ApplicationPermission'

Description

Use this cmdlet to add an Azure AD application.

Parameters

• type (string)

  Use this parameter to specify the object class of the directory object to be created. This is the name of a schema class object, such as User or Group. The cmdlet creates a directory object of the object class specified by the value of this parameter.

  Table 103: Parameters: type (string)

  Required	true
  Position	named
  Accepts pipeline input	false
  Accepts wildcard characters	false

• name (string)

  Use this parameter to set the 'name' attribute to this parameter value on the new object created by this cmdlet in the directory.

  Table 104: Parameters: name (string)

  Required	true
  Position	named
  Accepts pipeline input	false
  Accepts wildcard characters	false

• AzureTenantId (string)

  Use this parameter to enter the Azure AD tenant ID obtained from the default tenant created after subscribing for Microsoft Azure.

  NOTE: The values entered for configuring Azure AD tenant must exactly match the values configured for Azure AD, else Azure AD application creation and management of Azure AD objects fail.

  Table 105: Parameters: AzureTenantId (string)

  Required	true
  Position	named
  Accepts pipeline input	false
  Accepts wildcard characters	false

• Displayname (string)

  Use this parameter to specify the 'displayName' attribute to this parameter value.

  Table 106: Parameters: Displayname (string)

  Required	false
  Position	named
  Accepts pipeline input	false
  Accepts wildcard characters	false

• AzureAppPermissions

  Use this parameter to specify the permission scope for applications for Azure AD.

  Table 107: Parameters:AzureAppPermissions

  Required	true
  Position	named
  Accepts pipeline input	false
  Accepts wildcard characters	false

• AzureApplicationDescription

  Use this parameter to specify the description of the Azure AD application.

  Table 108: Parameters: AzureApplicationDescription

  Required	false
  Position	named
  Accepts pipeline input	false
  Accepts wildcard characters	false

Example

Connect to any available domain controller with the credentials of the locally logged on user, and create a new Azure AD application:

C:\PS> New-QADAzureConfigObject -type 'AzureApplication' -name 'AzureApplication' -DisplayName 'ApplicationDisplayName' -AzureTenantId 'AzureTenantGUID' -AzureAppPermissions 'ApplicationPermission'

Example

Connect to the local Administration Service with the credentials of a specific user, create a new Azure AD tenant and then disconnect:

C:\PS> $pw = read-host "Enter password" -AsSecureString

C:\PS> connect-qadService -service 'localhost' -proxy -ConnectionAccount 'company\administrator' -ConnectionPassword $pw

C:\PS> New-QADAzureConfigObject -type 'AzureApplication' -name 'AzureApplication' -DisplayName 'ApplicationDisplayName' -AzureTenantId 'AzureTenantGUID' -AzureAppPermissions 'ApplicationPermission'

C:\PS> disconnect-qadService

Active Roles Configuration steps

Active Roles Configuration steps to manage Hybrid AD objects

To configure Active Roles to manage Hybrid AD objects, perform the following tasks:

1. Create an Azure AD tenant.
2. Create the Azure AD application.
3. Provide the administrator consent for the Azure AD application.
4. Enforce the Built-in Policy - Azure - Default Rules to Generate Properties Policy Object to the on-premises Active Directory containers, which are synchronized to Azure AD.
5. Edit the edsvaAzureOffice365Enabled attribute for the Azure OU and set the value to “True”.
   1. In the console tree, go to the Organizational Unit you want to modify.
   2. Right-click the Organizational Unit, and then click Properties to display the Properties dialog box for that Organizational Unit.
   3. On the Properties dialog box, go to the Object tab and click Advanced Properties.
   4. From the list of available attributes, search and click on the attribute edsvaAzureOffice365Enabled.
   5. In the Edit Attribute dialog box, set the value to True.
   6. To set the attribute for all the Child organizational units, select the check box corresponding to All Child Organizational Units, and click OK.

Active Roles Configuration to synchronize

Active Roles Configuration to synchronize existing Azure AD objects to Active Roles

In any hybrid environment, on-premises Active Directory objects are synchronized to Azure AD using some means such as Azure AD Connect. When Active Roles 7.4 is deployed in such a hybrid environment, the existing users and groups' information, such as Azure objectID, must be synchronized back from Azure AD to on-premises AD to continue using the functionality. To synchronize existing AD users and groups from Azure AD to Active Roles we must use the back-synchronization operation.

The back-synchronization operation can be perfomed automatically or manually using the Active Roles Active Roles Synchronization Service Console:

• Automatic Back Synchronization is performed using the Azure Backsync Configuration feature in Active Roles Synchronization Service that allows you to configure the backsync operation in Azure with on-premises Active Directory objects through the Active Roles Synchronization Service Console. After the backsync operation is completed successfully the Azure application registration and the required connections, mappings, and sync workflow steps are created automatically.

  For information on configuring the backsync operation automatically using the Active Roles Synchronization Service Console, see Configuring Sync Workflow to back-synchronize Azure AD Objects to Active Roles automatically using the Active Roles Synchronization Service Console.

  For more information on the results of the backsync operation see the One Identity Active Roles Synchronization Service Administration Guide.

• Manual Back Synchronization is performed by leveraging the existing functionality of Synchronization Service component of Active Roles. Synchronization workflows are configured to identify the Azure AD unique users or groups and map them to the on-premises AD users or groups. After the back-synchronization operation is completed, Active Roles displays the configured Azure attributes for the synchronized objects.

  For information on configuring Synchronization workflows for Azure AD, see One Identity Active Roles Synchronization Service Administration Guide.