The customer has a hybrid Office365 implementation. When adding an O365 provisioning role to a global user, the expected behavior is that the user is retrieved from O365 and licenses added.
But the connector fails with:
20180831:100701:TID=a7bb70:Add :S316:C314:F: FAILURE: Connector Server Add (eTDYNAccountName=XXX) rc: 0x0013 (Constraint violation)
msg: Connector Server Add failed: code 19 (CONSTRAINT_VIOLATION): failed to add entry eTDYNAccountName=XXX,eTDYNAccountContainerName=Accounts,eTDYNDirectoryName=Office365,eTNamespaceName=Office 365,dc=im,dc=etasa: [email protected]
+APL94: O365: Failed to add account [XXX].
[new-msoluser : You must provide a required property: Parameter name: FederatedUser.SourceAnchor]
As they have set the Hybrid Mode for their endpoint.
Into the jcs_conn_Office365 log after the following line:
DEBUG - Adding Office 365 Account....
we should have the following one:
DEBUG - Updating Office 365 Hybrid Account: XXX
But we do not have.
Everything processed as if the Hybrid Mode option is not considered as enabled.