Azure Databricks - Stopped App Auto Started & Consumed Resources without any User Trigger

Microsoft Support can investigate unexpected Azure Databricks charges and, where appropriate, apply credits or refunds. Billing support is free.

Because the portal flow can be confusing and sometimes loops without clearly offering a ticket option, follow these steps carefully to open a billing support request for this Databricks cost issue:

1. Open the support request creation page directly:
   • Go to: https://portal.azure.com/#create/Microsoft.Support
2. Start a billing case:
   • In the search box, type billing and select it.
   • Choose Billing as the support area and select Next.
3. Select the affected subscription:
   • From the subscription dropdown, select the subscription where the Databricks charges appeared.
   • Click Next.
4. Bypass the automated “solutions” and force creation of a ticket:
   • After a short delay, several options or “solutions” will appear.
   • Select the Create a support request button at the top.
   • Do not click any of the suggested solutions.
5. Fill in the case details:
   • Provide a clear summary such as: “Unexpected Azure Databricks charges – workspace auto-started after 6+ months dormant; request investigation and credit.”
   • Choose an appropriate Problem type and Problem subtype under Billing (for example, unexpected charges / cost dispute), even if not an exact match.
   • Click Next.
6. Complete Additional details:
   • After another short delay, some automated solutions may appear again.
   • Click Return to support request (upper-left) instead of selecting any solution.
   • Back on the support case form, click Next to go to Additional details.
   • Provide:
     • Subscription ID.
     • Time window of the unexpected Databricks usage (for example, January 2026).
     • Confirmation that the workspace/app had been dormant for ~6 months and that no user logged in or started clusters/jobs.
     • The total unexpected charge amount and that this was a demo environment.
   • Click Next to go to Review + create, then click Create.

After submission, an automated email is typically sent within a few minutes, and a billing engineer usually responds within one business day. They can:

• Verify the Databricks usage and associated Azure resources.
• Check whether serverless or other background Databricks features (for example, data quality monitoring, Predictive Optimization, materialized views, or other serverless jobs) generated the charges.
• Determine whether a one-time courtesy credit or refund is appropriate.

To avoid future surprises once this is resolved, consider:

• Using budgets and alerts in Databricks and Azure Cost Management to detect unexpected spend early.
• Using Databricks cost dashboards and billing system tables to identify which features (for example, serverless jobs, data quality monitoring, or other serverless-billed features) generated usage.

If the portal still does not allow creating a ticket after following the steps above, repeat step 1 in a different browser or in a private/incognito window and ensure the correct subscription is selected.

References:

• Understand the terms in your Azure usage and charges file
• Identify anomalies and unexpected changes in cost
• Troubleshoot MCA billing issues with usage file pivot tables
• How Azure Databricks pre-purchase discount is applied
• Best practices for cost optimization
• Monitor the cost of serverless compute
• Understand Databricks networking costs
• Reactivate a disabled Azure subscription
• I need help with bill waiver on my subscription but cannot open a support ticket. - Microsoft Q&A
• Azure Front Door / CDN still incurring charges even after deletion (post auto-migration) - Microsoft Q&A