Sign-in fails for custom environment with empty additional properties using Authentication Broker and Default Web Browser methods

[v-xianya]

Storage Explorer Version

1.41.1

Regression From

Not a regression

Architecture

arm64

Storage Explorer Build Number

20260310.2

Platform

Windows

OS Version

Windows 11 arm64/Windows 11 x64/MacOS Sequoia 15.6.1/Linux Ubuntu 22.04

Bug Description

When adding a new custom environment in Storage Explorer and leaving the Additional properties field empty, the sign-in process fails. This issue reproduces when using both Authentication Broker and Default Web Browser sign-in methods.

However, if the Additional properties are automatically populated when the custom environment is created, the sign-in succeeds without issues.

Resource Types

No response

Authentication Method

None

Connection Type

None

Steps to Reproduce

1. Open Storage Explorer.
2. Open the Connect dialog and select Subscription.
3. Click Manage custom environment….
4. Add a new custom environment and leave Additional properties empty.
5. Select the newly added custom environment and proceed to Sign in.
6. Check whether the sign‑in succeeds.

Actual Experience

Sign-in fails.

Expected Experience

Sign-in should succeed even if Additional properties are empty, or the application should prompt the user to provide the required values.

Additional Context

If the Additional properties are automatically filled when creating the custom environment, the sign-in succeeds without issues.

[craxal]

@v-xianya This suggests the optional properties aren't as optional as the label suggests. What endpoints did you use when this issue occurred?

[v-xianya]

Hi @craxal
Sign-in fails when using this custom environment with no additional properties.

Sign-in succeeds when using custom environment with additional properties filled.