As suggested, I would work with support on this item. Essentially you will need to enable debug logging for the Azure AD sync (or InTune or MS365), after which more detailed information will appear in the errorlog (typically %ProgramFiles(x86)%\Lansweeper\Service\errorlog.txt). Support will be able to provide you with a DebugOptions.xml file that will provide the correct parameters for debugging.
Here's an excerpt showing the beginning of an AzureAD scan (identifying information has been obfuscated). This is from a v10 install, before Lansweeper started using the EntraID naming:
2024-01-04 12:42:19,102 [36] INFO LOGAZUREADSCANNING DEBUG Checking for valid credentials, trying xxxxxx
2024-01-04 12:42:19,117 [36] INFO LOGAZUREADSCANNING DEBUG Creating HTTP client.
2024-01-04 12:42:19,149 [36] INFO LOGAZUREADSCANNING DEBUG Getting new Access Token.
2024-01-04 12:42:20,478 [36] INFO LOGAZUREADSCANNING DEBUG Valid credential found, proceeding with xxxxxx
2024-01-04 12:42:20,478 [36] INFO LOGAZUREADSCANNING DEBUG Creating HTTP client.
2024-01-04 12:42:20,492 [36] INFO LOGAZUREADSCANNING DEBUG Retrieving Graph Users.
2024-01-04 12:42:20,492 [36] INFO LOGAZUREADSCANNING DEBUG Getting new Access Token.
2024-01-04 12:43:20,426 [43] INFO LOGAZUREADSCANNING DEBUG 9999 users found
...
2024-01-04 13:45:02,764 [45] INFO LOGAZUREADSCANNING DEBUG Start of AzureAD scanning.
2024-01-04 13:45:02,764 [45] INFO LOGAZUREADSCANNING DEBUG Start processing AzureAD scanning
2024-01-04 13:45:02,764 [45] INFO LOGAZUREADSCANNING DEBUG Start scanning of 1 tenants
2024-01-04 13:45:02,781 [45] INFO LOGAZUREADSCANNING DEBUG Start scanning tenant with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
2024-01-04 13:45:02,781 [45] INFO LOGAZUREADSCANNING DEBUG Checking for valid credentials, trying xxxxxx
2024-01-04 13:45:02,781 [45] INFO LOGAZUREADSCANNING DEBUG Creating HTTP client.
2024-01-04 13:45:02,781 [45] INFO LOGAZUREADSCANNING DEBUG Getting new Access Token.
2024-01-04 13:45:03,436 [45] INFO LOGAZUREADSCANNING DEBUG Valid credential found, proceeding with xxxxxx
2024-01-04 13:45:03,452 [45] INFO LOGAZUREADSCANNING DEBUG Creating HTTP client.
2024-01-04 13:45:03,452 [45] INFO LOGAZUREADSCANNING DEBUG Retrieving Graph Groups.
2024-01-04 13:45:03,452 [45] INFO LOGAZUREADSCANNING DEBUG Getting new Access Token.
2024-01-04 13:45:10,749 [76] INFO LOGAZUREADSCANNING DEBUG 9999 Groups found
2024-01-04 13:45:10,749 [76] INFO LOGAZUREADSCANNING DEBUG Retrieving Graph Users.
2024-01-04 13:45:39,296 [25] INFO DEBUG Free memory detected: 4969MB
2024-01-04 13:46:19,327 [30] INFO LOGAZUREADSCANNING DEBUG 9999 users found
2024-01-04 13:46:19,327 [30] INFO LOGAZUREADSCANNING DEBUG Retrieving Organization.
2024-01-04 13:46:19,436 [48] INFO LOGAZUREADSCANNING DEBUG Retrieved 1 organization.
2024-01-04 13:46:19,468 [48] INFO LOGAZUREADSCANNING DEBUG Retrieving Group Members.
2024-01-04 13:46:19,499 [141] INFO LOGAZUREADSCANNING DEBUG Retrieving User Group Members.
...
It can take a while; I've seen it take up to four hours to complete an Azure AD sync for us, although typically it completes within an hour or two. It also seems to be a somewhat resource intensive process on the collector side.