We use the microsoft recommended, and supported configuration of using ms-DS-ConsistencyGUID for Sourceanchor and immutableID's in AADsync.

We use this configuration because we had multiple forests that were migrated out of, so their objectGUID (what ADManager keys off of by default) is no longer relevant to their ms-DS-consistency guid. This attribute makes it extremely easy to migrate to other forests or domains without having issues with immutableID's.

Currently it is impossible to manage these accounts with ADManager if the AD Object has been migrated and is using ms-ds-consistencyguid as the sourceanchor.

Please resolve or add this feature ASAP as this is majorly impacting our use of this product.