BAD_REQUEST: Account per user limit exceeded, each user is only allowed to join 60 accounts

Cameron Joyner 0 Reputation points
2025-05-12T20:57:26.8466667+00:00

When trying to create a new Databricks instance from my Azure account I am shown this error:

{
  "code": "BadRequest",
  "message": "BAD_REQUEST: Account per user limit exceeded, each user is only allowed to join 60 accounts"
}

I am however certain that I belong to no more than three instances of Databricks. I was trying to execute a CREATE provisioning operation. Every time I attempt to use Copilot assist it fails to retrieve anything. Please help me understand what could be causing this.

Azure Databricks
Azure Databricks
An Apache Spark-based analytics platform optimized for Azure.
2,527 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Chandra Boorla 14,665 Reputation points Microsoft External Staff Moderator
    2025-05-12T21:14:17.1966667+00:00

    @Cameron Joyner

    The error you encountered "code": "BadRequest", "message": "BAD_REQUEST: Account per user limit exceeded, each user is only allowed to join 60 accounts" indicates that your Azure account has exceeded the maximum limit of 60 Databricks accounts for a single user. Even though you mentioned being part of only three instances, this limit can be affected by several factors:

    Possible Causes:

    1. Inactive or Orphaned Accounts - You may have been part of other Databricks accounts in the past, which are still active.
    2. Pending Invitations - Even accounts you were invited to (but did not accept) may count toward the limit.
    3. Multiple Workspaces - A single Databricks account can have multiple workspaces, each counting towards the limit.
    4. External User Configuration - If your user was set as an external user (guest user) in Azure Active Directory (AAD), this may have caused the issue.

    How to Resolve:

    1. External user to Internal user - This issue can be resolved by converting your Azure AD user type from an external user (guest) to an internal user.
    2. Review Your Account Memberships - Check all your active Databricks accounts in each Azure AD tenant you are part of.
    3. Remove Unnecessary Accounts - Work with the administrators of those accounts to remove your membership where not needed.

    For additional information, please refer: Convert external users to internal users (Preview)

    Please refer to the similar thread on the Microsoft Q&A forum that discusses the same issue: https://learn.microsoft.com/en-us/answers/questions/1922324/databricks-workspace-deployment-failed-with-badreq

    I hope this information helps. Please do let us know if you have any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    Thank you.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.