I have a custom object class in FIM with several external MAs connected. Provisioning is done by both FIM (with outbound sync and 'create object in external system') and by projection from external MA with MV extension rule New objects coming from FIM are created in external systems once original object falls into sync scope filtered by a set. There's an MPR to add outbound sync rule for such objects. Another MPR removes this rule then object leaves a set. and objects are deleted(disconnected) in external systems as well. but if I would delete an object in FIM - deprovisioning doesn't happen.. Actually object is first deleted from MV during delta sync and then it immediately comes back provisioned by external MA to MV and then exported to FIM :) I believe that this behavior is correct but... just wondering: how to trigger deprovision event on FIM object deletion?

Welcome to convergence :o) As long as you have an ERL on the MV object that points to an outbound synchronization rule, the object is reprovisioned. There are two options to prevent this from happening: Delete the metaverse object Bring the metaverse object out of the scope of a synchronization rule To delete the metaverse object, you need to configure the object deletion rule: To bring a metaverse object out of the scope of a metaverse object, you need a workflow. This is the same process you have used to bring the object into the scope of a synchronization rule: Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Markus, I've run into the same problem as the OP, the declarative deprovisioning doesn't seem to deal with deletes in FIM Portal I have a synch rule, an MPR and a workflow configured to fire off on new user creation and add object to synch rule scope - that works and provisions it to AD fine. Another MPR and workflow catch employment status change, and if it changes out of Contractor or Full Time Employee a deprovision gets triggered, also works fine. However, the deletion from FIM Portal doesn't trigger a deprovision - the user is instead re-synched from MV into FIM Portal on the next run of FIMMA - neither the status change MPR nor the object deletion MPR seem to get triggered on deletion, so ERL pointing to an outgoing synch rule remains and the object gets reprovisioned. (if I set object deletion in MV object deletion rules that catches it fine, but was hoping to use declaritive all the way) Regards, thanks Petar