AAD Connect v2 Group Writeback

[petben]

I have an OU in our local AD containing Azure groups that have been written back by the Azure AAD Sync client. The OU contains ALL our groups, but now the v2 AAD connect sync client is released it can sync only groups enabled for write back.

 

Can someone please tell me if it's OK to:

 

1. Stop the sync
   
2. Delete all the local AD created groups
   
3. Set the v2 writeback to enabled
   
4. Start the sync
   

 

Then surely the OU will populate with just groups enabled to write back?

Assure me I definitely will not be deleting any Azure groups? It's a one way sync..?

 

Thanks

[kevin_lane]

Before doing anything drastic I would just test can you not create a group,

 

 

 

Is it breaking anything at the moment ?

 

 

 

I have an OU in our local AD containing Azure groups that have been written back by the Azure AAD Sync client. The OU contains ALL our groups, but now the v2 AAD connect sync client is released it can sync only groups enabled for write back.

 

Can someone please tell me if it's OK to:

 

1. Stop the sync
   
2. Delete all the local AD created groups
   
3. Set the v2 writeback to enabled
   
4. Start the sync
   

 

Then surely the OU will populate with just groups enabled to write back?

Assure me I definitely will not be deleting any Azure groups? It's a one way sync..?

 

Thanks

[petben]

I can create a group yes. I’ve moved on a bit.

 

- I’ve set new groups to not write back

- client group write back v2 is now set as true

- only 1 test group is set as write back true

 

But I delete any group in the local AD OU where groups are synced to, run a sync and the group reappears.

 

Something must be misconfigured..

[HPlum78]

Bit off topic, but what would be really useful in group write back is the ability to use it to write back into Builtin Local groups. Then we would be able to leverage PIM in EntraID and have the members of these groups updated based on those groups and requests.