493 questions
I had the same issue appear too today with no changes to our release pipelines. I've resolved it by changing the Azure File Copy task version from 2.* to 6.*
Azure DevOps Pipeline Error - Required Minimum Version 0.9.0 of Azure Powershell Cmdlets Not Installed
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 37%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKT%3C/text%3E%3C/svg%3E)
Kareem, Tobi
75
Reputation points
When running our Azure Pipeline, we encountered the following error in the YAML below:
The pipeline attempts to execute AzureBlob Copy App Version 2.252.0 using Azure Powershell, but it fails due to outdated module version.
The last build that run was on 02-14-2025T22:38:10.4169481Z using Version : 2.251.1
How can we ensure the pipeline always uses the latest Azure Powershell Version.
Using Version 2.252.0, we are seeing this error:
##[error]The required minimum version 0.9.0 of the Azure Powershell Cmdlets are not installed. You can follow the instructions at https://azure.microsoft.com/en-in/documentation/articles/powershell-install-configure/ to get the latest Azure powershell
2025-03-08T02:57:41.4331352Z ##[command]Disconnect-AzAccount -Scope Process -ErrorAction Stop
2025-03-08T02:57:41.4741199Z ##[command]Clear-AzContext -Scope Process -ErrorAction Stop
2025-03-08T02:57:41.6125683Z ##[error]The required minimum version 0.9.0 of the Azure Powershell Cmdlets are not installed. You can follow the instructions at https://azure.microsoft.com/en-in/documentation/articles/powershell-install-configure/ to get the latest Azure powershell
2025-03-08T02:57:41.6760435Z ##[section]Finishing: AzureBlob Copy App
##[error]The required minimum version 0.9.0 of the Azure Powershell Cmdlets are not installed. You can follow the instructions at https://azure.microsoft.com/en-in/documentation/articles/powershell-install-configure/ to get the latest Azure powershell
Azure DevOps
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 73%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENK%3C/text%3E%3C/svg%3E)
Nagaraj K 15 Reputation points2025-03-08T16:36:05.72+00:00 Can MSFT support address this ASAP as we're blocked with PROD deployments because of this issue.
-
Arko 4,150 Reputation points Microsoft External Staff Moderator2025-03-10T08:03:34.8266667+00:00 Hi Nagaraj K, could you kindly share your yaml for better clarity?
You can try to incorporate an inline script in your yaml to ensure your desired version of powershell.- task: AzurePowerShell@5 displayName: 'Use Latest Azure PowerShell' inputs: azureSubscription: '<your-service-connection>' ScriptType: 'InlineScript' Inline: | Install-Module -Name Az -Force -AllowClobber -Scope CurrentUser Import-Module Az Get-Module -Name Az -ListAvailable azurePowerShellVersion: 'LatestVersion'Kindly read the note section of this document for better understanding- azurePowerShellVersion:LatestVersion
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 64%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
JZ 5 Reputation points2025-03-10T10:06:38.6533333+00:00 I think there's something wrong with AzureFileCopy@1
I'm trying to replace it with AzureCLI@2, but I cannot figure out how to output the outputStorageUri and the outputStorageContainerSasToken, they're used in the later steps.
-
Craig Mellon 0 Reputation points2025-03-10T14:59:54.57+00:00 I have the same issue this morning, we are using AzureFileCopy@2 - we can't use the later versions as the $web copy is not working.
Any reason why this started happening? I have tried the suggested powershell script above but no luck, still failing with same error :(
-
Craig Mellon 0 Reputation points
2025-03-10T15:03:13.24+00:00 I have the same error/issue with AzureFileCopy@2 also
-
Craig Mellon 0 Reputation points
2025-03-10T15:07:27.7733333+00:00 I have the same issue reported with AzureFileCopy@2 version also so I don't think that will fix it
-
Kareem, Tobi 75 Reputation points
2025-03-10T21:46:00.84+00:00 Hello @arko, any insight as to the question I asked above about the AzureBlob Copy App?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 69%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
KevinStorey 95 Reputation points2025-03-11T00:14:24.78+00:00 I had the same issue appear today - I resolved it by changing the Task version on the Azure file copy task from 2.* to 6.*.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 67%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAE%3C/text%3E%3C/svg%3E)
Aaron Edelman 0 Reputation points2025-03-11T13:30:33.8366667+00:00 Had the same issue this morning. Previously were using Task version 1.* and source path $(Build.ArtifactStagingDirectory)/$(Build.BuildNumber)_app.zip
Set Task version to 3.* and updated Build pipeline Target/Release Source to $(System.DefaultWorkingDirectory)/$(Build.BuildNumber)_app.zip
Sign in to comment
Accepted answer
-
KevinStorey 95 Reputation points
2025-03-11T00:12:21.85+00:00 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 11%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Sajeesh Kumar A 0 Reputation points2025-03-11T06:37:39.7166667+00:00 Yeah, this solved for us too.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 72%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Liam Thompson 5 Reputation points2025-03-13T03:26:40.4266667+00:00 After updating from 2.* to 6.* we got a different error which upon further investigation was an authorization issue.
Upload to container: 'container' in storage account: 'account' with blob prefix: '' failed with error: 'AzCopy.exe exited with non-zero exit code while uploading files to blob storage.' For more info please refer to https://aka.ms/azurefilecopyreadmeAdding the role "Storage Blob Data Contributor" to our User Principal fixed this and afterwards the whole pipeline succeeded.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 1%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
Steve White 0 Reputation points2025-03-17T13:07:11.1666667+00:00 Yes, a simple solution :)
Sign in to comment -
1 additional answer
Sort by: Most helpful
-
Arko 4,150 Reputation points Microsoft External Staff Moderator
2025-03-17T04:01:41.4633333+00:00 It looks like the core issue was with the version of the Azure File Copy task rather than the PowerShell module itself. While ensuring that the latest PowerShell modules are installed is generally a good practice, the actual fix in this case is updating the Azure File Copy task version in your pipeline. Modify your pipeline YAML to use AzureFileCopy@6 instead of the older v2 version
- task: AzureFileCopy@6 inputs: SourcePath: '<your-source-path>' Target: '<your-target>' AzureSubscription: '<your-service-connection>'Instead of manually managing PowerShell versions, ensuring that you're using the latest supported version of the Azure File Copy task should resolve this issue. Azure File Copy v6 is designed to be compatible with the latest Azure PowerShell versions, preventing the version mismatch error.