Update 5/19/2023: Clarified the timeline and scope of changes.
Starting July 15, 2023, we will start deprecating the legacy RPS protocol in the Security and Compliance PowerShell module. RPS is enabled by default for Security and Compliance cmdlets.
The timeline of disablements in this blog post applies only to tenants in our World-Wide (WW) cloud. Final RPS disablement for customers in other Microsoft cloud environments as well as WW cloud is scheduled for October 2023.
As part of our modernization efforts, the Security and Compliance admin experience is moving to REST-based cmdlets.
The new REST API will have the same cmdlets available and will have feature parity with the RPS v1 cmdlets; thus, existing scripts and processes don’t need to be updated. Simply using the new PowerShell module version 3.2.0-Preview3 will ensure REST is used instead of RPS.
You can switch to REST-based cmdlets now by doing the following:
- Install the Exchange Online Management v3 module version 3.2.0-Preview3 from here.
- Use Connect-IPPSSession -UseRPSSession:$false to establish the connection.
Once this version of the module is generally released (and is out of preview) using
-UseRPSSession:$false parameter will not be required.
We highly recommend that customers switch to the new module as soon as possible.
A subset of eDiscovery cmdlets (18 of them - list updated on 5/15/2023) are not yet supported using the REST API. ETA for support of those cmdlets is June 1, 2023. Until then, admins need to continue to use RPS with Connect-IPPSSession for those specific cmdlets. Please see the file attached to this blog post for the list of those cmdlets.
In short, all customers should install the Exchange Online v3 module version 3.2.0-Preview3 and use Connect-IPPSSession to establish a connection to the service.
If you have questions or concerns, please email us at EOPSCCcmdletinfo@microsoft.com.
Security and Compliance PowerShell Team