Contrasting outcomes when downloading Maven artifact from Azure Artifacts using REST API in Powershell - powershell

Question

I am running the below script in a Powershell ISE console to download a Maven package from our Azure Artifacts repository and and it works perfectly, downloading the war file to my local directory successfully.
Run in Powershell ISE
$url = 'https://pkgs.dev.azure.com/{organisation}/{project}/_apis/packaging/feeds/{feedID}/maven/{groupID/{artifactID}/{version}/{filename}/content?api-version=6.1-preview.1'
$connectionToken="my-personal-access-token"
$base64AuthInfo= [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($connectionToken)"))
$buildPipeline= Invoke-RestMethod -Uri $url -OutFile .\xxx-portal-18.29.06.war -Headers #{Authorization = "Basic $base64AuthInfo"} -Method Get
However, when I run the same script (albeit with a different output directory) from an Azure Pipelines Powershell Task as depicted below, it fails miserably. The error written to the Pipeline log appears to suggest the failure is down to an authentication issue. What could I be doing wrong and am I using the correct authentication method?
Run as an Azure Pipelines Powershell Task
$url = 'https://pkgs.dev.azure.com/{organisation}/{project}/_apis/packaging/feeds/{feedID}/maven/{groupID/{artifactID}/{version}/{filename}/content?api-version=6.1-preview.1'
$connectionToken="my-personal-access-token"
$base64AuthInfo= [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($connectionToken)"))
$buildPipeline= Invoke-RestMethod -Uri $url -Outfile $(Build.BinariesDirectory)\xxx-broker-portal-18.29.06.war -Headers #{Authorization = "Basic $base64AuthInfo"} -Method Get

Answer 1

We create a new Project-scoped maven feed and follow this blog: Maven Package Management with Visual Studio Team Services to publish a maven package. And then using this API: Maven - Download Package to download below war file with your provided PowerShell script.
And we run the same script (albeit with a different output directory) from an Azure Pipelines PowerShell Task, all work as expected.
Please check if you have proper permissions to write xxx-broker-portal-18.29.06.war file to target directory: $(Build.BinariesDirectory). If you own the administrator role for this private agent and can manage directories(Read, write, & manage) where this agent located in, this error should not occur.