Update 5/8/2023: We have added new information about the deprecation of RPS in the Security and Compliance PowerShell module in the post below. For more information on RPS deprecation for Exchange On...
Updated May 08, 2023
Version 9.0
Blog Post
3 MIN READ
Announcing Deprecation of Remote PowerShell (RPS) Protocol in Exchange Online PowerShell
@AdityaMukund and The_Exchange_Team Replying to your March 2nd remark:
You are wrong, 100 times over. This is after connecting to EXO using only "Connect-ExchangeOnline" with zero (0) parameters.
If I was using the UseRPSSession parameter (via older module) there would be a different banner.
----------------------------------------------------------------------------------------
You are now connected to an RPS session. We would love to know why you still prefer to use RPS cmdlets and how we can improve your experience with REST cmdlets, which are more secure, reliable than the RPS cmdlets and are now generally available.
Please share your feedback/suggestions with us at - email address removed for privacy reasons
Also, you can continue to access the earlier released 9 REST cmdlets such as Get-EXOCasMailbox, Get-EXOMailbox etc. on this module.
For more information on the RPS vs REST cmdlets please visit - https://aka.ms/ExchangeOnlineVersions
----------------------------------------------------------------------------------------
Please accept the fact that this is an issue with the module (or something directly related). In fact, UseRPSSession does not appear to be an available parameter with v3.1.0 and not sure how you can assume we are using the UseRPSSession parameter.
PS C:\> Connect-ExchangeOnline -userpssession
Connect-ExchangeOnline : A parameter cannot be found that matches parameter name 'userpssession'.
At line:1 char:24
+ Connect-ExchangeOnline -userpssession
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Connect-ExchangeOnline], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Connect-ExchangeOnline
I've been working with support on other cases and brought this issue up to them -- which they thought was odd. This occurs from several servers that had a previous version of the module installed, and from a desktop that never had a previous version of the module installed.