MicrosoftI don't know if anyone still watches these comments, and I've emailed the feedback address about this as well. I've noticed that the new cmdlets:
The 2nd point is pretty obvious, EXO servers wouldn't use the REST service to query themselves. However I mention it because Invoke-Command is by far superior until these commands start to offer the nest properties in their outputs. If returning nested properties won't be allowed, then the value returned for the flattened object properties where the value needs to be unique, should be unique values.
A perfect example is the GrantSendOnBehalfTo property. Exchange Online will return the display names of users in that property, which is not a guaranteed-unique property, and is therefore useless in factual reporting. This is a no-brainer to me, and I'm not sure why or how it was missed.
I originally found it difficult when I realized PowerShell remoting was such a downgrade compared to using the Exchange Management Shell (in this specific regard), but then I got used to Invoke-Command. I now fear the new cmdlets are going to be another downgrade for admins. My favorite thing to work on is Exchange, but it is getting harder and harder to not get caught up on these kinds of misses which seem like design choices or something. I understand there is internet connectivity and server performance to deal with here, but stripping the product of valuable functionality seems like the wrong direction to be taking it.
