You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The provider works with Azure CLI authentication to facilitate local development workflows, though for automated scenarios a service principal auth is necessary (and specification of azure_use_msi, azure_client_id, azure_client_secret and azure_tenant_id parameters).
Authenticating with Azure MSI
Since v0.3.8, it's possible to leverage Azure Managed Service Identity authentication, which is using the same environment variables as azurerm provider. Both SystemAssigned and UserAssigned identities work, as long as they have Contributor role on subscription level and created the workspace resource, or directly added to workspace through databricks_service_principal.
provider"databricks" {
host=data.azurerm_databricks_workspace.this.workspace_urlazure_workspace_resource_id=azurerm_databricks_workspace.this.id# ARM_USE_MSI environment variable is recommendedazure_use_msi=true
}
Authenticating with Azure CLI
It's possible to use Azure CLI authentication, where the provider would rely on access token cached by az login command so that local development scenarios are possible. Technically, the provider will call az account get-access-token each time before an access token is about to expire.
azure_workspace_resource_id - (optional) id attribute of azurerm_databricks_workspace resource. Combination of subscription id, resource group name, and workspace name. Required with auzre_use_msi or azure_client_secret.
azure_client_secret - (optional) This is the Azure Enterprise Application (Service principal) client secret. This service principal requires contributor access to your Azure Databricks deployment. Alternatively, you can provide this value as an environment variable ARM_CLIENT_SECRET.
azure_client_id - (optional) This is the Azure Enterprise Application (Service principal) client id. This service principal requires contributor access to your Azure Databricks deployment. Alternatively, you can provide this value as an environment variable ARM_CLIENT_ID.
azure_tenant_id - (optional) This is the Azure Active Directory Tenant id in which the Enterprise Application (Service Principal)
resides. Alternatively, you can provide this value as an environment variable ARM_TENANT_ID.
azure_environment - (optional) This is the Azure Environment which defaults to the public cloud. Other options are german, china and usgovernment. Alternatively, you can provide this value as an environment variable ARM_ENVIRONMENT.
azure_use_msi - (optional) Use Azure Managed Service Identity authentication. Alternatively, you can provide this value as an environment variable ARM_USE_MSI.
There are ARM_* environment variables provide a way to share authentication configuration using the databricks provider alongside the azurerm provider.
When a workspace is created using a service principal account, that service principal account is automatically added to the workspace as a member of the admins group. To add a new service principal account to an existing workspace, create a databricks_service_principal.
The text was updated successfully, but these errors were encountered:
Aiming at completeness of generated integration, please make sure to include also the Azure configuration options. here's the relevant documentation from upstream provider: https://registry.terraform.io/providers/databrickslabs/databricks/latest/docs#special-configurations-for-azure
Special configurations for Azure
The provider works with Azure CLI authentication to facilitate local development workflows, though for automated scenarios a service principal auth is necessary (and specification of
azure_use_msi
,azure_client_id
,azure_client_secret
andazure_tenant_id
parameters).Authenticating with Azure MSI
Since v0.3.8, it's possible to leverage Azure Managed Service Identity authentication, which is using the same environment variables as
azurerm
provider. BothSystemAssigned
andUserAssigned
identities work, as long as they haveContributor
role on subscription level and created the workspace resource, or directly added to workspace through databricks_service_principal.Authenticating with Azure CLI
It's possible to use Azure CLI authentication, where the provider would rely on access token cached by
az login
command so that local development scenarios are possible. Technically, the provider will callaz account get-access-token
each time before an access token is about to expire.Authenticating with Azure Service Principal
azure_workspace_resource_id
- (optional)id
attribute of azurerm_databricks_workspace resource. Combination of subscription id, resource group name, and workspace name. Required withauzre_use_msi
orazure_client_secret
.azure_client_secret
- (optional) This is the Azure Enterprise Application (Service principal) client secret. This service principal requires contributor access to your Azure Databricks deployment. Alternatively, you can provide this value as an environment variableARM_CLIENT_SECRET
.azure_client_id
- (optional) This is the Azure Enterprise Application (Service principal) client id. This service principal requires contributor access to your Azure Databricks deployment. Alternatively, you can provide this value as an environment variableARM_CLIENT_ID
.azure_tenant_id
- (optional) This is the Azure Active Directory Tenant id in which the Enterprise Application (Service Principal)resides. Alternatively, you can provide this value as an environment variable
ARM_TENANT_ID
.azure_environment
- (optional) This is the Azure Environment which defaults to thepublic
cloud. Other options aregerman
,china
andusgovernment
. Alternatively, you can provide this value as an environment variableARM_ENVIRONMENT
.azure_use_msi
- (optional) Use Azure Managed Service Identity authentication. Alternatively, you can provide this value as an environment variableARM_USE_MSI
.There are
ARM_*
environment variables provide a way to share authentication configuration using thedatabricks
provider alongside theazurerm
provider.When a workspace is created using a service principal account, that service principal account is automatically added to the workspace as a member of the admins group. To add a new service principal account to an existing workspace, create a databricks_service_principal.
The text was updated successfully, but these errors were encountered: