> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/activate/bi-tools/tableau-cloud.md).

# Tableau Cloud

This guide covers connecting Tableau Cloud to Data Products, publishing semantic models, and creating workbooks.

Connect Tableau Cloud to turn your dimensions and measures into charts, dashboards, and drill-downs - no SQL required.

Tableau Cloud connects to your semantic layer through the **MySQL wire protocol**. Since the MySQL endpoint is hosted on a private network, Tableau Cloud uses **Tableau Bridge** to securely access your semantic models.

Getting Tableau Bridge and network access set up is a one-time, platform-admin-adjacent task, heavier than the one-time [Tableau Desktop](https://v2.dataos.info/consume/activate/bi-tools/tableau.md) connection. If that setup isn't yours to do, loop in whoever administers Tableau Cloud and network access for your organization. Once it's done, publishing itself takes a few clicks from the Data Product page: no API calls required.

### Prerequisites

Set these up once before connecting Tableau Cloud to your semantic models.

<table><thead><tr><th width="229.4407958984375">Requirement</th><th>Detail</th></tr></thead><tbody><tr><td><strong>Enterprise Tableau Cloud</strong></td><td>An active Tableau Cloud subscription.</td></tr><tr><td><strong>Tableau Bridge</strong></td><td>Required to connect Tableau Cloud to the DataOS MySQL proxy running on a private network. <a href="https://www.tableau.com/support/releases/bridge">See more</a>.</td></tr><tr><td><strong>MySQL Connector/J</strong></td><td>Version <strong>9.2.0</strong> specifically. <a href="https://mvnrepository.com/artifact/com.mysql/mysql-connector-j/9.2.0">Download from Maven Repository</a>.</td></tr><tr><td><strong>DataOS username</strong></td><td>Your DataOS Id, found under <strong>Profile → Id</strong>.</td></tr><tr><td><strong>DataOS API token</strong></td><td>Generate from <strong>Profile → Tokens</strong>, or copy a token from <a href="https://v2.dataos.info/consume/get-started/before-you-begin.md">Before you begin</a>.</td></tr><tr><td><strong>Tableau Personal Access Token (PAT) or Username and Password.</strong></td><td>Required to publish semantic models to Tableau Cloud.</td></tr></tbody></table>

### Before you begin (one-time setup)

#### Install Tableau Bridge

Download and install [**Tableau Bridge**](https://www.tableau.com/support/releases/bridge) on a Windows or linux machine that has network access to your DataOS MySQL proxy.

Sign in using your Tableau Cloud account. After installation, ensure the Bridge status shows **Connected**.

#### Install the MySQL Connector/J driver

Tableau Bridge communicates with the DataOS MySQL proxy using the MySQL JDBC driver.

Download [**MySQL Connector/J 9.2.0**](https://mvnrepository.com/artifact/com.mysql/mysql-connector-j/9.2.0) and copy the JAR file to the Tableau Drivers directory **on the Bridge machine**.

**Windows**

```
C:\Program Files\Tableau\Drivers\
```

If the `Drivers` directory doesn't exist, create it.

Verify that the following file is available:

```
mysql-connector-j-9.2.0.jar
```

> **Important**
>
> The MySQL Connector/J JAR **must be present on the Bridge machine**. Tableau Bridge uses this driver to establish MySQL connections with the DataOS MySQL proxy.

> **Version 9.2.0 specifically.** Other versions may not be compatible with the MySQL wire protocol used by DataOS.

#### Configure Tableau Bridge in Tableau Cloud

Open Tableau Cloud.

Navigate to:

```
Settings
    └── Bridge
```

**Create a Bridge Pool**

1. Open **Pooling**.
2. Click **New Pool**.
3. Provide a pool name.
4. Assign the Bridge computer to this pool.

**Configure the Private Network Allowlist**

Navigate to:

```
Settings
    └── Bridge
         └── Private Network Allowlist
```

Click **Add New Domain**.

Enter your DataOS MySQL proxy domain.

Example:

```
tcp.intribeiks-071726.instance.dataos.cloud
```

Assign the domain to the Bridge Pool created in the previous step.

This allows Tableau Cloud to route all MySQL traffic through Tableau Bridge.

### Get a Tableau Personal Access Token (optional)

The publish form authenticates to Tableau Cloud using either your Tableau Cloud **username and password** or a **Personal Access Token (PAT)**. If you'll use your username and password, skip ahead to Publish the datasource section. To create a PAT instead:

1. Sign in to Tableau Cloud.
2. Click your **Profile** icon.
3. Select **My Account Settings**.
4. Scroll to **Personal Access Tokens**.
5. Click **Create Token**.
6. Enter a name.

Example:

```
sync-cloud
```

7. Click **Create Token**.
8. Copy the generated **Token Secret** immediately.

{% hint style="warning" %}
**Important**

Tableau displays the Token Secret only once. Store it securely. If it is lost, create a new Personal Access Token.
{% endhint %}

If you'd rather use your Tableau Cloud login directly, no separate setup step is needed: just have your username and password ready.

### 1. Publish the datasource

From the Data Product page, go to **Activate → BI Tools → Tableau Cloud** and open the setup guide. Under **Publish the datasource**, fill in the form:

<table><thead><tr><th width="199.639892578125">Field</th><th>Description</th></tr></thead><tbody><tr><td>Project name</td><td>Optional. The Tableau Cloud project to publish into.</td></tr><tr><td>Server name *</td><td>Your Tableau Cloud server URL, e.g. <code>https://10ax.online.tableau.com</code>.</td></tr><tr><td>Site id *</td><td>Your Tableau Cloud site name.</td></tr><tr><td>Username/Password or Personal Access Token</td><td>Choose how you authenticate to Tableau Cloud.</td></tr><tr><td>Username * / Password *</td><td>Required when Username/Password is selected.</td></tr><tr><td>Token name * / Personal access token *</td><td>Required when Personal Access Token is selected.</td></tr></tbody></table>

Click **Connect**. Publishing runs against Tableau Cloud in real time, you'll see it in progress, then a success or failure outcome. On success, the datasource is available in your Tableau Cloud site's **Explore** list. On failure, nothing is published, and the form shows the error Tableau Cloud returned so you know what to fix.

<details>

<summary>Automate it: publish via the Metadata Export API</summary>

For scripted or CI publishing, call the same endpoint directly instead of using the form.

Replace every `<...>` placeholder with your actual environment and credentials before running a command.

**Using a Personal Access Token**

```bash
curl --location 'https://<instance>.instance.dataos.cloud/vulcan/tenants/<tenant>/data-products/<data-product>/api/v1/metadata/exports/tableau/publish' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <DATAOS_API_TOKEN>' \
--data '{
  "server_address": "https://prod-apnortheast-a.online.tableau.com",
  "site_id": "moderndata",
  "token_name": "sync-cloud",
  "personal_access_token": "<TOKEN_SECRET>"
}'
```

**Windows PowerShell using a Personal Access Token**

Run this command as one physical line.

{% code overflow="wrap" %}

```powershell
curl.exe --location "https://<instance>.instance.dataos.cloud/vulcan/tenants/<tenant>/data-products/<data-product>/api/v1/metadata/exports/tableau/publish" --header "Content-Type: application/json" --header "Authorization: Bearer <DATAOS_API_TOKEN>" --data '{"server_address":"https://prod-apnortheast-a.online.tableau.com","site_id":"moderndata","token_name":"sync-cloud","personal_access_token":"<TOKEN_SECRET>"}'
```

{% endcode %}

**Using Username & Password**

```bash
curl --location 'https://<instance>.instance.dataos.cloud/vulcan/tenants/<tenant>/data-products/<data-product>/api/v1/metadata/exports/tableau/publish' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <DATAOS_API_TOKEN>' \
--data '{
  "server_address": "https://prod-apnortheast-a.online.tableau.com",
  "site_id": "moderndata",
  "username": "<TABLEAU_USERNAME>",
  "password": "<TABLEAU_PASSWORD>"
}'
```

**Windows PowerShell using Username & Password**

Run this command as one physical line.

{% code overflow="wrap" %}

```powershell
curl.exe --location "https://<instance>.instance.dataos.cloud/vulcan/tenants/<tenant>/data-products/<data-product>/api/v1/metadata/exports/tableau/publish" --header "Content-Type: application/json" --header "Authorization: Bearer <DATAOS_API_TOKEN>" --data '{"server_address":"https://prod-apnortheast-a.online.tableau.com","site_id":"moderndata","username":"<TABLEAU_USERNAME>","password":"<TABLEAU_PASSWORD>"}'
```

{% endcode %}

**Parameters**

<table><thead><tr><th width="216.5018310546875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><code>server_address</code></td><td>Tableau Cloud server URL</td></tr><tr><td><code>site_id</code></td><td>Tableau Cloud site name</td></tr><tr><td><code>token_name</code></td><td>Tableau Personal Access Token name (PAT auth only)</td></tr><tr><td><code>personal_access_token</code></td><td>Tableau Personal Access Token secret (PAT auth only)</td></tr><tr><td><code>username</code></td><td>Tableau Cloud username (username/password auth only)</td></tr><tr><td><code>password</code></td><td>Tableau Cloud password (username/password auth only)</td></tr></tbody></table>

**Successful response**

```json
{
  "server_address": "https://prod-apnortheast-a.online.tableau.com",
  "site_id": "moderndata",
  "project_name": "engineering-data-visualization",
  "datasource": "engineering-data-visualization",
  "id": "eefd3e7a-657b-4b00-a741-5d54551d007d",
  "status": "published"
}
```

</details>

### 2. Configure the connection

Once published, route the datasource through Tableau Bridge and confirm its live connection.

1. In Tableau Cloud, open **Explore** and open the published datasource.
2. Click **⋯ (More Options)** and select **Edit Connection**.
3. Configure the connection using your **DataOS credentials**:

<table><thead><tr><th width="199.639892578125">Field</th><th>Value</th></tr></thead><tbody><tr><td>Username</td><td>Your DataOS username (Id)</td></tr><tr><td>Password</td><td>Your <a href="https://v2.dataos.info/references/key-concepts/api-tokens">DataOS API Token</a></td></tr><tr><td>Network Type</td><td><strong>Private Network</strong></td></tr></tbody></table>

4. Click **Save**, then assign the datasource to the **Bridge Pool** you created earlier.

Your published datasource is now connected to DataOS through Tableau Bridge.

### 3. Build dashboards

1. Navigate to **Explore**.
2. Open the published datasource.
3. Click **New Workbook**.
4. Build your dashboards using the semantic models.
5. Publish the workbook to Tableau Cloud.

### You're connected

Your semantic models are now available as a Tableau Cloud data source. You can create dashboards, stories, and visualizations directly on top of the semantic layer without redefining joins, measures, or business logic.

### Limitations

* Publishing a **Workbook** or **Data Source** from Tableau Desktop is currently **not supported**.
* A data source published to Tableau Cloud cannot be connected back to Tableau Desktop.
* Semantic models are published through the Tableau Cloud setup guide on the Data Product page, or the DataOS Tableau Publish API.
* Tableau Bridge is required whenever the DataOS MySQL proxy is hosted on a private network.
* The **MySQL Connector/J 9.2.0** JAR must be installed on the Bridge machine.
* If the semantic model changes, republish the data source to reflect the latest schema.

### Troubleshooting

<table><thead><tr><th width="219.6405029296875">Symptom</th><th>Resolution</th></tr></thead><tbody><tr><td>Data source not published</td><td>Check the error shown in the publish form. If publishing via the API, verify the response returns <code>"status": "published"</code>.</td></tr><tr><td>Unable to connect</td><td>Ensure Tableau Bridge is online and assigned to the correct Bridge Pool.</td></tr><tr><td>Driver not found</td><td>Verify <code>mysql-connector-j-9.2.0.jar</code> exists under <code>C:\Program Files\Tableau\Drivers\</code> on the Bridge machine.</td></tr><tr><td>Connection timeout</td><td>Verify <code>tcp.&#x3C;instance>.instance.dataos.cloud</code> is added to the Private Network Allowlist and assigned to the Bridge Pool.</td></tr><tr><td>Authentication failed</td><td>Verify the DataOS username, DataOS API Token, Tableau PAT name, and PAT secret.</td></tr><tr><td>Personal Access Token missing</td><td>Ensure PATs are enabled for your Tableau Cloud site or contact your Tableau Site Administrator.</td></tr><tr><td>Cannot publish from Tableau Desktop</td><td>This is a current limitation. Publish semantic models using the Tableau Cloud setup guide on the Data Product page instead.</td></tr></tbody></table>

For data types, best practices, limitations, and governance, see the [Tableau Cloud](https://v2.dataos.info/references/interfaces/bi-tools/tableau-cloud) reference in References.


---

# 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://v2.dataos.info/consume/activate/bi-tools/tableau-cloud.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.
