Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article is an overview of your options for creating and managing workspaces.
What is a workspace?
A workspace is a Azure Databricks deployment in a cloud service account. It provides a unified environment for working with Azure Databricks assets for a specified set of users.
Workspace creation options
There are multiple ways to deploy an Azure Databricks workspace. The standard deployment method is through the Azure Portal or Terraform.
Additionally, you can create workspaces using the following tools:
- Deploy a workspace with the Azure CLI
- Deploy a workspace with PowerShell
- Deploy a workspace with an ARM template
- Deploy a workspace with Bicep
Requirements
Before you create an Azure Databricks workspace, you must have an Azure subscription that isn't a Free Trial Subscription.
If you have a free account, complete the following steps:
- Go to your profile and change your subscription to pay-as-you-go. See Azure free account.
- Remove the spending limit.
- Request a quota increase for vCPUs in your region.
Required Azure permissions
To create a Azure Databricks workspace, you must be the one of the following:
A user with the Azure Contributor or Owner role at the subscription level.
A user with a custom role definition that has the following list of permissions:
Microsoft.Databricks/workspaces/*
Microsoft.Resources/subscriptions/resourceGroups/read
Microsoft.Resources/subscriptions/resourceGroups/write
Microsoft.Databricks/accessConnectors/*
Microsoft.Compute/register/action
Microsoft.ManagedIdentity/register/action
Microsoft.Storage/register/action
Microsoft.Network/register/action
Microsoft.Resources/deployments/validate/action
Microsoft.Resources/deployments/write
Microsoft.Resources/deployments/read
Note
The Microsoft.Compute/register/action
, Microsoft.ManagedIdentity/register/action
, Microsoft.Storage/register/action
, Microsoft.Network/register/action
permissions are not required if these providers are already registered in the subscription. See Register resource provider.
:::