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
Hi,
We are having somewhat similar issue with EXOv3. We have a .net core app running in a Linux (Ubuntu focal) container. The app is using PowerShell SDK (Microsoft.PowerShell.SDK and System.Management.Automation) to make calls to Exchange using EXO. The app functions with no issues with EXOv2 (2.0.5). When we try to use EXOv3, we get the dreaded “Update-ModuleManifest” error when running Connect-ExchangeOnline.
The term 'Update-ModuleManifest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.If we use -UseRPSSession option with EXOv3, it starts working again. Since RPS is going to be depreciated this doesn't seem like a viable long-term solution.