az copy blob using sas token still broken

[TimurSadykov]

Describe the bug

The problem is that if using Windows cmd, default double quotes will not work.

The issue was filed before: #30509

It provided a workaround with single quotes around double quotes, but it is still a bug and takes hours to figure out.

Please fix.

Related command

az blob copy start

Errors

failed to perform copy command due to error: Login Credentials missing. No SAS token or OAuth token is present and the resource is not public
Failed to perform copy operation.
'sktid' is not recognized as an internal or external command,
operable program or batch file.
'skt' is not recognized as an internal or external command,
operable program or batch file.
'ske' is not recognized as an internal or external command,
operable program or batch file.
'sks' is not recognized as an internal or external command,
operable program or batch file.

Issue script & Debug output

No additional debug output besides the error message

Expected behavior

Expected to copy the files from source to destination

Environment Summary

azure-cli 2.67.0

core 2.67.0
telemetry 1.1.0

Extensions:
load 1.4.0 (dev) C:\Workspace\Github\azure-cli-extensions\src\load

Dependencies:
msal 1.31.0
azure-mgmt-resource 23.1.1

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\mbhardwaj.azure\cliextensions'
Development extension sources:
C:\Workspace\Github\azure-cli-extensions

Python (Windows) 3.12.7 (tags/v3.12.7:0b05ead, Oct 1 2024, 03:06:41) [MSC v.1941 64 bit (AMD64)]

Additional context

No response

[azure-client-tools-bot-prd]

Hi @TimurSadykov,

2.67.0 is not the latest Azure CLI(2.82.0).

If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

[yonzhan]

Thank you for opening this issue, we will look into it.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• unable to copy from blob container using a sas-token #30509
• Windows SAS token parsed badly #9536
• az storage blob upload/download with SAS token not recognized in powershell #27705
• Using --sas-token to access storage causing parsing error in powershell core #24399

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

Wrap the SAS token in both single and double quotes. For example:

az storage copy --source '"https://****.*39.blob.storage.azure.net/*****?skoid=*****&sktid=*****&skt=*****&ske=*****&sks=*****&skv=*****&sv=*****&st=*****&se=*****&sr=****&sp=****&sig=****"' --destination 'C:\Workspace\downloads' --recursive

Reference:

• unable to copy from blob container using a sas-token #30509 (comment)
• Using --sas-token to access storage causing parsing error in powershell core #24399 (comment)

Solution 2:

Escape the SAS token properly for Windows. For example:

$sasTokenEscaped = $IsWindows ? "`"$sasToken`"" : $sasToken

Reference:

• Windows SAS token parsed badly #9536 (comment)

Solution 3:

Use Start-Process to pass the SAS token as an argument. For example:

$token = ' "?sv=2021-06-08&ss=..... t2KLwAE%3D" '
Start-Process az -ArgumentList storage,container,list,--account-name,storage,--sas-token,$token -NoNewWindow -Wait

Reference:

• Windows SAS token parsed badly #9536 (comment)

Powered by issue-sentinel