An error occurred while saving the commentAnonymous commented
SSDT debugging is too buggy. Stepping *into* (F11) it skips right over tSQL code and steps into CLR code, with no way to get back into SQL code.
At least when SSMS supported debugging I could switch between the two depending on whether I needed to debug the TSQL or the CLR.
As it stands right now, there is no usable product that lets me debug SQL and CLR when they are both used in procedures.
Thanks for your feedback. We are working on a number of cost management features and we will include this in our plans.
Azure Billing Team
This is definitely on our list!
In the meantime, please create a budget which will trigger a script (e.g. Automation, Functions, or Logic Apps) via action groups to shutdown or delete resources based on your specific needs.