Workaround for Azure Storage Explorer using hard coded ports

Question

While Storage Emulator can be configured to use any set of ports, storage explorer is hard coded to use 10000, 10001, and 10002. We have a necessary third party app that uses hard coded 10001. What can we do to work around this problem?

Answer 1

@NCTom Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.

On the latest version of Storage Explorer you should be able to do an emulator connection with custom port values:

Are you referring to the “(Emulator – Default Ports)” node? If so, they you are correct; this node is hard-coded to connect to the default ports.
You to connect to an emulator listening to different ports, they can set up that connection by going through the Connect dialog:

Hope this helps!

Kindly let us know if the above helps or you need further assistance on this issue.

-------------------------------------------------------------------------------------------------------------------------------------------------------------

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.