Announcing Deprecation of Remote PowerShell (RPS) Protocol in Exchange Online PowerShell

Hi cking22001 . The info you need is in the Microsoft docs, you just need to read through all of the sections. I think the release notes are useful for this but agreed it’snot clearly called-out. The code breaking changes are pretty minor and we only had to make small modifications to our scripts. Here’s the main areas:

1. Use the https://learn.microsoft.com/en-us/powershell/module/exchange/get-connectioninformation cmdlet to get information about REST-based connections to Exchange Online PowerShell. This cmdlet is required because the https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/get-pssession cmdlet in Windows PowerShell doesn't return information for REST-based connections. Some of our scripts checked for a connection to Exchange using Get-PSSession before running. So we had to change to Get-ConnectionInformation because Get-PSSession returns nothing after you upgrade to V3. This was the main area we had to review and update.

2. Certain cmdlets that used to prompt for confirmation in specific scenarios no longer do so. By default, the cmdlet will run to completion.

3. The format of the error returned from failed cmdlet execution has been slightly modified. The exception now contains additional data (for example, the exception type), and the FullyQualifiedErrorId does not contain the FailureCategory. 

Hope this info helps…