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
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.
|
NOTE: AzureADTenantType can be Federated, Non Federated, or Synchronized depending on the customer's environment. |
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Use this parameter to set the 'name' attribute to this parameter value on the new object created by this cmdlet in the directory.
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
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. |
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Use this parameter to specify the required description for the Azure AD tenant.
Required |
false |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
|
NOTE: The Administrative user must have the required privileges to perform license management and Azure user and group management. |
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Use this parameter to specify the administrative user name for Microsoft Azure AD.
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Accepts value |
|
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
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'
Use this cmdlet to add an Azure AD application.
Parameters
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.
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Use this parameter to set the 'name' attribute to this parameter value on the new object created by this cmdlet in the directory.
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
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. |
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Use this parameter to specify the 'displayName' attribute to this parameter value.
Required |
false |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Use this parameter to specify the permission scope for applications for Azure AD.
Required |
true |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
Use this parameter to specify the description of the Azure AD application.
Required |
false |
Position |
named |
Accepts pipeline input |
false |
Accepts wildcard characters |
false |
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
To configure Active Roles to manage Hybrid AD objects, perform the following tasks:
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:
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.
For information on configuring Synchronization workflows for Azure AD, see One Identity Active Roles Synchronization Service Administration Guide.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책