-
Notifications
You must be signed in to change notification settings - Fork 231
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
AZCOPY_MSI_RESOURCE_STRING does not work with MSAL #2395
Comments
The option has been deprecated :
|
This doesn't make any sense, quoting from the official docs: https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-authorize-azure-active-directory?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json We were originally using "RESOURCE_STRING" not "OBJECT_ID" RESOURCE_STRING, which I'm assiming is Resource ID should work and used to. Example:
|
Please forgive me, I misread your issue. |
Hi, I believe this issue was fixed by the following PR #2406 This should be released as part of our 10.22 release |
The 10.22.0 version was just released. Closing this issue as a result. |
Which version of the AzCopy was used?
v10.21.0
Which platform are you using? (ex: Windows, Mac, Linux)
Linux (specifically shell extension in ev2)
What command did you run?
What problem was encountered?
How can we reproduce the problem in the simplest way?
Use any bash shell with User assigned managed identity, in my case it was in ev2
Have you found a mitigation/solution?
Use client ID instead of resource string
The text was updated successfully, but these errors were encountered: