### Description Object storage uploads break with an invalid `x-ms-version` header when setup on Azure Stack Hub environment. The error snippet indicates it expects service version `2023-08-03` which was set as [default](https://github.com/Azure/azure-storage-azcopy/blob/main/ChangeLog.md#version-10220) in azcopy version 10.22.0 > Updated all SDK dependencies to their latest version and the default service version to `2023-08-03` for all services. ([#2402](https://github.com/Azure/azure-storage-azcopy/pull/2402)) ``` RESPONSE 400: 400 The value for one of the HTTP headers is not in the correct format. ERROR CODE: InvalidHeaderValue -------------------------------------------------------------------------------- <?xml version="1.0" encoding="utf-8"?><Error><Code>InvalidHeaderValue</Code><Message>The value for one of the HTTP headers is not in the correct format. RequestId:redacted Time:2025-06-26T12:20:53.3435591Z</Message><HeaderName>x-ms-version</HeaderName><HeaderValue>2023-08-03</HeaderValue></Error> -------------------------------------------------------------------------------- ERROR DETAILS: https://aka.ms/AzCopyErrgor/InvalidHeaderValue ``` One of the recent GitLab updates was to "[Update dependency Azure/azure-storage-azcopy to v10.28.0](https://gitlab.com/gitlab-org/build/CNG/-/merge_requests/2203)" but it seems Azure Stack Hub only supports older service versions with the [latest](https://learn.microsoft.com/en-us/azure-stack/user/azure-stack-acs-differences?view=azs-2501#api-version) being `2020-10-02` ### Possible workaround Users can specify the API version to override the default using `AZCOPY_DEFAULT_SERVICE_API_VERSION` but this is not stated as supported or documented within GitLab object storage. The issue is to help verify if there is any other workarounds for users to modify the service version headers and workaround such updates whenusing Azure Stack Hub which uses older versions..