user import in azure fails with key error. about db-migration HOT 4 CLOSED

What does the azure_logs/groups/ folder contain?
Does the destination workspace have the groups defined, but missing the individual members?

From the logs, all the groups should exist but the members should be missing according to the stacktrace. However, it's unclear how the key error is generated here since we don't use that type of id for group / user membership.

from db-migration.

Does this environment use service principals?

from db-migration.

It looks like there's a service principal defined and assigned to a particular group, which is causing the issue here.
Is it possible to copy the group member response here? The logfile is under azure_log/groups/group_name file.

from db-migration.

Filtering out service principals and we will need a feature enhancement to move those over. It's current a feature request to get that supported.

from db-migration.