The Exchange Online PowerShell v3 module (the v3 module) is now Generally Available. The v3 module has all REST-based cmdlets and it enables the use of Exchange Online cmdlets via REST API calls. It ...
Updated Sep 20, 2022
Version 3.0
Blog Post
Not specific to PowerShell vs Windows PowerShell, but I saw a warning yesterday in the output from one of the REST-backed Set-**** cmdlets which stated that in traditional remote PowerShell sessions, a confirmation prompt would have been presented, but will no longer be presented with the REST-backed cmdlets. This seems like a major no-no to me. PowerShell's basic principles need to be maintained, whether it's REST-backed or not. So -WhatIf and -Confirm really ought to be carefully maintained in my opinion. They're part of the greatness of PowerShell and avoiding them this late in the game is just bad bad bad. I would have an easier time accepting it if it wasn't Microsoft producing the module/cmdlets.
WhatIf has already been tossed to the wayside for many cmdlets over the years, especially SCC ones where they would arguably be even more important. Now confirmation is also going to be tossed to the side? Please reconsider this.