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.
Thank 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 firstname.lastname@example.org.
Christian Wuerdig commented
This has been under review for 3 years now - is there any update on this? Being able to automatically change storage tiers based on last read access would be very useful. I would assume most data in blob storage is write-once-read-many so archiving based on last modification date is not all that useful (well at least not for us)