We've been using multiple outbound sync rules from one MV Object to provision multiple AD Accounts (of different types, with different DNs and AccountNames).



This has suddenly stopped working. We've gone over changes made and found none that should affect the provisioning.

Now, only one user account is provisioned in ADMA. We only get one provisioning-rules on the ADMA.

We use the same Relationship on the two Sync Rules, but different Inbound Scoping.

Any ideas?

I.e. what we are trying to accomplish is to provision several AD User accounts from one object in the MV.

This has been possible, and should be possible, using several Sync Rules. Shouldn't it?

We have now resolved this.

The solution was to not only use Inbound scoping, but also include the additional scoping attribute in the Relationship. So now we can provision, e.g., multiple AD accounts from one identity again.

• Marked as answer by Leo Erlandsson 20 hours 32 minutes ago

We have now resolved this.

The solution was to not only use Inbound scoping, but also include the additional scoping attribute in the Relationship. So now we can provision, e.g., multiple AD accounts from one identity again.

• Marked as answer by Leo Erlandsson Wednesday, February 11, 2015 3:14 PM