Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No possibility to authenticate via non default tenant because Auth window doenst open in external browser anymore.

Open
#9,139 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
azure

Research direction

Start by reproducing the Windows sign-in flow in Storage Explorer v1.44.0 with access only to a non-home tenant. Compare the embedded authentication behavior with the former external-browser flow and investigate how tenant selection is handled. Done means an unauthenticated user can select an accessible tenant before authentication and sign in to that tenant.

Written by the indexing model from the issue text.

Description

:beetle: regression :computer: windows :gear: sign-in
Storage Explorer Version

v1.44.0

Regression From

No response

Architecture

x64

Storage Explorer Build Number

No response

Platform

Windows

OS Version

No response

Bug Description

No possibility to authenticate via non default tenant because Auth window doenst open in external browser anymore.

In our corporate environment we have users with access to Storage Accounts in different tenants, not in the home tenant.
In the home tenant they have no Azure permissions at all.
Therefore Auth fails because auth happens by default on the home tenant. Before this version the auth window opened in the external browser, so we were able to change the Tenant ID and login.
But now this is not possible anymore because the auth happens within an window in Storage Explorer.

The perfect solution would be to allow the user to pick the tenant for auth before the auth prompt happens.

Resource Types

No response

Authentication Method

Sign in

Connection Type

Sign in (subscription)

Steps to Reproduce
  1. Launch Storage Explorer (completely unauthenticated)
  2. Sign In
  3. Embedded Auth Window opens with home tenant which is declined as the user has no permissions for Azure resources in the home tenant. The user can't pick a foreign tenant.
Actual Experience
  1. Launch Storage Explorer (completely unauthenticated)
  2. Sign In
  3. Embedded Auth Window opens with home tenant which is declined as the user has no permissions for Azure resources in the home tenant. The user can't pick a foreign tenant.
Expected Experience
  1. Launch Storage Explorer (completely unauthenticated)
  2. Sign In
  3. User can pick a tenant to connect - users tenants are being listed if he has multiple.
  4. Auth in selected tenant
Image
Additional Context

No response

Dominant language
No language data
Stars
455
Forks
92
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/AzureStorageExplorer

All issues in microsoft/AzureStorageExplorer

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.