Has there been any issues raised around the use of the ExchangeOnlineManagement 3.0.0 and 3.1.0 modules in an Azure Automation runbook?
I noticed from Thursday 9 Feb that the module no longer authenticates under a Managed Identity or Credential flow context on either a PowerShell 5.1 or 7.1 runbook. I have regressed back to 2.0.6-preview-7 to get it working again in the runbook.
When using 3.0.0 or 3.1.0 modules in a 7.1 runbook, I get the error:
OperationStopped: C:\ModulesV2\User\ExchangeOnlineManagement\netCore\ExchangeOnlineManagement.psm1:729
Line |
729 | throw $_.Exception.InnerException;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0,
| Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'.
OperationStopped: C:\ModulesV2\User\ExchangeOnlineManagement\netCore\ExchangeOnlineManagement.psm1:729
Line |
729 | throw $_.Exception.InnerException;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0,
| Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'.
Similarly, in a 5.1 runbook, I get the error:
Failed
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.
I've been able to replicate the error across three different tenants and three subscriptions.
Any ideas?