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,934 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,280 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,334 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.
1,028 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 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.
635 votes -
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.
331 votesWe will take a look. This is an interesting idea!
-
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.
314 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.
-
Azure Policy For Preventing Public Blob Containers
There are no ARM REST API properties for Blob containers which means we can't create an Azure Policy for not allowing people to ever create public blob containers.
This is how every AWS breach has occurred due to accidentally setting storage to public.
301 votesThe feedback is well received. Azure Storage team is working on the feature for this scenario. It’s estimated to ship in H1 2020.
-
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.
294 votesRight now, we don’t plan to add this support but up-vote this and we could consider.
-
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.
177 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.
-
Virus scanning for Blob Storage
Need the ability for real-time virus scanning on blobs.
124 votesThank you for your feedback. This functionality is offered by security partners. Symantec has released the support on Azure Blob Storage. Please refer to the partner website for detailed information.
-
Enable life cycle management for append blob
Currently life cycle management is only supported for block blob. We are using Azure SQL DB auditing feature and this is creating huge amount of blob files.But these are of append blob type and that is not supported by life cycle management. Please provide support for append blob so that we can manage these log files properly.
106 votes -
Enable Authorization to the Azure Static Websites using Azure Active Directory
Right now, there is development done to use Blob storage for a static website (known as Azure Static Websites). The feature is in preview.
However, the downside of this is that the website is public. There is no built-in to restrict the access to the website.
In my use case, I would have used Azure Static Websites to store the static documentation produced by DocFx (https://dotnet.github.io/docfx/). This documentation includes the classes as well including technical documentation and wikis.
I would be great if I could use my Azure Active Directory to control who can actually see the pages…
86 votes -
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…
72 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.
-
Permanent deletion of soft-deleted blobs (GDPR)
We considered using the new Azure Blob Storage - Soft Delete feature - as a backup solution and safety precaution for accidental blob deletions caused by potential code bugs in our (multitenant) application.
We would like to set the retention as high as possible from a safety perspective, but need to set it as low as possible from a GDPR compliance perspective; since we need to remove all PII for resigning customers - this also include soft deleted blobs.
Since there seem to be no way to permanently delete soft deleted blobs (before they are automatically removed by the retention…
53 votes -
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.
49 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.
-
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.
46 votesThe feedback is well received. Azure Storage team is working on the feature for this scenario. It’s estimated to ship in CY2019.
-
Delete multiple containers at once Azure Storage Explorer
Currently, you can only delete one container at a time from Azure Storage Explorer. Being able to delete more than one would be very valuable when handling storage management.
41 votes -
Include Azure SQL as a "trusted Micorsoft service to access the Storage Account"
We're restricting access to our Storage Accounts by configuring the Firewall & Virtual networks.
However, one of these storage accounts must also be accessible to our Azure SQL db's. This is currently not supported.Rather than securing the Storage Account, it has been proposed to restrict access from the Azure SQL side, BUT, that configuration currently only works if some other features (external tables) aren't used. We've now come full circle :)
Ideally, we'd like to see that we can secure the Storage Account - and include Azure SQL as a trusted service.
40 votes -
http/2 storage blob
Hello, Is there an approximate date for HTTP / 2 to be enabled in Azure Blob Storage?
A few months ago I read it was in your backlog, but I do not know if that reqeuerimiento is still waiting.
38 votes
- Don't see your idea?