**Update. Wow what timing. I now see MC post MC541649! Fantastic stuff. Can't wait to see v3.2.0 come along with RESTful Connect-IPPSSession!
Wondering, how does this stuff apply to Connect-IPPSSession? In even the latest of the latest ExchangeOnlineManagement, it still exclusively uses RPS. I've been noticing the last few weeks, Connect-IPPSSession is just about 55-60% reliable, at best. The other 40-45% of the time (at least) it fails right after downloading all the commands and all the format info with error:
Processing data for a remote command failed with the following error message: The request for the Windows Remote Shell with ShellId B344C6FE-ADCF-4EB7-996F-BE430F9DDC0A failed because the
shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and
retry the operation. For more information, see the about_Remote_Troubleshooting Help topic.
If I try with Connect-ExchangeOnline using -ConnectionUri https://can01b.ps.compliance.protection.outlook.com/PowerShell-LiveId, I get this error:
Your attempt to connect to this Exchange server was denied because your account isn't enabled for Remote PowerShell. Your Exchange administrator can use the Set-User
-RemotePowerShellEnabled command to enable your account.
Meanwhile, I got check my account because I think this is not true:
PS C:\Users\MyUser> Get-user email address removed for privacy reasons | fl Rem*
RemotePowerShellEnabled : True
I do see in the March post that the RPS deprecation is not affecting Connect-IPPSSession. So maybe these issues are totally unrelated. But then I ask, why is Connect-IPPSSession not getting any love?.... again? (remember CBA only came to Connect-IPPSSession well after it came to Connect-ExchangeOnline. If RPS is so bad, then how is the Compliance Center so OK, but Exchange Online itself is so NOT OK? Can we get something non-RPS working for Compliance stuff? MS Graph maybe?
I also wonder about that false error message telling me that RPS is disabled on my account. It's not disabled in our tenant as far as I know, since Connect-IPPSSession is working sometimes here. Is this maybe an artifact of the way of the future when tenants created after April 1 2023 are targeted for RPS disablement?