An Apache Spark-based analytics platform optimized for Azure.
Hello @Arvind Kumar
Deleting the Resource Groups does not necessarily stop all charges immediately, especially with services such as Azure Databricks.
A few things I would check before assuming the deleted Resource Groups are still running:
In Cost Analysis, change the date range to include the days before and after deletion and group the costs by Resource and Resource group. This helps identify exactly which resource is generating the charge.
Check the meter/service name for the new charges. If they are still Databricks-related, look at the Databricks workspace and its associated resources.
Azure Cost Management data is not always real-time. There can be a billing/usage reporting delay, so charges appearing today may relate to usage that occurred before the Resource Group was deleted.
Also check for resources that aren't obvious from the Resource Group view, such as managed resources, disks, snapshots, public IPs, or other subscription-level resources.
If the Resource Group name shown in Cost Analysis is from several days ago and there are no current resources, I would first compare the usage date vs. billing date before deleting anything else.
The most useful clue is the actual Service name + Resource + Usage date behind one of the recent charges. If those charges continue for several days with usage dates after the Resource Group deletion, then I'd raise a Microsoft billing/support request with that information.
If you can share a screenshot of the Cost Analysis breakdown showing the Service/Resource and dates (hide subscription ID or other sensitive information), it would be much easier to tell whether this is simply delayed billing data or an active resource still generating cost.