Tables in Azure Storage are an example of this -- the delete is performed asynchronously by a background thread some time later (just garbage collection). The t

Tables in Azure Storage are an example of this -- the delete is performed asynchronously by a background thread some time later (just garbage collection). The table is not immediately deleted. I don't think you can force Azure to immediately delete it, but you could possibly raise a support ticket to ask them to delete it immediately. Have not tried this though. Part of the reason is performance, I would assume, since a large delete could be hard on the overall system, and could slow Azure down for you + other customers. Also because some customers accidentally delete critical resources sometimes. (Or forgot to copy down any important config options from the resource before deleting it. I have some experience with that mistake.)