we are getting limit error while creating the workspace in the databricks

Question

so basically there multiple subscription under same domain and those subscription are used by different users in a day if 70-80 user tries to create workspace only 3-4 students are able to create after that if we try w will get the error
"statusMessage": "{"status":"Failed","error":{"code":"ResourceOperationFailure","message":"The resource operation completed with terminal provisioning state 'Failed'.","details":[{"code":"RESOURCE_EXHAUSTED","message":"Limit reached for workspace creation. You've hit your daily limit for workspace creation. Please try again in 24 hours."}]}}",

 we are facing issues even if we delete the existing workspace and try to deploy

Answer 1

Hi @Niveditha Jain

In your scenario:

• Multiple subscriptions exist under the same organization/domain.
• Around 70-80 students/users attempt to create workspaces in a single day.
• Only the first few users (3-4 as observed) successfully create workspaces.
• Subsequent users receive the RESOURCE_EXHAUSTED error because the workspace creation quota has been consumed.

A few important points:

1. The limit is typically associated with workspace provisioning requests, not necessarily the number of existing workspaces. Failed or repeated creation attempts may also contribute to the quota consumption.
2. Waiting approximately 24 hours is consistent with the error text and the quota reset behavior reported for similar workspace creation limits.
3. If this is a training, classroom, lab, or student onboarding scenario where dozens of workspaces must be created daily, the usage pattern is likely exceeding the intended provisioning rate. You may need to:
   • Pre-create workspaces in advance.
   • Distribute creations across multiple days.
   • Open a support request with the service provider and ask whether the tenant/account can receive a quota increase or exemption for educational use.

Thanks.

Answer 2

we need to know whether there is any daily limit for this if there how to change that

Answer 3

Stop workspace creation attempts for 24 hours from the last failed attempt, then retry once; deleting existing workspaces does not bypass the daily creation throttle reported by the deployment service.

The exact RESOURCE_EXHAUSTED daily workspace-creation limit is not listed among the published Azure Databricks resource or API limits, so there is no documented self-service quota setting that can be increased in the portal. Published non-fixed Databricks limits can be raised through the Azure Databricks account team, but this specific daily creation limit is absent from that list.^1^

Immediate action

1. Pause all automated and student deployments for 24 hours.
   • Avoid repeated retries during that period.
   • After 24 hours, submit one test deployment from one affected subscription.
   • Use a new, unique workspace name and unique managed-resource-group name.
2. Do not delete more workspaces to address this error.
   • The message concerns the number of creation operations during a time window, not the number of workspaces currently present.
   • Your result after deletion confirms that deletion does not clear the current restriction.
3. Record the scope by testing only after the waiting period. For each affected deployment, retain:
   • Subscription ID
   • Tenant ID
   • Region
   • UTC deployment time
   • Deployment/correlation ID
   • Full RESOURCE_EXHAUSTED response
   • Number of successful and failed creations during the preceding 24 hours
   • Subscription offer/type
   Because the published limits page does not define this throttle, its scope—subscription, tenant, billing account, region, or another backend boundary—cannot be determined from public documentation. The fact that subscriptions share a domain does not by itself establish the scope.

If the error remains after 24 hours

Open an Azure support request for the backend workspace-creation restriction:

1. Azure portal → Help + support → Create a support request.
2. Select the affected subscription.
3. Choose Azure Databricks and the category for workspace deployment/creation. If the guided flow offers it, select Issues deploying a workspace.
4. Include the diagnostic information above and request:
   • Identification of the throttle’s scope.
   • Confirmation of the reset timestamp.
   • Review of failed or deleted workspace records that might require backend cleanup.
   • A limit increase or exemption for the instructor-led deployment volume, if available.

Do not select Azure Databricks Serverless quota unless the failure explicitly concerns DBUs/hour for serverless compute; that is a different quota.

Subscription prerequisites

Check these only for subscriptions that have not previously created a workspace successfully:

• Azure Databricks workspace creation requires a subscription that is not Free Trial. A free account must be converted to pay-as-you-go, have its spending limit removed, and have sufficient regional vCPU quota.^2^
• The deploying identity must have Owner, Contributor, or an equivalent custom role at subscription scope. The custom role must include the documented Databricks workspace, deployment, resource-group, and provider-registration actions.^2^

These prerequisites are secondary in this case: a permissions or provider-registration failure would not normally return the quoted, explicit daily limit reached message.

Recommended design for 70–80 students

Avoid creating and deleting one Azure Databricks workspace per student each day. Provision a smaller set of persistent workspaces in advance, add students as workspace users, and control their compute access with groups and cluster policies. Workspace administrators can assign users and groups and regulate cluster creation through cluster policies.^3^

This reduces workspace deployment operations and avoids relying on an unpublished daily creation threshold.

---

References

1. Resource limits
2. Create a workspace
3. Azure Databricks administration overview