Would the list have best practice advice on this?

An account disappears from the SQL data source, so it disappears from the SQL MA CS and Metaverse but I left it as a disconnector in the AD MA CS, thinking it would just "re-join!" (how naive!).

Not good it turns out as that leads to the "reverse join" problem. There is no AD MA CS connector if it reappears in the Metaverse so the Metaverse extension crashes as it tries to provision it but the object already exists in the AD MA CS, albeit as a disconnector, which can't be seen by the the DLL.

Is it best to clean everything out if an account has to be deprovisioned? e.g. delete the object from the SQL MA CS, Metaverse and AD MA CS?

If it reappears in the SQL data source, it'll go through initial flow again, which may not be a good idea (for us anyway).

I know it's really bad practice to initiate deprovisioning on a lack of data but things are as they are.

thanks,

Alistair

########################################################################

To unsubscribe from the MICROSOFT-IDENTITY list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=MICROSOFT-IDENTITY&A=1

This message was issued to members of www.jiscmail.ac.uk/MICROSOFT-IDENTITY, a mailing list hosted by www.jiscmail.ac.uk, terms & conditions are available at https://www.jiscmail.ac.uk/policyandsecurity/