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. Manage SAS Token by Name and Include in Audit Logs

    Give SAS tokens a name when generating then:
    - allow report/table of all generated token
    - allow revoke of exisiting token (or modification of access)
    - use the SAS token name in storage audit logs

    At the moment, the storage access logs do not show any useful information about who has made access, and this is critical to a practical audit function.

    3 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

      Thank you for your feedback. Currently you can use a stored access policy to manage revocation of an existing token. You are also able to track requests made using an existing stored access policy in the storage account logs. See https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1#controlling-a-sas-with-a-stored-access-policy for more details. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

    • Remove or dramatically increase the max number of stored access policies per container, file share, table, or queue

      Today the maximum policy you can have is 5. This is way to low as we are using blob storage in a data sharing scenario between providers and consumers and we need to use policies to be able to revoke issued SAS tokens in this sharing scenario. 5 policies means that we can only control 5 SAS keys that can be revoked. We need a lot more.

      38 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
      • CloudStorageAccount.Parse(): Support SafeString

        CloudStorageAccount.Parse(): Today takes string as parameter, as it contains username/password, I think it would be better if it took a SafeString.

        0 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
        • Improving the indexed partitioning criteria for handling storage accounts with same naming conventions

          As described in detail here: https://azure.microsoft.com/en-us/documentation/articles/storage-performance-checklist/#subheading47 , Azure handles indexed partitioning with an index with aphabetical criteria, so storage accounts starting with A-H will go into one partition, H’-R will go into a different partition and last R’-Z will go into another different partition too.
          We discovered that this could affect High Availability of VMs if you take care of putting them into Availability Set and use different storage accounts for their virtual disks, but same naming convention for accounts. In this case, if a fail happens on a given partition for example during an internal maintenance task or storage…

          4 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
          • Azure Control Panel functionality for snapshots or incremental backup

            I know that data is replicated but that doesn't protect against logical errors, accidental removal by admin or hacker screwing up the data.

            So I really would like to see this done natively from Azure instead of building my own backup systems like these:
            http://blogs.msdn.com/b/windowsazurestorage/archive/2010/04/30/protecting-your-blobs-against-application-errors.aspx

            http://blogs.msdn.com/b/windowsazurestorage/archive/2010/05/03/protecting-your-tables-against-application-errors.aspx

            910 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              16 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

              Our apologies for not updating this ask earlier. We view this ask as a set of related features. Recycle Bin for Blobs will address data loss as a result of logical errors. It will provide functionality to automatically generate and retain snapshots each time data is deleted or overwritten. You will be able to restore this data within a configurable retention period. This feature is at the front of our backlog.

              Object Versioning for Blobs will also address data loss as a result of logical errors. It will provide an interface to store and access multiple versions of the same object. This feature is also on our backlog for delivery after Recycle Bin.

              Write Once Read Many (WORM) protection for Blobs will disable object modification (by anyone, including administrators and hackers) for a specified period of time. This feature is also on our backlog.

              We will be delivering…

            • Don't see your idea?

            Feedback and Knowledge Base