ADB WS error

Biswajit Mohapatra 0 Reputation points
2025-12-03T22:14:14.42+00:00

Not able to create a Workspace .

error :-The workspace 'adb2' is in a failed state and cannot be launched. Please review error details in the activity log tab and retry your operation.

Status

Failed

Resource group

db-training-001

Location

West Europe

Subscription

Azure subscription 1

Subscription ID

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Workspace type

Serverless

Pricing Tier

Premium (+ Role-based access controls)

Tags(edit)

Add tags

Am 1st time user and got this error while lunching a workspace

Azure Databricks
Azure Databricks
An Apache Spark-based analytics platform optimized for Azure.
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-12-03T22:14:26.0666667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It appears that your Azure Databricks workspace creation has failed, and the error message indicates that the workspace is in a failed state. Here are some steps you can take to troubleshoot and resolve this issue:

    1. Check Activity Log: Review the error details in the Activity Log tab of the Azure portal. This log will provide specific information about why the workspace failed to launch.
    2. Delete Failed Workspace: If the workspace is in a failed state, you will need to delete it. When you delete the failed workspace, the managed resource group and any successfully deployed resources will also be deleted. After deletion, you can attempt to create a new workspace.
    3. Verify Resource Group and Location: Ensure that the resource group (db-training-001) and the location (West Europe) you are using are correctly set up and available for creating Azure Databricks workspaces.
    4. Check Subscription Limits: Make sure that your Azure subscription has not hit any limits on the number of resources that can be created.
    5. Workspace Type and Pricing Tier: Since you are trying to create a serverless workspace with a premium pricing tier, ensure that this configuration is supported in your selected region.

    If you continue to experience issues, consider reaching out to Azure support for further assistance.


    References:

    0 comments No comments

  2. VRISHABHANATH PATIL 1,820 Reputation points Microsoft External Staff Moderator
    2025-12-04T01:00:06.3133333+00:00

    Hi @Biswajit Mohapatra

    Thank you for contacting Microsoft QA.

    It looks like you're facing an issue with creating a Databricks Workspace because it’s in a failed state. Here are some steps you can consider troubleshooting and hopefully resolve the problem:

    Check the Activity Log: Go to the Azure portal, navigate to your resource group (db-training-001), and check the activity log for your workspace (adb2). This log should provide specific error details that can pinpoint what's causing the failure.

    Permissions and Roles: Since you're using a Serverless Workspace with Premium tier, ensure that the service principal or user account you are using has the necessary permissions. Specifically, assign the Storage Blob Data Contributor role on the Azure Data Lake Storage account that your workspace is trying to access. You can refer to the article on granting service principal access.

    Resource Conflicts: Sometimes, the workspace creation fails due to resource conflicts or limitations in your subscription. Please check for any existing resources that might be causing conflicts and ensure that you're not exceeding your subscription limits.

    Private Endpoint and Network Configuration: If your workspace is trying to connect to a storage account using a private endpoint, ensure that the virtual network is correctly configured and that the VNet peering is established between Azure Databricks and the storage account virtual network, as outlined in the article regarding network configurations.

    Retry Creating Workspace: Once you have checked the above, you can try to create the workspace again after resolving any issues you have found.

    If the problem persists, I’d recommend reaching out to Azure support for a more in-depth investigation.

    Follow-Up Questions:

    • Have you checked the activity log for any specific error messages related to the workspace creation?
    • Can you confirm if the necessary permissions are granted to the service principal or user account?
    • Are you attempting to connect the workspace to any private endpoints or specific Azure Data Lake Storage accounts?
    • Have you exceeded any resource limits in your Azure subscription?

    Hope this helps you get your workspace up and running! Let me know if you have any further questions.

    0 comments No comments

Your answer

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