[ad_1]
We previously announced the Deprecation of Remote PowerShell Protocol (RPS) in Exchange Online, and we’ve now reached the end of RPS. Since making the announcement, usage of RPS in our WW cloud has dropped dramatically.
We have disabled the self-service diagnostic to re-enable or opt-out of this change, and we will now be turning off RPS. In fact, we will turn off RPS for our WW cloud customers by tomorrow.
Usage of RPS in our sovereign (not WW) clouds has also seen dramatic drop, and we will be turning off RPS for sovereign cloud customers this month.
For all customers, when we disable RPS for your tenant, you will get a Service Health Notification in the Microsoft 365 admin center that we have done so.
Using Exchange Online PowerShell going forward
Once RPS is disabled for your tenant (or if RPS was already disabled) you will need to meet the following prerequisites to use Exchange Online PowerShell:
Thank you!
Finally, we want to thank you for all the work you have done to migrate from the RPS protocol in Exchange Online PowerShell to REST, which provides a more secure and robust way to use Exchange Online PowerShell.
Exchange Online Manageability Team
[ad_2]
Source link
