User scenario:

• Currently when end-user runs the periscope, in the end, user gets prompted with shared storage uri which works well with storage-explorer.

Possible enhancement to this process:

• If we get user consent and generate the URL via user's SAS which is downloadable via web-browser then it saves the storage-explorer step.

💡 not sure the underlying work involved but this idea can be explored to make it simpler.