Hi Guys,
Is it possible to run a AZ Cli command within my powershell runbook in Azure?
From Azure cloud shell i am able to execute the CLI commands to perform some tasks on my remote machine within azure network. I want to incorporate the same commands within my Powershell runbook.
az --vm run-command invoke --command-id RunShellScript --resource-group 'AUTOMATION_TESTRG' --name 'testing-vm-stripe' --scripts '/tmp/one.sh'
Regards,
Janakiraman
AFAIK, currently it is not a supported feature. I see these related feature requests already raised and one of them is triaged by responsible Azure feature team. So I recommend you to upvote it. In general, Azure product or feature team would check feasibility of a feature request, prioritize against existing feature backlog, add in roadmap as appropriate and would announce and/or update the related Azure document once a feature request is addressed.
If it's okay I would recommend you to try PowerShell equivalent of your CLI command. Example:, if the CLI command is az vm run-command invoke then try to go for Az PowerShell cmdlet Invoke-AzVMRunCommand.
I have tried this option, but i noticed the script path of the command checks for the location on the sandbox where its running.
For example if i want to invoke a script on remote server, Invoke-AzVMRuncommand checks that locally and fails with the error file is not found.
Regards,
Jana.
Invoke script (for example test.ps1 that's under c:\ drive) on a remote server with the help of below approach.
$ServicePrincipalConnection = Get-AutomationConnection -Name 'AzureRunAsConnection'
Add-AzAccount -ServicePrincipal -TenantId $ServicePrincipalConnection.TenantId -ApplicationId $ServicePrincipalConnection.ApplicationId -CertificateThumbprint $ServicePrincipalConnection.CertificateThumbprint
$rgname ="rrrrrrrrrrrrrr"
$vmname ="vvvvvvvvvvvvvv"
$ScriptToRun = "c:\test.ps1"
Out-File -InputObject $ScriptToRun -FilePath ScriptToRun.ps1
Invoke-AzVMRunCommand -ResourceGroupName $rgname -Name $vmname -CommandId 'RunPowerShellScript' -ScriptPath ScriptToRun.ps1
Remove-Item -Path ScriptToRun.ps1
Note: Replace value of $rgname and $vmname with your resource group name and VM name as appropriate.
Did you get chance to review the above information? Let me know if you have any further queries regarding it.
Hello tbgangav-MSFT,
I have tried to invoke the remote commands to api calls and it worked for me yesterday, apologize for the delay in response.
Here is the link which i followed.
Thanks again for your support.
https://blog.tekspace.io/access-azure-rest-api-using-powershell/
Regards,
Janakiraman
Yes you can run az cli in PowerShell.
Once az cli is installed, add az cli command path to your computer's environmental variable and then set the alias for az following below steps.
Run below commands as an administrator.
Adding az cli command path to your computer's environmental variable path
$azCliPath = "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin"
$CurrentPath =(Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' -Name PATH).path
$NewPath = “$CurrentPath;$azCliPath”
Set-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' -Name PATH -Value $NewPath
Set alias for az command running using below PowerShell command
Set-Alias -Name az -Value "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd"
After completing the above steps, you should be able to run "az" command in your PowerShell or ISE.
Has anything changed with this regarding Azure CLI in PS 7.0 (preview) in the last couple days? I've been able to run Azure CLI in runbooks for the last 3 weeks or so, using it to export our Azure DNS zones to txt files then using Azure Powershell to copy the txt files to a storage account.
This script ran every day at 5am and looks to have started failing on 11/20 and no longer recognizes the "az login" command when running. Nothing else has changed on this automation account, still using PS 7.0 (preview) runtime.
@DamianEvans-2262 I did not. I ended up just running my script as a scheduled task on a VM I had in enrolled into Azure Arc and authenticated in the script using a managed identity for the VM. Not ideal but works for now.
11 people are following this question.
