Microsoft has released security updates for vulnerabilities found in:
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
These updates are available for the following specific...
Updated May 05, 2021
Version 8.0
Blog Post
Nino_Bilic
Microsoft
MicrosoftWe totally understand the frustration. Unfortunately, this was a security related change and therefore we were not able to go through the normal notification period of a "feature" change.
As long as the code in question uses .invoke() to run the command on the server and not on the client then yes .AddScript() will no longer work. The fact .AddScript() was working with .Invoke() at all was actually a problem that was corrected by the April update.
If script still needs to be run import the session instead of invoking the runspace and the scripts will run without issues.
Review the following sample: David-Barrett-MS/ExchangePowerShellAutomationSample: A sample application demonstrating how to connect to Exchange Remote PowerShell and run cmdlets programmatically. (github.com)
Please contact Microsoft Exchange Developer Support and they will be more than happy to directly assist in converting from a direct invoke() to a session import and invoke.