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. Static website hosting in Azure blob storage

    This would require supporting default file to render and somekind of redirect from root to a particular container.

    2,166 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      70 comments  ·  Blobs  ·  Flag idea as inappropriate…  ·  Admin →

      Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.

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

    • Provide Time to live feature for Blobs

      If I need to provide a user (or external system) some data (blob) which might be outcome of some processing (or other) and it has some expiration time I'd like to just put a new blob and set TTL property with TimeSpan (or set absolute DateTime). When the period is over my blob is deleted. So I don't have to pay for it and don't need to spin up some service for doing it myself.

      1,174 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        34 comments  ·  Blobs  ·  Flag idea as inappropriate…  ·  Admin →

        Thank you for your feedback. We are currently in public preview of blob storage lifecycle management. The feature set offers a rich, rule-based policy engine which you can use to transition your data to the best access tier and to expire data at the end of its lifecycle. See our post on the Azure Blog to get started: https://azure.microsoft.com/en-us/blog/azure-blob-storage-lifecycle-management-public-preview/preview/.

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

      • 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

        1,046 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          25 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

          Thank you for your feedback. We view this ask as a set of related features.

          Soft delete for blobs enables you to save and recover your data where blobs or blob snapshots are deleted. It does not protect against container or account deletion. This feature is currently generally available. You can see the announcement here: https://azure.microsoft.com/en-us/blog/soft-delete-for-azure-storage-blobs-ga/ and the full documentation here: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-soft-delete

          Object versioning will also offer object-level protection, and will offer a few incremental improvements to soft delete. Specifically, it will make recovery of deleted data easier. This feature is planned for the coming year.

          Container soft delete will protect against container-level deletion and modification. This feature is planned for the coming year as well.

          Native support for blob backup will protect against account-level deletion and modification, and is currently on our backlog.

          We will provide updates when they become available. For any further questions, or to discuss your…

        • Provide me with full text search on table storage

          Does what it says on the tin....really need better search capabilities over azure table storage.

          921 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            43 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →

            A common need for users of Azure Table Storage is searching data in a Table using query patterns other than those that Table Storage provides efficiently, namely key lookups and partition scans. Using Azure Search, you can index and search Table Storage data (using full text search, filters, facets, custom scoring, etc.) and capture incremental changes in the data on a schedule, all without writing any code. To learn more, check out Indexing Azure Table Storage with Azure Search: https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-tables

          • Allow user-based access to Blob Containers (for support employees)

            For auditing purposes and to prevent data corruption, we want to give our support employees a user-centric, read-only access to Blob Containers in order to be able to investigate possible data corruptions (caused by bugs in systems).

            This is not possible now because the security architecture of Blob Service does not even know the concept of users or roles.

            SAS is not secure enough mechanism because it gives access to anyone by just sharing a link + you can't track who's actually using it.

            297 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              9 comments  ·  Blobs  ·  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.

            • Add a way to copy the contents of an entire storage account to another storage account

              Say your application stores important data in an Azure Storage Account, perhaps spread across both Table and Blob containers.

              It would be very handy to be able to copy the entire contents of a storage account to another storage account. So that you could duplicate your azure storage environment between your stage production environments easily, allowing you to test updates to your application on a copy of your live production data before actually deploying it to production.

              I know that bits and pieces of this functionality exist already, via things like Copy Blobs and Blob Snapshots, but nothing built in…

              143 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                13 comments  ·  AzCopy  ·  Flag idea as inappropriate…  ·  Admin →

                Thank you for your feedback. We would like to get more feedback about this item before we prioritize. Is the ask here to replicate a storage account on-demand ? Or have a mechanism to always keep two or more storage accounts in sync ?

                Meanwhile, to unblock some of our users we have published a sample that copies blobs from an account to another account: https://docs.microsoft.com/en-us/azure/storage/scripts/storage-common-transfer-between-storage-accounts?toc=%2fpowershell%2fmodule%2ftoc.json

              • Allow setting Archive tier at the account and container levels

                Currently the archive tier can be set only at the blob level. There are plenty of uses cases for having entire storage accounts or containers for archival where setting the tier for each blob is tedious and non-value-adding.

                117 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  7 comments  ·  Blobs  ·  Flag idea as inappropriate…  ·  Admin →

                  Thank you for your feedback. We are currently in public preview of blob storage lifecycle management. The feature set offers a rich, rule-based policy engine which you can use to transition your data to the best access tier and to expire data at the end of its lifecycle. This framework can be used to match and tier blobs based on prefix to enable batch archiving of an account, containers, or even virtual directories. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for account and container level archiving exists. See our post on the Azure Blog to get started: https://azure.microsoft.com/en-us/blog/azure-blob-storage-lifecycle-management-public-preview/preview/.

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

                • Azure storage - WORM capable blobs

                  To better use Azure as a compliant storage for archiving, it'd be nice to have Azure to support WORM feature. More info is on the below thread:
                  http://social.technet.microsoft.com/Forums/windowsazure/en-US/79258196-b8e1-4e10-90f2-feed54d69d0e/azure-and-worm-for-compliance?forum=windowsazuredata

                  78 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    4 comments  ·  azure.microsoft.com  ·  Flag idea as inappropriate…  ·  Admin →

                    Thank you for your feedback. We are currently in public preview of immutable storage for Azure Blobs which will enable you to keep your data in a non-erasable and non-modifiable state for a configurable retention interval. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-immutable-blob-storage-now-in-public-preview/

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

                  • Provide an actual "read-only" role for Azure File Service

                    The reader role available in RBAC doesn't really do what you think it'd do when applied to Azure File Service. A user with this role can't even see the Azure File Service when browsing the storage account.

                    As I understand it this is by design as the reader role works on Azure objects and not on files and folders.

                    What I need is a method that prevents users from accidentally deleting files or folders by giving them read-only access to the actual files and folders. I don't need fine grained control over access to files and folders, just a straightforward…

                    59 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      1 comment  ·  Files  ·  Flag idea as inappropriate…  ·  Admin →

                      Thank you for this feedback!

                      We’re working on or have shipped several features that we think will satisfy this request.

                      First, we have shipped the share snapshot feature, which enables you to protect a point-in-time for a file share. If a user were to delete a file, you can restore from the previous snapshot. To make this easier, Azure Backup will soon support scheduling share snapshot.

                      Second, and more to the specific ask in the initial post, we are working on AAD authentication and authorization for Azure file shares. When we ship this feature, you will have the ability to set share ACLs that prevent deletes or modifications.

                      Thanks,

                      Will Gries
                      Program Manager, Azure Files

                    • 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.

                      16 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        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.

                      • more detailed error messages

                        We've run into an issue where data we tried to store wouldn't fit in the blob file. The error message was (416) The page range specified is invalid.

                        At first it wasn't clear whether we were trying to start saving beyond the page file or data didn't fit or something else was culprit. Eventually we figured it out.

                        It would be nice if the error message would provide more details: page size, size we tried to save, location we tried to save within the file, etc. This would've showed us the issue right away. Instead we had to spend a…

                        12 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          2 comments  ·  Blobs  ·  Flag idea as inappropriate…  ·  Admin →

                          Thank you for your feedback. We are currently working on providing this functionality and will provide updates when they become available. See the following article for the latest: https://docs.microsoft.com/en-us/rest/api/storageservices/status-and-error-codes2. Note that for REST API version 2017-07-29 and later, failed API operations also return the storage error code string in a response header. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

                        • Increase the size of a BLOB Storage Account to an indefinite amount

                          I'm currently working on a solution which will be using multiple storage accounts which will continue to grow indefinitely.
                          The 100TB limit means that I have to continuously list the blobs in my container to workout what the total size used is and then determine if I need to create a new storage account on the fly. This is cumbersome and time consuming for the type of performance the business requires.

                          It would be better to remove the account size limitation which would simplify the solution considerably and remove all the blob listing look-ups which seem counter intuitive. The only…

                          9 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            3 comments  ·  Blobs  ·  Flag idea as inappropriate…  ·  Admin →

                            Thank you for your feedback. We are currently working on increasing the scale limits of storage accounts. See the following post for updated capacity limits (currently at 5 PB for a single storage account): https://azure.microsoft.com/en-in/blog/announcing-larger-higher-scale-storage-accounts/. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.

                          • Email Notifications of Storage/Capacity

                            have email notifications of storage limit or service capacities. Recently ran out of space w/ no warning...

                            7 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
                            • 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
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                2 comments  ·  Storage Explorer  ·  Flag idea as inappropriate…  ·  Admin →
                              • highlight how to disable Nagle's algorithm in your performance optimization MSDN articles

                                The MSDN article that describes Nagle's algorithm (http://msdn.microsoft.com/en-us/library/windowsazure/hh697709.aspx) should highlight the performance gains from disabling Nagle's algorithm.

                                In our case, disabling that algorithm yielded an order of magnitude improvement in latency (from 300 to 30 ms). This is a vital piece of information that is not highlighted in performance optimization documentation for Azure.

                                It may even be worthwhile to consider disabling Nagle's algorithm by default, or provide some default configuration examples that remark on this algorithm.

                                1 vote
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  0 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
                                • Don't see your idea?

                                Feedback and Knowledge Base