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.
Our 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 firstname.lastname@example.org.
"Rename" feature in the later versions of Azure Storage Explorer was also replaced with "Clone with new name" feature!!
I don't get it!
We'd love to hear the reasoning behind this, as I assume there is one. Right?
Jason Smedley commented
Please provide this feature. I know at the base level copy and paste is the same, but lets build something for everyone. User empathy time please.
Ezra Epstein commented
This is part of Microsoft's cloud business "strategy." Like all things MS they give two sh.... about quality, they optimize for revenue and bragging rights. Copying data costs money... which means more revenue for Microsoft. As utterly dumb as that is, that's the way they make their business decisions. It is quite literally the antithesis of Amazon's customer-centric approach. Other than folks being conned into using their platform, Microsoft's cloud would be out of business.
Same with their VMs. It's a pattern. Most things on Azure require a custom VM, which adds to not only their ability to fleece folks for money (don't get me started on the cost of a software firewall - a built-in feature of both AWS and Google Cloud), all these extra VMs let MS brag that they are #2 in the cloud. Well, sure, when all your customers have to spin up 10x the number of machines as on a cloud like Googles, it is not a surprise.
Yuttakonkit, Yuttakon [Accenture] commented
Still waiting, for this feature with notice that you already have a renaming feature in Azure Storage Explorer.
This is where we would be hoping for a .Rename method.
You guys still need to write an in-place rename method (iislog.csv --> iislog.csv.processed). You already know this, but just figured I would remind you. It's clearly more complicated on the backend than we understand, which probably explains why you push the processing (copy/delete) down to us.
And btw... Microsoft.Azure.Storage.File.CloudFile doesn't have a rename method either.
But using files doesn't work for me because you don't have File event triggers in Data Factories. The only event I can develop against is Blob events (create and delete).
Plus... most network administrators in most companies these days love to run around blocking SMB ports with their firewalls, so Microsoft.Azure.Storage. API (talking to the webservices on the back end) is the only option available to me.
copy/remove is okay in quite a few scenario's, but in combination with Media Services it's not viable
Muthusamy A commented
6 years and still there isn't solution for this. I meant, "SOLUTION", not a workaround.
Jeff Walter (jwalter1) commented
It's utterly ridiculous that you guys would put out such a poorly designed feature. Shame on you.
Blob functionality is very weak compared to S3. Missing this kind of functionality is akin to selling someone a car without A/C.
Andy Norris commented
Me, too. Wow. Please.
This would be very useful indeed.
reem dawg commented
is it possible to rename an Azure File Share? How?
Any update from MS?
Eddie Kumar commented
My automation solution overwrites the older files (on nightly basis), we needed to change few files names, this lack of Rename functionality is unfortunate as if I were to rename the file-name at source the automation process will not overwrite the file in Azure File storage (it will duplicate it) which will propagate and affect the further systems where files are transferred (by the automation), this means I will need to change the automation code. Therefore, I'd highly recommend for the Rename feature to be included asap please.
It's definitely bad experience that even we want to swap the folder to .backup but we cannot do it easily.
This is a huge blocker for us and we're likely going to move to another platform because of it. Our organization has 300 TB+ of data in azure blob storage and not being able to perform such a basic file operation makes using this service extremely painful.
Christopher Warrington (CHRISTOPHER) commented
I would like to be able to rename blobs so I can have them in a different namespace while they are being created/uploaded to. Then, after they are finalized, they can be renamed to their "published" location. Couple this with per-blob expiration and implement atomic rename-and-reset-TTL, then blob upload error recovery becomes trivial: start uploading to a temporary blob with a short TTL, when done, rename-and-reset-TTL to the final name. If anything goes wrong, the partial blob will just go away automatically.
+1, this limitation is slowing down my deployment pipeline. Please add this.
Martin Brandl commented
Until we get a clean solution that don't require to copy and delete a file, You can use my convenience cmdlet: Rename-AzureStorageBlob: