After deleting the resource group which has azure sql resource and cancelled the subscription still iam incurring cost for database why it so?

Question

After deleting the resource group which has azure sql resource and cancelled the subscription still iam incurring cost for database why it so?

Answer 1

If you are still incurring costs for an Azure SQL Database after deleting the resource group containing it and canceling the subscription, you my want to check the following:

1. Subscription Cancellation Timing: When you cancel an Azure subscription, it doesn't immediately stop all billing. Azure subscriptions typically go through a "disabled" state before being fully deprovisioned. During this period, some resources might still incur charges until the subscription is fully deactivated.
2. Resource Not Fully Deleted: Sometimes, resources like Azure SQL Databases might not be fully deleted if there were dependencies or issues during deletion. Verify in the Azure portal or via CLI/PowerShell that the SQL database and all related resources are indeed deleted.
3. Other Linked Resources or Services: There might be other resources or services linked to the SQL database or the subscription that are still active and incurring costs.
4. Billing Lag: Azure billing can have a delay. Charges might appear after the fact for usage that occurred before deletion or cancellation.
5. Multiple Sub or Accounts: Ensure that the charges are not coming from another subscription or account linked to your billing.
6. Support or Reserved Instances: If you had any reserved capacity or support plans, those might continue to incur charges even after resource deletion.

I hope you find this helpful ♠

Answer 2

Hello MSharif It sounds like you deleted your resource group (with the SQL server and DB) and even cancelled the subscription, but you’re still seeing charges. That can happen for a few reasons:

1. Final billing cycle
   • When you cancel a subscription, Azure waits up to 72 hours to close out your billing cycle. You’ll still be billed for any usage that occurred before the cycle closed (this shows up on your “final bill”).
   • You might see those charges a few days after cancellation.
2. Backup and retention storage
   • Azure temporarily preserves your database backups in case you reactivate the subscription. You aren’t billed for that retained data, but any backup storage consumed before deletion does show up on the last invoice.
3. Support plan or recurring services
   • If you had an Azure support plan, it isn’t prorated when you cancel—it runs through the end of that billing month.
   • Any recurring Marketplace purchases (licenses, third-party add-ons) will auto-renew unless you turn off auto-renewal under Cost Management + Billing → Recurring charges.
4. Orphaned resources
   • Make sure there aren’t any leftover resources (like managed instances, elastic pools, or firewall rules) still sitting outside that deleted RG.

Here’s what you can do next:

Step 1: Review your actual charges

• In the portal go to Cost Management + Billing > Cost analysis

• Filter by your subscription, then by service (SQL Database) or by “Charge type” to see what exactly drove the costs

Step 2: Validate that everything’s gone

• Go to All resources and confirm there are no SQL-related items (servers, elastic pools, failover groups) left behind

Step 3: Check for support/marketplace renewals

• In Cost Management + Billing > Recurring charges, turn off auto-renewal for any support plan or marketplace purchase

Step 4: Request a refund if needed

• If you’ve confirmed there’s no active resource but still have unexplained charges, click Request a refund in the Azure portal to see if you qualify for an expedited refund.

Hope that helps! If you need more info, please let us know. thanks

Reference docs

• What happens after subscription cancellation?
• Review usage in Cost analysis
• Cancel a support plan / turn off auto-renewal