The term 'Get-AzContext' is not recognized as a name of a cmdlet

[nbhargava2022]

Hi,
We are seeing the following error when executing our scripts in version '7.1.5'

====================
The command Get-AzContext is part of Azure PowerShell module "Az.Accounts" and it is not installed. Run "Install-Module Az.Accounts" to install it.
The intelligent recommendation feature is in preview. Help us improve it by sharing your experience: https://go.microsoft.com/fwlink/?linkid=2202436
Unhandled error occurred while deploying VM.
The term 'Get-AzContext' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

The same script was working last week. and we do see that the script loads the Az.Accounts module

Loaded Module 'Az.Accounts'

Can someone suggest why are we seeing this error and how it can be fixed.

Thanks
Nidhi

[dingmeng-xue]

This error should happen when Az.Accounts cannot be imported. Please execute Get-Module in the same console when you see that error. If you cannot see Az.Accounts in result, share the whole result of Get-Module to us.

This page https://learn.microsoft.com/en-us/powershell/azure/troubleshooting?view=azps-9.2.0#command-found-but-could-not-be-loaded can give you hints as well.

[nbhargava2022]

Hi @dingmeng-xue ,
I am not able to access the console to run the Get-Module command as this is part of the our build pipeline tests and get executed on a remote machine.
I did add "Import-Module Az.Accounts" to the script. But still see the failure occasionally. It doesn't happen all the time.

I tried adding Get-Module, but now I am unable to reproduce the error.

Could it be a timing issue where the loading of module takes time.
If yes, can you suggest if we should wait before invoking any commands to connect to the account after loading the module.

This issue started happening recently. So not sure what changed in the environment.