You press Sign in, Storage Explorer says Waiting for authentication…, and nothing else happens. No browser window, no error — it just sits there. This has been open in Microsoft's own issue tracker for years, so if it feels like the app rather than your account, that reading is fair.
Storage Explorer signs you in by launching your default browser. If it cannot launch it — an unusual default browser, a browser that opens into a locked profile, or a browser still starting up — the app waits forever for a callback that never comes.
The hang lives in the interactive sign-in flow. If you attach a storage account with an access key or a SAS token instead, there is no browser step at all:
This is also why key-based tools do not suffer this class of failure: there is no redirect, no callback, and nothing to wait on. The trade-off is real — account keys grant full access to that account, so treat them like passwords, and some organizations disable them on purpose.
If what you actually need is to look at a container and read a file, a full desktop app is a lot of moving parts to keep working. Reading blobs over the REST API with a key is a much smaller surface — that is the approach our IDE plugin takes, listed below.
These guides are written by sellerkit. We publish JetBrains IDE plugins, including one for Azure Blob Storage, listed below. Everything above works whether or not you use it.
Our plugin declares no upper IDE build limit, makes no network call until you press Connect, and each release is run through the JetBrains Plugin Verifier against multiple IDE versions before it ships.