Ability to config Storage Explorer for production data vs test data

This is a feature request from a customer.

The main thing they are trying to avoid is accidental deletion or modification of production data.
Occasionally, on-call engineers will have to look at production data to investigate issues. Most of the data for existing titles is stored in Tables although they do have data in blobs and queues as well. Going forward they plan to use COSMOSDB, specifically tables. The on-call engineers are currently listed on all Azure subscriptions. This means that their default view in Storage Explorer is pretty overwhelming. Table names are similar or even identical across different subscriptions and storage accounts. The sheer number of accounts and similarly named resources makes it easy to lose the context of where they are, making accidental deletions or modifications a real concern. The concern is that an engineer would intend to delete a resource is a test environment and accidentally delete a similarly named resource in a product environment.

Feature request: Storage Explorer supports configure different profiles. One profile has all test accounts and a different one has all production accounts. This way, they at least have the confidence of what context they are in - they wouldn't accidentally mix test and production resources.
Other potential approach:

• being able to connect to entire subscriptions as read-only or opt-in to read-write access
• being able to snap the navigation tree to the currently viewed resource tab to provide context for whatever you are looking at

Contact info: Jacobs

No files, tests, or entry points are named. Start by locating how Storage Explorer groups subscriptions, storage accounts, tables, blobs, and queues, then investigate whether profiles or read-only access fit the existing model. Done means production and test resources can be kept in separate contexts without accidental cross-environment modification.