Thanks Matthew, appreciate the tips above. But Microsoft should really up their game when it comes to remote PowerShell, especially considering the push we face to move everything to the cloud. Both in speed and reliability. Or give us proper reporting
so we can at least eliminate the need of collecting basic data via PowerShell and use it only for Set- cmdlets against a pre-populated CSV or similar.
The "no language" mode is way too restrictive to make anything other than generic 'get all data' cmdlets work with Invoke-Command, so the very least you can do is offer us a proper support for server-side filtering across all cmdlets. Even the error handling
is pain with the remote session, though Invoke-Command still saves the day in most cases.
Support for ADAL/MFA for 'plain' PowerShell, with some automation elements added as well, is also a must.