You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Synchronises Orchestrator users with Windows Active Directory, based on AD group membership mapped to Orchestrator Roles.
3
+
Synchronises Orchestrator users with Windows or Azure Active Directory, based on AD group membership mapped to Orchestrator Roles.
4
4
.DESCRIPTION
5
-
You provide the AD domain name and a mapping from relevand AD groups to Orchestrator Roles.
6
5
New users in AD are added to Orchestrator and existing users added moved to the correct Role.
6
+
Azure AD users are matched by comparing the Azure AD user principal name with the user Email in Orchestrator.
7
7
The script also handles removing Orchestrator users from roles when they were removed from the corresponding AD group.
8
8
AD users that were removed from all relevant AD groups (eg. an employee that changed role) or were removed from AD (eg. a former employee that left the company) become 'orphaned users'. They are still defined in Orchestrator but do not have any Role. The script supports the -OrphanedUsersAction parameter allowing to optionally List or Remove these users.
9
9
The script is idempotent, repeated invocations should not modify the Orchestrator users unless something changed in AD.
10
10
You should first import the UiPath.PowerShell module and authenticate yourself with your Orchestrator using Get-UiPathAuthToken before running this script.
11
+
The script does not modify the Admin user roles membership, even if the Email matches the AzureAD domains. This is a common scenario and can result in accidentally locking Admin user out of Administrators group.
12
+
The script adds new Orchestrator users using the Azure AD DisplayName as Name and leaves Surname empty. It does not try to split the DisplayName and figure out the Surname.
11
13
.PARAMETERDomainName
12
-
The domain to sync users with. It does not necessarily has to be your current user or machine domain, but there must be some trust relationship so your Windows session can discover and interogate this domain AD.
14
+
The Windows domain to sync users with. It does not necessarily has to be your current user or machine domain, but there must be some trust relationship so your Windows session can discover and interogate this domain AD.
15
+
.PARAMETERAzureAD
16
+
Use currently connected Azure AD for sync. You must first connect the PowerShell session to Azure AD using Connect-AzureAD
13
17
.PARAMETERRolesMapping
14
18
A Hashtable mapping AD groups to Orchestrator roles. Make sure you type the names correctly.
15
19
.PARAMETEROrphanedUsersAction
16
20
Optional action to handle orphaned users. You can List or Remove these users.
21
+
.PARAMETERAllowUsernameTruncate
22
+
Optional switch to allow truncation of imported usernames to 32 characters, the Orchestrator username length limit.
Import AD users from MyDomain and maps the members of the 'RPA Admins' AD group to the 'Administrator' Orchestrator role and members of the 'RPA Users' AD group to the 'User' Orchestrator role.
Import AD users from MyDomain and maps the members of the 'RPA Admins' AD group to the 'Administrator' Orchestrator role and members of the 'RPA Users' AD group to the 'Users' Orchestrator role.
Import AD users from Azure Active Directory and maps the members of the 'RPA Admins' Azure AD group to the 'Administrator' Orchestrator role and members of the 'RPA Users' Azure AD group to the 'Users' Orchestrator role.
Import AD users from MyDomain but since there is no mapping, the effect is to orphan all exiting Orchestrator MyDomain users and then remove them because of the -OrphanedUsersAction Remove parameter. In effect this invocation removes all MyDomain users from Orchestrator.
Deletes all Azure Active Directory managed users from Orchestrator.
35
+
Important notice: this will remove any user in Orchestrator that has an Email domain matching the Azure AD domain, even if it was not imported from Azure AD.
0 commit comments