Azure Synchronization Service - Connector Verbose Logging

@paul_manyNumbers Thank you for reaching out to us, As I understand you are looking for details on how to enable verbose logging for LDAP synchronization to Entra ID.

Refer to the steps mentioned here to capture the ldap trace (etl) - https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/troubleshoot/troubleshoot-ldap-using-etw https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/turn-on-debug-logging-ldap-client

For verbose information use this flag - 0x1bddbf73

Process name use it as : miiserver.exe & powershell.exe

Below is the sample script which you can use.

echo off
echo "set reg keys for tracing"
reg ADD HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ldap\Tracing\miiserver.exe /f
reg ADD HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ldap\Tracing\powershell.exe /f
logman create trace "ds_aadc" -ow -o c:\temp\ldapClientAADConnect.etl -p "Microsoft-Windows-LDAP-Client" 0x1bddbf73 0xff -nb 16 16 -bs 1024 -mode Circular -f bincirc -max 4096 -ets

echo "press a key to stop tracing"
pause
logman stop "ds_aadc" -ets

netsh trace convert input=c:\temp\ldapClientAADConnect.etl output=c:\temp\ldapClientAADConnect-formatted.txt

echo "deleting reg keys" reg delete HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ldap\Tracing\miiserver.exe /f
reg delete HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ldap\Tracing\powershell.exe /f

echo "finished."

Sharing the screenshot for reference of the script. Let me know if you have any further questions, feel free to post back.

Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.