Why does OIM provision assignements on AADGroup.OnPremisesSyncEnabled = true?

I've just seen the following behavior:

 

I have set a person to isInActive, so it looses all the assigned groups on AD and AAD Accounts.

 

On the AAD Account there are some cloud only groups and some hybrid groups (coming from on prem AD) assigned.

 

So, it makes sense, that the cloud only groups are removed from the AAD account.

 

But the hybrid Groups (AADGroup.OnPremisesSyncEnabled = true) are managed over on prem AD and AAD Connect. So there shouldn't be any provisioning directly to AAD.

 

Now I'm wondering how I should handle this situation.

- Should I prevent that AADUserInGroup could be deleted at all, if it is not the "Synchronization" User performing that action?

- Should I do some special SyncProject Configuration? (having a schema on OIM side, that excludes that hybrid groups, ...)

- Any other approach?

 

 

I consider this problem as a quite common one, and I'm wondering that OIM is trying to maintain members for hybrid groups at all, since this would be never successful .

  • Hi Rodney,

    The insert/remove to those tables will still happen.  What I have described simply inhibits the provisioning.

    Cheers, B.

  • Okay in that case we still need VPR#34448 (I have no access to see what it entails) which I hope will make sure that:

    • Block these actions in the UI.
    • Process wise block editing of objects that are synced from the on premise AD.
    • Block editing actions on Azure AD objects that are solely managed by Azure AD like dynamic membership groups etc.
    • Make sure that the relevant tables (AADUser, AADGroup, AADUSerInGroup) are consistent and do not need a target system synchronization to get to a consistent state.

    This issue exists already for years without publicly visible progress, I will keep on playing DJ and click end with error in the job queue info tool.