You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The script AKSEdgeRemoteDeployment.ps1 used in Quickstart successfully deployed AKS-Edge-Essentials but failed to connect to Azure Arc with the following error message:
az : The term 'az' 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.
At C:\AksEdgeScript\AKS-Edge-1.0.266.0\tools\modules\AksEdgeDeploy\AksEdge-Arc.ps1:175 char:24
+ $ret = az login --service-principal -u $aiauth.Servic ...
+ ~~
+ CategoryInfo : ObjectNotFound: (az:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Error: ServicePrincipalId/Password possibly expired.
C:\AksEE\AksEdgeRemoteDeploy.ps1 : Azure login failed.
At line:1 char:1
+ .\AksEdgeRemoteDeploy.ps1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,AksEdgeRemoteDeploy.ps1
Based on the error message, seems like it's using az command to connect to Azure, but it is not mentioned anywhere in the document that Azure-CLI is required.
Describe the bug
The script AKSEdgeRemoteDeployment.ps1 used in Quickstart successfully deployed AKS-Edge-Essentials but failed to connect to Azure Arc with the following error message:
Based on the error message, seems like it's using
az
command to connect to Azure, but it is not mentioned anywhere in the document that Azure-CLI is required.To Reproduce
Steps to reproduce the behavior:
.\AksEdgeRemoteDeploy.ps1
Expected behavior
The script should connect to Azure Arc if all Azure configs are provided.
Screenshots
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: