Error "Constraint Violation" or "Server unwilling to process" when committing a provisioning workflow.
Provisioning rule set for:
UserPrinciplename -> UserPrinciplename
This will violate the constraint of the attribute in the target domain as the attribute is stored as userpname@domainA.com and try to apply this to the target, whereas the resulting attribute should be userpname@domainB.com.
To modify the Workflow to allow the update of the userprincipalname attribute the following rule should be created.
In this example the prefix of the userprinciplename is from the source sAMAccountName attribute, other source attributes can be used (e.g. firstname.lastname):
Here you can add attributes and text to make up the userPrincipalname (or any other target attribute):