Storage
-
make it possible to use SSL on blob storage using custom domains
Currently you can use SSL but you have to user the standard URL. You can create a CNAME to your storage account but most browsers complain that the traffic was rerouted and is possibly an attack. There should be a way to install a domain certificate to your containers.
4,215 votesYou can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.
Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at azurestoragefeedback@microsoft.com.
-
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,191 votesThank 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,227 votesThank 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.
-
Rename blobs without needing to copy them
Copying blobs in order to rename them is a heavy operation, especially when the blob is big, or when you need to change many files, such as when changing a directory name.
643 votesOur apologies for not updating this ask earlier. Renaming Blobs is on our backlog, but is unlikely to be released in the coming year. Today, you can use the “Copy Blob” API as a workaround.
Using the Azure Files service you can address Azure Storage like a network share using the SMB2.1 protocol. This enables usage of normal Windows API’s to rename files and directories. You can get started with the Files service by visiting https://docs.microsoft.com/en-us/azure/storage/storage-dotnet-how-to-use-files.
For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
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.
301 votesThank 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.
-
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.
127 votesThank 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.
-
Auto defragment append blobs
Append blobs are great, however, when a such a blob is generated through a long series of small increments, the read performance of the resulting blob is very poor: from 10x to 20x slower than reading a regular page blob.
The performance problem goes away if the app rewrite the append-blob in large 4MB chunks. However, this process is complicated to setup, and collides with any 'always-on' property of the app.
As append blobs are append-only, it would be much better if Azure was taking care of defragmenting the append blobs on its own; possible through a dedicated API operation…
52 votesThank you for your feedback. This work is planned for the coming year. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Make Blob access policies Azure Resource Manager managed
In order to apply Azure Policies the item you want to control has to be ARM managed. Apparently Blob Access Policies are not ARM managed (i.e. resource that can be managed by calling https://management.azure.com/[ResourceId]). Because of this the Azure Policies product group can't make a policy alias to audit/deny the use of public containers/blobs, see: https://github.com/Azure/azure-policy/issues/131.
This is a big issue because the use of anonymous access to storage containing enterprise data is a huge risk.
37 votes -
Allow adding headers to static website hosting in blob storage
The static website hosting is fantastic, to make this feature even more awesome please allow adding of custom headers like CSP, HSTS etc secure the static website.
32 votes -
hotlink prevention
Preventing others to consume my Azure resources via HTTP_REFERER header validation.
This is a common scenario for blogs, websites etc.Scott Hanselman has even written a blog post about it: http://www.hanselman.com/blog/BlockingImageHotlinkingLeechingAndEvilSploggersWithIISUrlRewrite.aspx
19 votesThank you for your feedback. This ask will be discussed amongst our team to determine if we plan to do this and when. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Support GZIP & DEFLATE Content-Encoding for List Blobs Responses
For collections with large numbers of blobs, the XML response payload easily approaches 100s of MBs. In our testing, each block of 5000 objects resulted in a ~2.8MB response. This is without any other flags set (i.e. no snapshots, no metadata, no uncommitted blobs). The response XML is highly compressible. In our testing we saw a 93% size reduction. (2.8MB -> 210KB). This would be a huge improvement in transfer performance, and a large cost savings in egress bandwidth situations.
19 votesThank you for your feedback. Transfer compression will address this ask and is on our backlog. As soon as we have progress to share, we will do so. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Server side delete, rename of virtual folder
Currently if I have millions of documents inside a virtual folder, there is not way to delete them without actually iterating through everything, which is extremely time consuming (weeks to process deletions)
For example, if you have multiple containers, which in turn have multiple virtual folders with millions of blobs, moving, renaming or deleting the "folder" is impossible without some painfully slow iterating through everything.
thanks!
15 votesThank you for your feedback. Both batch delete of storage blobs and blob rename are on our backlog, but there is no ETA we can provide at this time. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Support If-Modified-Since precondition in blob enumeration APIs
(Unless I've missed it somewhere) It would be real nice if last modification time filtered blob enumerations could be applied server-side.
12 votesThank you for your feedback. This ask will be discussed amongst our team to determine if we plan to do this and when. We will provide updates when they become available. 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 votesThank 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.
-
We would like to audit/log delete operations on Azure blob storage containers. Currently we can only do this at a Storage Account layer.
We are simply looking for more granularity with our storage logging in Azure. If someone were to view/delete our blob containers, we would like to see these operations logged and have the ability to alert on them.
11 votesThank you for your feedback. Firing events on container deletions is on our backlog but there is no ETA we can share at this time. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Add capability for bulk deletion of blobs
Right now, deletion of a container is the only way a number of blobs can be deleted together. The drawback, however, is that the container name cannot be used again for some time. This causes inconvenience for a number of use cases.
Proposal: There should at least be way for emptying the container in one API call
11 votes -
CORS Rule
Currently we are able to enable CORS with exact domain(ex: http://www.abc.com) or all origin ("*"). can you provide feature for supporting all sub domains say http://*.abc.com so that CORS will enabled for all sub domains of abc.com and restricted for all other domains.
9 votesThank you for your feedback. This ask will be discussed amongst our team to determine if we plan to do this and when. We will provide updates when they become available. 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 votesThank 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.
-
Implement viewer for json / csv blob files
At the moment the only way to view a files in storage blobs is to download it and open it within an editor. This is fine for larger files, but for the smaller ones it would be a bit easier to be able to get a quick (pre)view of the file in the browser by just clicking it. Should not be that hard to implement an additional pane with a view of the raw file contents.
9 votesThank you for you feedback. This work is planned for the coming year. We will provide updates when they become available. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
create an API method for getting the number of BLOBs in a Container
As far as I understand, there is currently no method for getting the total number of blobs in a single container.
And there is also the maximum number of blobs per request (5.000).
We have containers with 10k - 100k blobs so we would really need a way of quickly checking the number of blobs that are in a container.
9 votesOur apologies for not updating this ask earlier. Storage analytics at the container level is on our backlog, but is unlikely to be released in the coming year. Currently, account level analytics are available. In order to monitor, diagnose and troubleshoot an Azure Storage account, please see https://docs.microsoft.com/en-us/azure/storage/storage-monitoring-diagnosing-troubleshooting. In .Net you can now use the Analytics class to process these metrics. The API can be referenced at https://msdn.microsoft.com/en-us/library/azure/microsoft.windowsazure.storage.analytics.aspx. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
- Don't see your idea?