What to do with existing manually created group after getting group from Azure AD?

[aaddgg454]

Hi All,

1. what to do with the existing ticket having old manually created group populate on their assignment group ?

2. Roles that we have gave to groups manually?

[Ankur Bawiskar]

@aaddgg454 

this is process related discussion which you should have with customer.

if they are planning to decommission manual groups then what happens to those group members.

Do they need to be migrated to groups created via AD and if yes then which one?

Once that is sorted you can have discussion about the roles.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[aaddgg454]

Customer want to as per ServiceNow what is the best practice ? How we gonna deal with the existing tickets ?

[Ankur Bawiskar]

@aaddgg454 

you can discuss for active tickets if they are supposed to be reassigned.

you need to check impact with regards to notifications, SLAs, etc while bulk updating.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Dr Atul G- LNG]

Hi @aaddgg454 

We are in manual fuss, and I can share my experience, as I’m currently working directly with ServiceNow on one of the projects.

Recommendation:

• AD Groups: Bring in the AD groups — these are best practice as they are easy to maintain and all members are verified via AD.

• Manual / Local Groups: Keep manual/local groups only if there are local users who don’t use SSO for the client (like I have in my current client).

• Cleanup: Delete all other manual groups and retain only AD groups wherever possible.

Bottom line: Keep local/manual groups only for local users; for everyone else, use AD groups.