I've got some problems with an MPR not working as expected. I have the following situation: Set: AllAccounts (contains all accounts of type user, test, service, ... based on a string attribute accountType) set: AllUserAccounts (contains all accounts of type user based on a string attribute accountType) MPR: transition in AllAccounts: run workflow: add SR: Provision AD Account (create account in AD) MPR: transition in AllUserAccounts: run workflow: add SR: Provision User Specific properties (adds extra attributes) SR: Provision User specific properties is configured to depend on SR Provision AD Account We are talking newly added users to the portal, so the "run on policy update" should not be required. Whenever a new user appears in the portal the SR Provision AD Account is added, and eventually applied. I would expect the other SR to be added shortly after, however this never happens. I am aware that the users simultaniously is "member" of both sets, but I would expect this to work out ok. The SR is added if I check "run on policy update" and enable/disable the MPR. But that can't be the way to go. Any thoughts where I'm going wrong? http://setspn.blogspot.com

This is because you have your SRs in different MPRs. When you look through your requests, you will probably find some PostProcessingErrors: This is because when AllUserAccounts MPR is processed, a dependent component doesn't exist. The idea of this feature is to avoid that in a list of SRs, the synchronization engine tries to apply a SR if a dependent SR has not been applied yet. To fix this, put your SRs into one workflow. Cheers, Markus