**YouTube** is an American [online video-sharing](https://en.wikipedia.org/wiki/Video_hosting_service "Video hosting service") [platform](https://en.wikipedia.org/wiki/Web_platform "Web platform") headquartered in [San Bruno, California](https://en.wikipedia.org/wiki/San_Bruno,_California "San Bruno, California")

cf3f59da-c081-4fab-99d2-f02e60e183b0.PNG

New users in AD are added to Orchestrator and existing users added are moved to the correct Role. Azure AD users are matched by comparing the Azure AD user principal name with the user Email in Orchestrator.

The script also handles removing Orchestrator users from roles when they were removed from the corresponding AD group. 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.

The script is idempotent, repeated invocations should not modify the Orchestrator users unless something changed in AD.

You should first import the UiPath.PowerShell module and authenticate yourself with your Orchestrator using Get-UiPathAuthToken before running this script.

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.

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.

This activity has been developed by Remus Rusanu, UiPath Software Architect.

Synchronizes Orchestrator users with Windows or Azure Active Directory, based on AD group membership mapped to Orchestrator Roles

Version	Release Date	Download Link
1.0.0	June 11, 2019
First version

Sync AD Users to Orchestrator