Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Support for Azure Files to Azure Files Sync Using Identity #2183

Closed
mbrat2005 opened this issue Apr 22, 2023 · 3 comments · Fixed by #2271
Closed

Add Support for Azure Files to Azure Files Sync Using Identity #2183

mbrat2005 opened this issue Apr 22, 2023 · 3 comments · Fixed by #2271
Assignees
Milestone

Comments

@mbrat2005
Copy link

Which version of the AzCopy was used?

10.18.1

Which platform are you using? (ex: Windows, Mac, Linux)

Windows and Linux

What command did you run?

azcopy sync https://filesyncfunction01.file.core.windows.net/sourceshare/ https://filesyncfunction03.file.core.windows.net/destshare/ --preserve-smb-info --preserve-smb-permissions --recursive

What problem was encountered?

Difficult error message:
error parsing the input given by the user. Failed with error service level URLs () are not supported in sync:

--> https://github.com/Azure/azure-storage-azcopy/blob/main/cmd/pathUtils.go#L260

How can we reproduce the problem in the simplest way?

  1. azcopy login
  2. Run command as above with two shares

Have you found a mitigation/solution?

Continue using SAS tokens.

@nakulkar-msft
Copy link
Member

Hi @mbrat2005, sorry. The error is misleading. Azure Files does not yet support using Identity or other forms of oAuth yet. Use a SAS token on both source and destination.

@mbrat2005
Copy link
Author

It would be great if the error were more clear, but even better if AzCopy supported identity based file sync--especially with more customers moving to further secure their Storage Account by disabling key-based auth.

@gapra-msft
Copy link
Member

This should be fixed in 10.20.0. Thanks for your patience while we got the release out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants