Lately I’ve been having a blast replacing WMI calls with commands from the AAD Connect ADSync PowerShell module. I hit an issue using the ADSync module with PowerShell remoting. To illustrate:

Invoke-Command -ComputerName Sinking -ScriptBlock {Get-ADSyncRunProfileResult}
There was no endpoint listening at net.pipe://localhost/ADSyncManagement that could accept the message. This is often caused by an incorrect address or SOAP 
action. See InnerException, if present, for more details.

It seems some of the commands initiate a connection to an endpoint, which I suspect creates an authentication double-hop issue.

If you are interested in helping prioritize this issue, please vote for the feedback item: ADSync Cmdlets Fail with Remote PowerShell

The ADSync module has some great commands, help make them better with your votes :-)