This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 20%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESJ%3C/text%3E%3C/svg%3E)
Since the morning of Thursday 9 Feb 2023, I've not been able to successfully authenticate with ExchangeOnlineManagement via an Azure Automation runbook using either a credential flow or Managed Identity. I can replicate this issue across three different tenants on three different subscriptions. It was working fine up until Thursday, now I get the following error:
PowerShell v5.1 / ExchangeOnlineManagement v3.1.0 using Managed Identity
PowerShell v7.1 / ExchangeOnlineManagement v3.1.0 using Managed Identity
PowerShell v7.1 / ExchangeOnlineManagement v3.1.0 using Credential flow
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 39%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
I have the same problem my runbook started failing on Thursday 9th with exactly the same error. So far google has led me here, checked service health in our tenant and no issues reported... yet.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 41%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
@Steve Johnson I am sorry for the inconvenience. We have seen similar incidents reported and it is under investigation.
A workaround would be to use version 2.0.5 of ExchangeOnlineManagement module. This seems to be working.
Another workaround would be to use Hybrid Workers to execute the runbook jobs for the runbooks using this module.
I will keep an eye on our investigation and update this thread as soon as I have an update.
Thanks @AnuragSingh-MSFT - I've regressed back to using the 2.0.6-preview-7 version and that works. Also, whilst it's being deprecated from June 2023, adding the -UseRPSSession parameter forces the 3.1.0/3.0.0 to work as well as a temporary workaround too.
@Steve Johnson thank you very much for sharing the workaround with the community. I am keeping an eye on the internal investigation about the issue with v3.1.0 and will update here.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 65%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERD%3C/text%3E%3C/svg%3E)
Hi @AnuragSingh-MSFT ,We are also having the same issue. May I know has this issue has been resolved? If I switch to 2.0.5 then I can't authenticate using the System Managed identity. It gives the below error.
Connect-ExchangeOnline : A parameter cannot be found that matches parameter name 'ManagedIdentity'. At line:6 char:24 + Connect-ExchangeOnline -ManagedIdentity -Organization 'willowinc.onmi ... + ~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Connect-ExchangeOnline], ParameterBindingException + FullyQualifiedErrorId : NamedParameterNotFound,Connect-ExchangeOnlin
@Steve Johnson , Rajesh1257 - Can you please share the region (e.g., WestUs, CanadaCentral) where your Automation Account instance is deployed which is facing this issue?
I will share an update as soon as I have any. Thank you.
For me, its UK South.
@AnuragSingh-MSFT ,Mine is in Australia East
@Steve Johnson , Rajesh1257, Martyn Burgess - following up to check if you had a chance to review the solution provided above.
@AnuragSingh-MSFT I can confirm this did work for the 5.1 EXO 3.1.0 module, thanks. However, 7.1 is still not working.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 43%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
I have just tested this fix and it now works. Thank God! Painful...
thank you for the confirmation.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 30%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMJ%3C/text%3E%3C/svg%3E)
I'm experiencing the same issues as @Alexandros Kanakaris posted above here. That was almost a year ago.
@AnuragSingh-MSFT Is anything being done to fix this?