Update: We are currently working on enabling operational backup for blobs and the ETA for the limited preview is November ’20.
Do check out this short demo to catch a glimpse of what operational backup of blobs will offer: https://aka.ms/AB-BlobBackup
For more details, please reach out to us at AskAzureBackupTeam@microsoft.com
We haven’t forgotten about this request! This is something we would like to bring in the future, but we cannot provide a timeline at this time.
Thank you for using UserVoice!
Thanks for the feedback! We are working on enabling this feature.
An error occurred while saving the commentPiers Lawson commented
Our current deployment process "promotes" a build of a website through TEST, UAT, PRE-PROD and eventually to PROD. Deployment slots seem an ideal way to provide a similar process... however, despite all the benefits of using the Swap functionality, the downside is that after a Swap, our old code would end up making its way back down that chain. After a few releases, TEST would be running what had been the PROD code several releases earlier.
Since other web sites also have TEST, UAT, PRE-PROD sites as well, which would link to other sites in the corresponding deployment slots, we could end up with one TEST site running the next release of its code linking to another web site running a very old release of its software.
So a button to copy the code running in one slot to another slot rather than using a Swap would be very useful. We'd then just have to decide if we would use the copy all the time instead of swap, OR use swap to promote followed by a copy backwards when we're happy OR use copy all the time except for a swap between PRE-PROD and PROD so we can rollback in PROD but don't have to worry about keeping most of the other environments in sync.
Or is there a better way to do this? Perhaps using Deploy tasks for TEST, UAT and PRE-PROD then a Swap for PRE-PROD to PROD?