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.
3,787 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,066 votesStatic websites is planned for the coming year! This feature will include more detailed error messages as well as support for a default Storage Blob. As soon as we have updates to share on Static Websites we will do so. 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,106 votesWe are pleased to announce that we have made an Azure Logic Apps template available to expire old blobs. To set up this automated solution in your environment: Create a new Logic Apps instance, select the “Delete old Azure blobs” template, customize and run. We will release a blog post detailing instructions and providing more templates in the coming weeks.
Allowing users to define expiration policies on blobs natively from storage is still planned for the coming year. As soon as we have progress to share, we will do so. We will continue to provide updates at least once per quarter.
For any further questions, or to discuss your specific scenario, send 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.
515 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.
292 votesThank you for you feedback. This work has been started. 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.
-
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.
105 votesThank you for your feedback. We are currently working on features that will provide this functionality and 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.
-
Virus scanning for Blob Storage
Need the ability for real-time virus scanning on blobs.
82 votesThank 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.
-
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…
49 votesThank 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.
-
Provide ability to limit the size of the payload being uploaded to a blob storage using a sas token
Currently there are only handful of limitations one can associate with a SAS token generated for Azure Storage Blob. Those are time period, access type, IP address filtering as well as protocol. It would be great to add a new option to limit the amount of data which can be uploaded to the storage.
44 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.
-
SAS tokens for blobs with restricted file types and maximum file size
When issuing a Shared Access Signature (SAS token) there should be(optional) parameters for maximum file size and restricted whitelisted file extensions so that clients can upload files only with any of the whitelisted extensions in token with not bigger than maximum size mentioned in SAS token.
38 votes -
Map multiple CNAME records to Blob Storage
At present it's possible to only map a single CNAME record to blob storage. It would be useful to map multiple CNAME records.
There is a work-around if you don't mind spending the extra money though: Create an Azure CDN for the storage and then map multiple CNAME records to the CDN instead.
30 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.
-
Please provide a function to view on Blob snapshot within the portal.
We want to check the status of Blob snapshot within the portal.
It will be very useful if we can check and manage it through the portal, because we use Blob snapshots for VM backup.----------
Japaneseポータル上で Blob のスナップショットの状態を確認したい。
VM のバックアップに Blob スナップショットを使用している為、
ポータルから確認したり、管理できるようになると良い。28 votesThank you for you feedback. This work has been started. 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.
-
Allow-Blob-Meta-Name with dash, as in Access-Control-Allow-Origin
Blob defined as CDN may need to send Access-Control-Allow-Origin header.
20 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.
-
Adding S3 APIs
Our store uses S3 API for virtual download storage. We'd like to give azure storage an oppotunity, event tested the following successfully:
Using s3cmd and other Amazon S3-compatible apps with Azure Blob Storage | Microsoft + Open Source
https://open.microsoft.com/2017/11/09/s3cmd-amazon-s3-compatible-apps-azure-storage/But Minio is not a native solution, does not having transfer acceleration functionality provided by S3, and may require constant updates. We really want Azure to support S3 API, or at least some API so that we can enable user's download which only valid for a limited time.
18 votesCurrently, you can use shared access signatures (SAS) to accomplish time-based expiry of access. See the following article for more details: https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1?toc=%2fazure%2fstorage%2fblobs%2ftoc.json. If there is another reason for which you’d like us to support exactly the S3 API, please send us an email at azurestoragefeedback@microsoft.com with details of your specific scenario.
-
Ability to backup blob storage with automatic retentions
Support snapshot or backup feature from Azure backup vault for blob storage including deduplication feature
16 votesThank you for your feedback. Blob storage soft delete will allow you to configure automatic snapshotting of blobs and allow you to specify retention periods for those snapshots. Soft delete will be configurable directly from the storage account. This feature is currently being worked on. For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
-
Improve case sensitivity options by providing optional auto to lowercase
Recently we attempted to migrate from windows file store to azure blob storage and ran into the problem of case sensitivity with azure blobs. We were migrating html based marketing assets which would be a nightmare to attempt to find all the URL's to assets and to lowercase them. Alternative we would need to write a small site that sits in front to lower case all requests. This would require us to first rename all blobs to ensure they are lowercased. In addition to this we would also need to write something that would upload a file to blob and…
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.
-
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!
12 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.
11 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.
- Don't see your idea?