Deprecation of Remote PowerShell (RPS) Protocol in Security and Compliance PowerShell
Published May 08 2023 10:06 AM 32.5K Views

Update: There are no more cmdlets left that do not support REST protocol.

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 (or newer) 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 (or newer) 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.

In short, all customers should install the Exchange Online v3 module version 3.2.0 (or newer) and use Connect-IPPSSession to establish a connection to the service.

If you have questions or concerns, please email us at

Security and Compliance PowerShell Team

Version history
Last update:
‎Jul 25 2023 01:54 PM
Updated by: