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,720 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.
-
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.
875 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.
-
Azure Antimalware should be able to scan blob storage
Azure Antimalware should be able to scan blob storage. Currently you have to save the file a a file system for the real time protection to be able to scan it. Once it has been scanned then you would have to move it to the blob storage. Would like to be able to write directly to blob storage and have the real time protection monitoring the files.
291 votesWe will take a look. This is an interesting idea!
-
Ability to mount a blob or virtual disk as an iSCSI device
Either blobs or virtual disks should be mountable as as an iSCSI device. Right now, I'd have to create a windows server with an iSCSI target. This seems like madness because the blob is already some kind of virtual device.
iSCSI is ideal for clustering and availability services and would solve problems with SQL Server clusters and other Windows Server cluster requirements.
277 votesRight now, we don’t plan to add this support but up-vote this and we could consider.
-
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.
25 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.
-
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
22 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.
20 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.
-
Support "Last Accessed" timestamp in blob metadata
With the new "Cool Storage" feature announced recently, it would be useful if we could tell when our "Hot" blobs were last accessed, so we could push them to Cool storage where appropriate. We could achieve this with a proxy service and SAS signatures, but having this automatically updated in the blob metadata itself would be much simpler and remove the requirement for any compute resource being required for simply accessing a blob.
17 votesThank you for your feedback. Allowing users to define policies to tier data based on access patterns 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.
-
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.
-
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.
-
SAS behavior for replacing/overwriting blobs
It would be useful to define in the SAS token what to do in case of creating a blob with an existing name. The current behavior replaces/overwrites the existing blob.
Furthermore the default behavior is somehow a security threat, because a hacker having a SAS could replace existing entries.7 votesThank you for your feedback. Today, a write (w) permission would be required in the SAS for replacement of existing entries. We have work planned to automatically generate snapshots on overwrites to save existing data in this case. 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.
-
Blob Storage :: Enable filtration in listing APIs
The Azure Blob Storage service is intended to be scalable, but the APIs do not enable filtration of results. The Azure Blob Storage service should enable filtration of container and blob listing at the service fabric layer.
7 votesThank you for your feedback. To help us better understand your specific scenario and what kinds of filters need to be supported, please send us an email at azurestoragefeedback@microsoft.com.
-
Make blob storage publisher publish snapshot events for Event Grid
Currently the blob storage publisher can publish BlobCreated and BlobDeleted when an object is created/update and deleted respectively. However no events are published when a blob is snapshotted.
6 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.
-
"Snapshot if exists" function
At the present time, running the "Snapshot Blob" operation against a non-existent blob yields an error.
It would be very useful to have a "Snapshot if exists" operation (or indeed an option on the present "Snapshot Blob"). So that if a blob does not exist, no error is generated.
6 votesThank you for your feedback. To help us better understand your specific scenario, please send us an email at azurestoragefeedback@microsoft.com.
-
CloudPageBlobs should have a CURRENT snapshot name that always points to the latest
CloudPageBlobs should have a CURRENT snapshot that always directly follows the latest version of the blob it is refrencing. This would allow for many read-only mounts of the VHD with out having to manage the create/delete cycle of time stamped labels. Additionally this mount would reduce the unmount/remount cycle that moves around drive letters and can mess up previously opened files.
5 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.
-
move pageblobs already in the cloud to cool storage, you can't!
I was on the phone today with Microsoft Azure. I have 12TB of data in pageblobs that I would like to move to azure cool storage for archiving. Well, the only way to do that is to download them to local HDD and then convert and upload to cool storage. You can not at this time transfer from your azure storage files "in the cloud" over to cool block blobs. Plus, another limitation is that block blobs have a size limit of 195GB due to its internal architecture. I have plenty of pageblobs over 1tb that I would like to…
5 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.
-
Fix Bug: Azure Blob Client has issues when reading a stream that is larger than StreamMinimumReadSizeInBytes and the buffer is not base2
See attached example C# file that illustrates the issue.
When using an pageBlob.OpenRead(), along with a non-base2 buffer (i.e. 15 vs 16 bytes) to read the stream ( blobStream.Read(blobBuffer, 0, blobBuffer.Length); ) it will fail when you cross the boundary defined by StreamMinimumReadSizeInBytes3 votes -
Add the lease start datetime as a property of a blob
That will allow us to calculate the age of the lease, which will help in determining if we should break the lease. For example, if a job is terminated an infinite lease will stick on the blob. But if we can calculate how old is the lease, then we can determine whether to break it.
1 voteThank you for your feedback. Providing this functionality 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.
- Don't see your idea?