In scenarios of containers and databases deleted by mistake, customers will now spend less time performing restore. Earlier, restore action for deleted containers would result in the creation of another account and the customer had the responsibility to move the data from the restored account using spark, bulk API, or Azure Data Factory. This was cumbersome, error prone, and added the time and cost it takes to do the restore. With new In-Account restore capability, customers can do a quicker restore, thus providing better availability.
Learn More