-
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
recently getting error #2944
Comments
Turns out there is a workaround, not sure why it works, but here it is:
|
Hi @lovettchris, Which version of AzCopy are you encountering this issue with? |
azcopy version 10.28.0 |
There is an issue with the device login flow in AzCopy 10.28.0 version. The fix will be included in the next release. In the meantime, you can use AzCopy version 10.27.1 if you need to use device code authentication for AzCopy login. Thanks. |
Good to know, thanks. |
Today I'm getting a new error and so your workaround is not working. "az login" succeeded by the following failed:
Saying:
|
azcopy login has been rock solid for years now, but just this week I'm starting to get a bunch of errors.
Error Code: 530033
Request Id: a7e1d4dd-8171-42c5-bf08-17951d892b00
Correlation Id: 3b0a8452-6fc9-4317-a1de-385cc2f35567
Timestamp: 2025-02-13T02:20:34.686Z
App name: Azure Storage AzCopy
App id: 579a7132-0e58-4d80-b1e1-7a1e2d337859
IP address: 73.157.66.142
Device identifier: 5ffc0ca6-c2af-4b20-9eb0-583381a5da1e
Device platform: Windows 10
Device state: Compliant
Weird thing is this error happens right after I was able to do a successful
az login --use-device-code
which is weird because I thought both were using the same authentication gateway...??? Any ideas? My machine is clean and says I can access company resources and what is more weird, my desktop machine in the office using the same user account and smart card can doazcopy login
without any problems, so it is not my account, somehow my laptop at home is suddenly missing something? Do I need to refresh some certificate or something?The text was updated successfully, but these errors were encountered: