I'm facing a strange issue with the Exchange Online PowerShell module that started suddenly yesterday. When I try using the `set-mailbox` command, I get an error, but everything else, like `get-mailbox`, works without a hitch. The error message reads: Exception of type 'Microsoft.Exchange.Configuration.Tasks.CmdletNeedsProxyException' was thrown. I've tried several solutions like using different machines and even disabling our proxy agent, but nothing has worked. It's odd that this issue is isolated to the `set-mailbox` command. I couldn't find any relevant information online about this error. Is anyone else encountering this problem? Just to add, I've also removed the proxy agent, reinstalled the Exchange Online PowerShell module, and tested from a corporate laptop at home, yet nothing seems to resolve the issue. I even checked with a separate development O365 tenant and have the same problem there, so it doesn't seem to be tenant-specific.
1 Answer
I’ve encountered a similar issue with the `set-mailbox` command in Exchange Online PowerShell. Here are a few things you might want to consider:
1. Ensure you’re using the latest version of the Exchange Online PowerShell module; sometimes older versions can break due to changes in Microsoft’s backend.
2. Try reconnecting with a new session using `Connect-ExchangeOnline`, and check the module version using `Get-Module ExchangeOnlineManagement`.
3. If you are behind a proxy, consider running the command from a machine that is not behind it to rule out proxy-related issues.
These CmdletNeedsProxyException errors often arise when there's a mismatch between your local module version and Microsoft's backend configurations.
Thanks for the suggestions! I've already ruled out the proxy as I disabled the corporate proxy agent and tested from a different machine with module version 3.4, while my original was 3.9. I'm really curious about any backend changes that might be causing this. I might try re-installing the module to see if that does anything.