Azure Automation Accounts Az.Accounts PowerShell module broken?
Philipp Durrer
10
Reputation points
Since May 31st 2024 mid day UTC I see all our PowerShell 7.1 Runtime jobs failing due to the following error:
Failed
[91mWrite-Error: [0mC:\usr\src\tmp\accaf8e0-f99e-4d6b-8a7f-47b42ff95a77\runbooks\StartStop-AKS.ps1:223
[96mLine |
[96m 223 | [0m [96mStopStartAksCluster[0m
[96m | [91m ~~~~~~~~~~~~~~~~~~~
[91m[96m | [91mSystem.IO.FileLoadException: Could not load file or assembly
[96m | [91m'Microsoft.ApplicationInsights, Version=2.18.0.315,
[96m | [91mCulture=neutral, PublicKeyToken=31bf3856ad364e35'. at
[96m | [91mSystem.Management.Automation.Runspaces.InitialSessionState.Bind_LoadAssemblies(ExecutionContext context) at System.Management.Automation.Runspaces.InitialSessionState.Bind(ExecutionContext context, Boolean updateOnly, PSModuleInfo module, Boolean noClobber, Boolean local, Boolean setLocation) at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String moduleManifestPath, ExternalScriptInfo manifestScriptInfo, Hashtable data, Hashtable localizedData, ManifestProcessingFlags manifestProcessingFlags, Version minimumVersion, Version maximumVersion, Version requiredVersion, Nullable`1 requiredModuleGuid, ImportModuleOptions& options, Boolean& containedErrors)
[0m
[91mWrite-Error: [0mC:\usr\src\tmp\accaf8e0-f99e-4d6b-8a7f-47b42ff95a77\runbooks\StartStop-AKS.ps1:223
[96mLine |
[96m 223 | [0m [96mStopStartAksCluster[0m
[96m | [91m ~~~~~~~~~~~~~~~~~~~
[91m[96m | [91mSystem.IO.FileLoadException: Could not load file or assembly
[96m | [91m'Microsoft.ApplicationInsights, Version=2.18.0.315,
[96m | [91mCulture=neutral, PublicKeyToken=31bf3856ad364e35'. at
[96m | [91mSystem.Management.Automation.Runspaces.InitialSessionState.Bind_LoadAssemblies(ExecutionContext context) at System.Management.Automation.Runspaces.InitialSessionState.Bind(ExecutionContext context, Boolean updateOnly, PSModuleInfo module, Boolean noClobber, Boolean local, Boolean setLocation) at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String moduleManifestPath, ExternalScriptInfo manifestScriptInfo, Hashtable data, Hashtable localizedData, ManifestProcessingFlags manifestProcessingFlags, Version minimumVersion, Version maximumVersion, Version requiredVersion, Nullable`1 requiredModuleGuid, ImportModuleOptions& options, Boolean& containedErrors)
[0m
[91mOperationStopped: [0mC:\usr\src\tmp\accaf8e0-f99e-4d6b-8a7f-47b42ff95a77\runbooks\StartStop-AKS.ps1:149
[96mLine |
[96m 149 | [0m [96mthrow $_.Exception[0m
[96m | [91m ~~~~~~~~~~~~~~~~~~
[91m[96m | [91mCould not load file or assembly
[96m | [91m'Microsoft.ApplicationInsights, Version=2.18.0.315,
[96m | [91mCulture=neutral, PublicKeyToken=31bf3856ad364e35'.
[0m
My script is basically trying to do the following:
#Inizialiting connection to the AutomationAccount
try
{
Import-Module Az.Accounts
"Logging in to Azure using Managed Identity..."
Connect-AzAccount -Identity
}
It looks like it doesn't matter the PowerShell version nor if I use a custom Runtime Environment or not everything fails. It's as if the Automation Account execution environment changed architecture and still tries to import the x64 modules.