MetricSign
EN|NLRequest Access
High severityresource

Power BI Refresh Error:
QUOTA_EXCEEDED

What does this error mean?

A Databricks operation was blocked because the workspace or the underlying cloud subscription has exhausted a resource quota, such as vCPU count, IP addresses, or job run rate.

Common causes

  • 1The Azure subscription or AWS account has reached the vCPU quota for the selected VM family or region
  • 2The Databricks workspace has hit the 1000 job runs per hour API rate limit
  • 3The number of active clusters exceeds the workspace-level cluster policy limit
  • 4Public IP address quota in the cloud account has been exhausted

How to fix it

  1. 1Step 1: Identify which quota is exceeded from the error message (vCPU, IP, job rate, cluster count).
  2. 2Step 2: For cloud vCPU quotas: request an increase via the Azure portal (Subscriptions > Usage + quotas) or AWS Service Quotas.
  3. 3Step 3: For Databricks job rate limits: stagger job schedules or batch concurrent runs to stay under 1000 runs/hour.
  4. 4Step 4: Terminate idle clusters to free up vCPU and IP allocations.
  5. 5Step 5: Review cluster policies to enforce auto-termination and prevent quota creep from long-idle clusters.

Frequently asked questions

How quickly are Azure vCPU quota increases approved?

Azure quota increases for standard VM families are often auto-approved within minutes via the portal. Spot vCPU quota increases may require manual review and can take up to 2 business days.

Can I avoid quota issues with Databricks Serverless?

Databricks Serverless compute manages capacity on Databricks' own infrastructure, so cloud vCPU quotas in your subscription do not apply. However, Serverless is only available for specific workload types and regions.

Other resource errors