Use dependency ordering when deleting multiple resources
When deleting multiple resources, ensure that deletions are done in the proper dependency ordering such that one doesn't get errors during the deletion process.
Further recommendation would be to track user-created objects and allow them to be deleted directly. If I create a single higher level object (e.g. CloudFoundry instance), it will create dozens of underlying Azure objects. I don't have an option to delete the original object, instead I need to delete the base objects in the proper dependency order. Furthermore, I may unintentionally delete an unconnected object (e.g. a diagnostic storage account) used by unrelated objects.