> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks/getting-access.md).

# Getting access

The CARTO Analytics Toolbox for Databricks is installed in your Unity Catalog and works with SQL Warehouses.

{% hint style="success" %}
The CARTO Analytics Toolbox for Databricks is available for CARTO customers. [Contact us](mailto:support@carto.com) to get an installation package.
{% endhint %}

## Requirements

* [Unity Catalog](https://docs.databricks.com/en/data-governance/unity-catalog/index.html) enabled in your Databricks workspace
* A [SQL Warehouse](https://docs.databricks.com/en/compute/sql-warehouse/index.html) provisioned in your workspace
* Appropriate permissions to create functions in your catalog

{% hint style="warning" %}
**Check your Databricks region before you start**

All installation methods below rely on Databricks Unity Catalog HTTP connections (the mechanism behind `http_request()`) to reach the AT Gateway, which powers every Analytics Toolbox feature that calls out to CARTO's APIs: the Location Data Services (LDS) module (geocoding, isolines, routing), the import and export modules, and the creation of Builder maps from Databricks (used by CARTO Workflows). These connections are only available in Azure regions where Databricks Model Serving is supported — see the [Databricks region support tables](https://learn.microsoft.com/en-us/azure/databricks/resources/feature-region-support). If your workspace's region doesn't support Model Serving, none of these features can work regardless of how the Analytics Toolbox or AT Gateway is configured.
{% endhint %}

## Installation

There are different ways to install the Analytics Toolbox for Databricks:

* [**SQL Warehouse installation guide**](/data-and-analysis/analytics-toolbox-for-databricks/getting-access/sql-warehouse.md): This is the most standard and easy way to install the Analytics Toolbox. It provides step-by-step instructions for installing functions in your Unity Catalog.
* [**Installation in an Azure VNet**](/data-and-analysis/analytics-toolbox-for-databricks/getting-access/installation-in-an-azure-vnet.md): This option is only suitable for Self-Hosted deployments of the CARTO platform on Azure that need to access the Analytics Toolbox functions within a VNet using an AT Gateway deployed on Azure Container Apps.
* [**Installation on a private AKS**](/data-and-analysis/analytics-toolbox-for-databricks/getting-access/installation-on-private-aks.md): For Self-Hosted deployments on AKS where the AT Gateway must remain fully private. Connectivity from Databricks Serverless SQL Warehouses is established over Azure Private Link via a Databricks Network Connectivity Configuration (NCC).

{% hint style="info" %}
Looking for the legacy cluster-based installation? See the [Legacy documentation](/data-and-analysis/analytics-toolbox-for-databricks/getting-access/legacy.md) section.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks/getting-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.