Active Directory
A set of directory-based technologies included in Windows Server.
6,846 questions
Any update ?
API-driven inbound provisioning to on-premises AD - Unable to assign Manager
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 87%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELJ%3C/text%3E%3C/svg%3E)
Linu John
0
Reputation points
API-driven inbound provisioning to on-premises AD - Unable to assign Manager
We have configured API-driven inbound provisioning to the on-premises Active Directory (AD), and it is functioning as expected. However, we have identified an issue: whenever a new user is created using the provisioning API, attempting to assign a manager who is an existing user in AD located in a different organizational unit (OU) results in the following error.
However, this issue does not occur when assigning a manager who was created through the provisioning service, even if they exist in a different BU .
Error Message from provisioning Log
We were unable to assign xxx@*** as the manager of xxxx@**** . In order to ensure that the references are updated properly, you have two options. First, ensure that xxxx@xxxxx is in scope for provisioning. Provision xxxx@**** on-demand and then provision xxxx@xxxxx on-demand. Alternatively, you can restart provisioning after ensuring that xxx@**** is in scope for provisioning.*
PropertyName
manager
SkipReason
UnableToResolveReferenceAttributeValue
manager Add
The error is asking to do scoping on-demand however on-demand scoping feature is not available in API-driven inbound provisioning .