Storage

How can we improve Azure Storage?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Storage to have readonly key for blobs

    Allow for Storage to have Read only keys that can be used in client tools like Azure Storage explorer or Cloudberry for read only access.
    Often times, a client tool needs to be given to customer to access files and it is not feasible to give the shared key which has full access.

    Even better would be to allow for a "user" key to be generated with granular permissions on containers that can be set from Azure portal.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Storage Explorer  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for you feedback. Currently we are in public preview of Azure Active Directory authentication for storage. This feature set allows you to use Azure’s role-based access control framework to grant specific permissions to users, groups and applications down to the scope of an individual blob container or queue. You can see the public preview announcement here: https://azure.microsoft.com/en-us/blog/announcing-the-preview-of-aad-authentication-for-storage/

    For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

  2. Please fix standalone Azure Storage Explorer to not change DateTime fields

    I'm using the standalone Azure Storage Explorer with a Table Storage database and when I double-click a row to see the fields and then click Update, Azure Storage Explorer changes the DateTime fields even though I didn't make any changes. It's adding 6 hours each time.

    It's easy to reproduce: open a table with a DateTime field, double-click a row, don't change anything - just click Update. Then open the same row and you'll see the time has changed. Click update again. Open the row again - the time changed again (adding 6 hours each time)!

    While searching for help…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Storage Explorer  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base