Fix Group ID Not Found - Sync 365 / Azure AD

Group Mapping Error – Group ID Not Found

Error: GroupId not found – Username to Database update

This error occurs when a custom license or contact filter in Sync 365 is configured to use a Microsoft Entra ID (Azure AD) group that no longer exists or has been renamed.


Cause: The group reference used in Sync 365 (by display name or ID) does not match any group currently available in the customer’s Entra ID (Azure AD) tenant.

Resolution

To resolve the issue, fix the group reference by checking both Sync 365 and Microsoft Entra:

  1. Login to the customer’s Microsoft Entra portal
  2. Navigate to Groups and confirm the group exists
  3. Update the group name in Sync 365 to match the correct group in Entra ID:
    • Go to Custom Licenses or Contact Filters in Sync 365
    • Edit the group name to match what’s in the tenant

Once the group reference is corrected, rerun the license sync or wait for the next scheduled update.

    • Related Articles

    • Catalog Item # not found

      Error: Catalog Item 14830 not found This error occurs when trying to update an agreement and the SKU does not exist in the PSA. Cause: A product referenced in your billing profile no longer exists or is marked inactive in your PSA (e.g., ConnectWise, ...

    • Master Index Page for Troubleshooting Microsoft 365 Errors

      Troubleshooting Microsoft 365 Errors If you've received an error in Sync 365 related to authentication, consent, token refresh, or license sync, use the links below to find the exact resolution. Authentication& MFA Errors AADSTS50078 – MFA expired ...

    • User Not Found – Account Does Not Exist or Is Inactive

      Error: User was not found This error usually appears when the partner relationship between your tenant and the customer has been removed — or the GDAP relationship has expired or wasn’t set up properly. Cause: Without a valid and active GDAP ...

    • AADSTS700003 – Device Object Not Found in Tenant

      Error: AADSTS700003 – Device object was not found in the tenant This error occurs when the device originally used for delegated admin access has been deleted from your directory. Cause: If the Azure AD device associated with your delegated admin ...

    • AADSTS50177 – User Not Found in Target Tenant

      Error: AADSTS50177 – User does not exist in tenant and cannot access the application This error means the user referenced in the delegated access attempt isn't recognized in the customer tenant. It typically results from a broken or missing GDAP ...