This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
Choosing an existing Storage Account may fail with the error "The remote server returned an error: (400) Bad Request" #2
Labels
bug
Something isn't working
Comments
|
This issue is now resolved |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Additional Details
While trying to use an existing storage account, the SAS key generation failing with the error “The remote server returned an error: (400) Bad Request.” This issue happens when someone chooses "StorageV2 (general purpose v2)" storage account and it appears that endpoints for V2 storage accounts accept calls over TLS 1.2 protocol only.
This issue will be addressed in DaaS version
1.43where in all the DaaS code will force all the outbound calls over TLS 1.2 protocol only. Once DaaS Version 1.43 is available everywhere in Azure App Service, this issue will be closed.The text was updated successfully, but these errors were encountered: