{"id":179,"date":"2025-02-26T13:24:52","date_gmt":"2025-02-26T21:24:52","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/?p=179"},"modified":"2025-02-26T13:27:31","modified_gmt":"2025-02-26T21:27:31","slug":"using-powershell7-with-managed-runcommand","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/using-powershell7-with-managed-runcommand\/","title":{"rendered":"Using Powershell7 with Managed Runcommand"},"content":{"rendered":"

Today, all scripts run through Managed RunCommand will by default use Powershell 5. What if you have a script that requires Powershell7? This is supported via a new feature, but you will need to specify the different script shell.<\/p>\n

Here’s what you need to do.<\/p>\n

Ensure your VM has Powershell7<\/strong><\/p>\n

Powershell7 is not installed by default. To ensure it’s available on your machine, you have the following options.<\/p>\n

    \n
  1. Create a VM image with Powershell7 pre-installed and use that to create your VMs. For more information on creating images, see here<\/a>. For information on sharing images, see here<\/a>.<\/li>\n
  2. Use RunCommand to install Powershell7 on your VM.<\/li>\n<\/ol>\n

    Here’s an example on how to do this:<\/p>\n

    az vm run-command create --name \"blah\" --vm-name $vmname--resource-group $rg --script \"Invoke-WebRequest -Uri https:\/\/github.com\/PowerShell\/PowerShell\/releases\/download\/v7.4.6\/PowerShell-7.4.6-win-x64.msi -OutFile PowerShell-7.msi; Start-Process msiexec.exe -ArgumentList '\/i PowerShell-7.msi \/quiet \/norestart' -Wait;Remove-Item -Path PowerShell-7.msi\" --location $location<\/code><\/p>\n

    By the time you read this, you’ll likely need to update the download of Powershell7, which can be found here<\/a>.<\/p>\n

    To verify that everything installed, check the instance view. Note that you may need to open an outbound networking rule for this to work.<\/p>\n

    az vm run-command show --name \"blah\" --vm-name $vmname --resource-group $rg --expand instanceView<\/code><\/p>\n

    3. Download the package yourself and create a VmApplication from it. More detail on VM Applications can be found here<\/a>.<\/p>\n

    This option is more complicated, but is useful in situations where your VM is locked down and you don’t wish to open the outbound connection. Since VM Applications are downloaded via the host as a proxy, there’s no need to open any ports.<\/p>\n

    Run your script using Powershell7<\/strong><\/p>\n

    As of this writing, this feature isn’t yet supported in the Portal (which only supports Action RunCommand and not Managed RunCommand), or via CLI and Powershell, where the necessary parameter isn’t supported. You’re therefore going to need to use an ARM template. Here is an example.<\/p>\n

    {<\/code>\n\u00a0 \u00a0\"$schema\": \"https:\/\/schema.management.azure.com\/schemas\/2019-04-01\/deploymentTemplate.json#\",<\/code>\n\u00a0 \u00a0\"contentVersion\": \"1.0.0.0\",<\/code>\n\u00a0 \u00a0\"resources\": [<\/code>\n\u00a0 \u00a0{<\/code>\n\u00a0 \u00a0 \u00a0 \"type\": \"Microsoft.Compute\/virtualMachines\/runCommands\",<\/code>\n\u00a0 \u00a0 \u00a0 \"apiVersion\": \"2024-07-01<\/strong>\",<\/code>\n\u00a0 \u00a0 \u00a0 \"name\": \"[concat(parameters('vmName'), '\/RunPowershellSeven')]\",<\/code>\n\u00a0 \u00a0 \u00a0 \"location\": \"[parameters('region')]\",<\/code>\n\u00a0 \u00a0 \u00a0 \"dependsOn\": [],<\/code>\n\u00a0 \u00a0 \u00a0 \"properties\": {<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"asyncExecution\": false,<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"source\": {<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"script\": \"Write-Output $PSVersionTable\",<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \"scriptShell\": \"Powershell7\"<\/strong><\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0},<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"parameters\": []<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0}<\/code>\n\u00a0 \u00a0}<\/code>\n\u00a0 \u00a0],<\/code>\n\u00a0 \u00a0\"parameters\": {<\/code>\n\u00a0 \u00a0 \u00a0 \"vmName\": {<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"type\": \"string\",<\/code>\n\u00a0 \u00a0 \u00a0 },<\/code>\n\u00a0 \u00a0 \u00a0 \"region\": {<\/code>\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"type\": \"string\"<\/code>\n\u00a0 \u00a0 \u00a0 }<\/code>\n\u00a0 \u00a0}<\/code>\n}<\/code><\/p>\n

    Note the ScriptShell property that indicates the command should be run on Powershell7. Also note that the apiVersion must be at least 2024-07-01 for this to work.<\/p>\n

    To run this command on a VM, you then may run:<\/p>\n

    New-AzResourceGroupDeployment -ResourceGroupName $rg -TemplateFile $templateFilePath -vmName $vmname -region $region<\/code><\/p>\n

    And again to validate that the command ran:<\/p>\n

    az vm run-command show --name \"RunPowershellSeven\" --vm-name $vmname --resource-group $rg --expand instanceView<\/code><\/p>\n

    Of course your script doesn’t (and shouldn’t typically be) in line. All of the standard Managed RunCommand properties that download a script are valid.<\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    Today, all scripts run through Managed RunCommand will by default use Powershell 5. What if you have a script that requires Powershell7? This is supported via a new feature, but you will need to specify the different script shell. Here’s what you need to do. Ensure your VM has Powershell7 Powershell7 is not installed by […]<\/p>\n","protected":false},"author":103696,"featured_media":184,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,6],"tags":[17,9],"class_list":["post-179","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-vm-runtime","category-runcommand","tag-powershell7","tag-runcommand"],"acf":[],"blog_post_summary":"

    Today, all scripts run through Managed RunCommand will by default use Powershell 5. What if you have a script that requires Powershell7? This is supported via a new feature, but you will need to specify the different script shell. Here’s what you need to do. Ensure your VM has Powershell7 Powershell7 is not installed by […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/posts\/179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/users\/103696"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/comments?post=179"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/posts\/179\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/media\/184"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/media?parent=179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/categories?post=179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-vm-runtime\/wp-json\/wp\/v2\/tags?post=179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}