On Azure, synchronizing nested groups (groups with groups inside) into ServiceNow imports empty records
Azure allows you to create groups with groups are group members (nested). However, on ServiceNow, the system only allows you to add Users on the group form. When synchronizing nested groups with ServiceNow, Azure creates empty records on the instance group form.
You recognize this problem because:
- You have Azure setup with groups with groups as members (beside users)
- You have setup a synchronization with a ServiceNow instance
- You will see empty user records being created on the parent group
The problem is caused because ServiceNow group form does not allow nested groups, or groups inside groups. Group members can only be Users. On Azure, the Groups allow both groups and users. However, Azure does not differentiate or add the members of the nested groups, instead it try to create them as members.
Please note Azure is not a ServiceNow product. For specific questions on the synchronization process, please contact Microsoft support.
To resolve this problem, please ensure on Azure to that any Group added to the synchronization, does not have any groups inside any other group, or nested. Instead, add the member of those nested groups into the parent group.
To accomplish this:
- Copy all the users members of the nested group into the parent.
- Remove the nested group from the group
- Repeat as many times as nested groups present.
|Note: Azure is not a ServiceNow product. For specific questions on the synchronization process, please contact Microsoft support.|