Open lswwan opened 3 years ago
@lswwan ,
Thanks for reaching out! We only support sync between Local <-> Blob, Blob <-> File and Local <-> File right now. Let me bring this to notice of my peers. @zezha-msft Also, it may be a shot in the dark but can you try using the equivalent blob endpoint for the URL once?
https://[storage_account_name].blob.core.windows.net/[container]/[path/to/folder]"
@lswwan ,
Thanks for reaching out! We only support sync between Local <-> Blob, Blob <-> File and Local <-> File right now. Let me bring this to notice of my peers. @zezha-msft Also, it may be a shot in the dark but can you try using the equivalent blob endpoint for the URL once?
https://[storage_account_name].blob.core.windows.net/[container]/[path/to/folder]"
Already tried but didn't work since the service principal that I used only have POSIX Level permission at folder level.
Which version of the AzCopy was used?
AzCopy 10.10.0
Which platform are you using? (ex: Windows, Mac, Linux)
Windows 10
What command did you run?
azcopy login --service-principal --application-id XXXXXXX azcopy sync "C:\path\to\folder" "https://[storage_account_name].dfs.core.windows.net/[container]/[path/to/folder]"
What problem was encountered?
The following error was captured:
error parsing the input given by the user. Failed with error source 'C:\path\to\folder' / destination 'https://[storage_account_name].dfs.core.windows.net/temp/folder' combination 'LocalBlobFS' not supported for sync command
How can we reproduce the problem in the simplest way?
The problem can be reproduced every time you run the same azcopy command
Have you found a mitigation/solution?
Use the blob endpoint ".blob.core.windows.net" can fix the problem but require "Storage Blob Data Contributor" role.