Active Roles 7.2 - Azure Active Directory and Office 365 Administrator Guide

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 7: 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 8: 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 9: 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 10: 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 11: 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 12: 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 'Application1' -name 'CompanyApplication' -DisplayName 'ApplicationDisplayName' -AzureTenantId 'CompanyAzureID' -AzureAppPermissions 'CompanyAppPermission'

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 'Application1' -name 'CompanyApplication' -DisplayName 'ApplicationDisplayName' -AzureTenantId 'CompanyAzureID' -AzureAppPermissions 'CompanyAppPermission'

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 AD objects to Azure AD

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.1 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.

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 Administrator Guide.

Pre-requisites to configure the back-synchronization:

• The hybrid environment must have Azure AD Connect installed and configured.
• Synchronization Service Component must be installed and configured for Active Roles.
• Azure AD configuration and the Administrator Consent for Azure AD application through web interface must be complete.
• Azure AD built-in policy must be enforced and the attribute edsvaazureOffice365enabled must be set to true for the container where the back-synchronization is performed.

Configuring Sync Workflow to back-synchronize

Configuring Sync Workflow to back-synchronize Azure AD Objects to Active Roles

To configure sync workflow to back-synchronize users perform the following steps:

• Step 1: Create Connection to Azure AD in the hybrid environment.
• Step 2: Create Connection to Active Roles in the hybrid environment
• Step 3: Create Sync Work flow
• Step 4: Create Mapping

Step 1: Create Connection to Azure AD in the hybrid environment

Create a connection to Azure AD using the Azure AD Connector. The configuration requires the Azure domain name, the Client ID of an application in Azure AD, and the Client Key to establish the connection with Azure AD.

To configure an application:

1. Create an Azure Web application (or use any relevant existing Azure Web Application) under the tenant of your Windows Azure Active Directory environment.

   The application must have "Application Permissions" to "read" and "write" directory data in Windows Azure Active Directory.

   NOTE: Alternatively, to assign the required permissions to the application by running a Windows PowerShell script, see the Creating a Windows Azure Active Directory connection section in Sync Service Guide.

2. Open the application properties and copy the following:

• Client ID
• Valid key of the application

3. You need to supply the copied client ID and key when creating a new or modifying an existing connection to Windows Azure Active Directory in the Synchronization Service Administration Console.

Step 2: Create Connection to Active Roles in the hybrid environment

Create a connection to Active Roles using the Active Roles Connector. The configuration requires the local domain details and Active Roles version used. Define the scope to select the container from which the objects for synchronization must be selected.

Step 3: Create Sync Work flow

Create a Sync Workflow using the Azure AD and Active Roles connections. Add a Synchronization step to Update Azure User/Group to Active Roles User/Group. Configure the Forward Sync Rule to synchronize the following:

• Azure ObjectID property of a user/group to the Active Roles user/group edsvaAzureObjectID property.
• Set the edsvaAzureOffice365Enabled attribute in Active Roles user/group to True.

Step 4: Create Mapping

Create a Mapping Rule which identifies the user/group in Azure AD and on-premises AD uniquely and map the specified properties from Azure AD to Active Roles appropriately.

For example, the property userprincipalname can be used to map users between on-premises AD and Azure AD in a federated environment.