Keep Data Fresh

After you publish workbooks and data sources to Tableau Cloud, you can decide how you want to keep the data current. Options for keeping published data fresh depend on the characteristics of your data sources.

Data freshness options by data source

The following table lists data freshness options (and exceptions) that are available depending on the data source.

Exceptions

  • Tableau Cloud does not support connections to any cube-based data source.

  • Tableau Cloud does not support published connections that use Kerberos authentication.

  • Although you can publish extracts of SAP BW data to Tableau Cloud, refreshes are not supported. The best way to update SAP BW data sources is to republish them.

Options

SourcePublish optionsFreshness optionsAuthentication
On-premises data (accessible only from a private network)

File-based data

(Excel, .csv, .txt)

Extract only

Use Tableau Bridge (recommended)

Manual refresh from Tableau Desktop

Automated command-line scripts

n/a

Statistical file

(SAS (*.sas7bdat))

Extract only

Use Tableau Bridge (recommended)

Manual refresh from Tableau Desktop

Automated command-line scripts

n/a

Data hosted on a cloud platform

(For example, Oracle on Amazon RDS)

Live connection or extract, depending on database

Use Tableau Bridge (recommended)

Manual refresh from Tableau Desktop

Automated command-line scripts

Embedded credentials in Tableau Bridge settings

Relational database 

(Relational databases that Tableau Desktop connects to. For example, SQL Server, Oracle, IBM DB2)

Live connection or extract, depending on database

Use Tableau Bridge (recommended)

Manual refresh from Tableau Desktop

Automated command-line scripts

Embedded credentials in Tableau Bridge settings

Cloud data (accessible from the public internet)

Data hosted on cloud platforms

(See the list of supported platforms in
Allow Live Connections to Data Hosted on a Cloud Platform

Live connection or extract

Extracts:

Schedule directly on Tableau Cloud

Embedded credentials + IP safe list

Edit Connections on Tableau Cloud

Salesforce, Google Analytics

Extract only

Schedule directly on Tableau Cloud

Refresh Data Using Saved Credentials

OAuth Connections

Google BigQuery,

Google Sheets

Live connection or extract

Extracts:

Schedule directly on Tableau Cloud

Refresh Data Using Saved Credentials

OAuth Connections

Cloud (Box, Dropbox, OneDrive, Google Drive) file-based data

(Excel, .csv, .txt, .tab, .tsv, .json)

Live connection or extract

Extracts:

Schedule directly on Tableau Cloud

Refresh Data Using Saved Credentials

OAuth Connections

Anaplan

Oracle Eloqua

ServiceNow ITSM

Extract only

Schedule directly on Tableau Cloud

Refresh Data Using Saved Credentials

Embedded credentials

Edit Connections on Tableau Cloud

Marketo

 

Extract only

Schedule directly on Tableau Cloud

Embedded credentials

Web Data Connectors

Extract only

For basic user name and password credentials, use Tableau Bridge.

For custom (non-basic) username and password credentials, use the Tableau Desktop Refresh From Source command, or run a manual refresh from Tableau Desktop. For more information, see the WDC Authentication(Link opens in a new window) topic in the Tableau Web Data Connector API Help.

Tableau Bridge: Embedded credentials

Other: n/a

Tableau Cloud IP addresses for data provider authorisation

As a security measure, cloud data providers might require you to supply authorised IP addresses from which external applications request access to your data. A request from an IP address that is not explicitly approved could be rejected. To make sure live connections you publish to Tableau Cloud remain uninterrupted, add Tableau Cloud to your data provider’s allowlist.

The table lists IP address ranges that Tableau Cloud uses, depending on your site location. You can see its location in the URL that appears after you sign in to Tableau Cloud.

IP addresses are dedicated to and controlled by Salesforce.

Note: In addition to enabling communication over the Tableau Cloud IP range, you might need to enable access over the appropriate database port (for example, 80 or 443) depending on the communication type (HTTP or HTTPS).

Important: From August to December 2024, Tableau Cloud sites will be migrating to Salesforce's Hyperforce(Link opens in a new window), one pod at a time. Because Hyperforce uses different IP addresses, the migration to Hyperforce will require you to update your data provider’s allowlist. Going forward, IP addresses will need to be updated periodically. For more information, see the New IP addresses (after Hyperforce migration) section below.

For more information about Tableau Cloud's migration to Hyperforce, including when your pod will be moving, see the Tableau Cloud Migration to Hyperforce(Link opens in a new window) knowledge article.

New IP addresses (after Hyperforce migration)

From August to December 2024, Tableau Cloud sites will be migrating to Salesforce's Hyperforce(Link opens in a new window) by pod. After your pod’s migration to Hyperforce, your data provider’s allowlist will need to be updated to use Hyperforce IP addresses.

IP address process change

Hyperforce IP addresses are updated periodically and will require your data provider's allowlist to be updated. To stay informed about new IP addresses, you have one or both options:

  1. Periodically review the IP address tables below: At least 30 days before the IP addresses are enabled, the IP address tables below are updated. Site admins will also receive an email notification alerting them of the new IP addresses.

  2. Automate IP address updates using the JSON text file: Salesforce recommends that your data provider’s allowlist mirror the https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window) text file at all times by automating the IP address updates. New IP addresses are posted to the text file at least 30 days before they’re enabled and are denoted by the “Created Date” (in UTC).

    In the text file, the IP address and range for your pod are listed by the Hyperforce region that your pod resides in. To determine the Hyperforce region that your pod resides in, refer to the "Pod Name" and the associated "Hyperforce Region Name" in the tables below. For example, if your pod name is "prod-ca-a", your Hyperforce region name is "ca-central-1". In https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window) text file, search for "ca-central-1" for the appropriate IP addresses to include in your data provider's allowlist.

Pods migrated to Hyperforce

Pod Name (Host Name)LocationHyperforce Region NameInitial IP Address and Range after Hyperforce Migration
prod-ca-a

(prod-ca-a.online.tableau.com)

Canada - Quebecca-central-1155.226.152.0/23

(Alternatively, search for "ca-central-1" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

prod-uk-a

(prod-uk-a.online.tableau.com)

Europe - UKeu-west-2145.224.200.0/23

(Alternatively, search for "eu-west-2" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

useast-1

(us-east-1.online.tableau.com)

US East - Virginiaus-east-1155.226.144.0/22

(Alternatively, search for "us-east-1" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

10AY

(10ay.online.tableau.com)

US West - Oregonus-west-2155.226.128.0/21

(Alternatively, search for "us-west-2" region inhttps://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

DUB01

(dub01.online.tableau.com)

Europe – Germany (formerly Europe – Ireland)eu-central-1145.224.208.0/23

(Alternatively, search for "eu-central-1" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

Pods not migrated to Hyperforce

LocationPod Name (Host Name)Hyperforce Region NameInitial IP Address and Range after Hyperforce Migration
US East - Virginiaprod-useast-bus-east-1155.226.144.0/22

(Alternatively, search for "us-east-1" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

US West - OregonUW2Bus-west-2155.226.128.0/21

(Alternatively, search for "us-west-2" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

Asia Pacific – Australiaprod-apsoutheast-aap-southeast-2141.163.192.0/23

(Alternatively, search for "ap-southeast-2" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

US East - Virginiaprod-useast-aus-east-1155.226.144.0/22

(Alternatively, search for "us-east-1" region inhttps://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

Europe - IrelandEW1Aeu-central-1145.224.208.0/23

(Alternatively, search for "eu-central-1" region inhttps://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

Asia Pacific - Japanprod-apnortheast-aap-northeast-1141.163.208.0/23

(Alternatively, search for "ap-northeast-1" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

US West - Oregon10AZus-west-2155.226.128.0/21

(Alternatively, search for "us-west-2" region in https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))

For more information, see one of the following:

Old IP addresses (before Hyperforce migration)

The IP addresses in the table below only apply if the pod where your Tableau Cloud site resides has not migrated to Hyperforce yet.

For more information, see one of the following:

Pods and IP addresses (before Hyperforce migration)
Host Name (Pod)LocationHyperforce Region NameIP Addresses or Range

10ax.online.tableau.com (10AX)

US West - Oregon

us-west-2

34.208.207.197

52.39.159.250

10ay.online.tableau.com (10AY)

US West - Oregon

us-west-2

34.218.129.202

52.40.235.24

10az.online.tableau.com (10AZ)

US West - Oregon

us-west-2

34.218.83.207

52.37.252.60

us-west-2b.online.tableau.com (UW2B)

US West - Oregon

us-west-2

34.214.85.34

34.214.85.244

us-east-1.online.tableau.com (useast-1)

US East - Virginia

us-east-1

50.17.26.34

52.206.162.101

prod-useast-a.online.tableau.com (prod-useast-a)US East - Virginiaus-east-1

3.219.176.16/28

prod-useast-b.online.tableau.com (prod-useast-b)

US East - Virginia

us-east-13.219.176.16/28

dub01.online.tableau.com (DUB01)

EU West - Ireland

Note: After the move to Hyperforce, region will move to Germany. For more information, see Tableau Cloud Migration to Hyperforce(Link opens in a new window) knowledge article.

eu-central-1

34.246.74.86

52.215.158.213

eu-west-1a.online.tableau.com (EWA1)

EU West - Ireland

Note: After the move to Hyperforce, region will move to Germany. For more information, see Tableau Cloud Migration to Hyperforce(Link opens in a new window) knowledge article.

eu-central-1

34.246.62.141

34.246.62.203

prod-apnortheast-a.online.tableau.com (prod-apnortheast-a)

Asia Pacific - Japan

ap-southeast-1

18.176.203.96/28

prod-apsoutheast-a.online.tableau.com (prod-apsoutheast-b)

Asia Pacific – Australia

ap-southeast-2

3.25.37.32/28

prod-uk-a.online.tableau.com (prod-uk-a)

EU West - UK

eu-west-2

18.134.84.240/28

prod-ca-a.online.tableau.com (prod-ca-a)

Canada - Quebec

ca-central-1

3.98.24.208/28

Find authorisation steps for your data provider

The following links take you to the steps on common data providers’ websites for authorising external applications on their platforms.

Amazon:

Microsoft Azure(Link opens in a new window)

Google Cloud Platform(Link opens in a new window)

Disclaimer: The links in the list above take you outside of Tableau.com. Although we make every effort to ensure links to external websites are accurate, up to date and relevant, Tableau cannot take responsibility for the accuracy or freshness of pages maintained by external providers. Contact the external site for answers to questions regarding its content.

Tableau Bridge connections to Tableau Cloud

To facilitate connections between on-premises data and Tableau Cloud, Tableau Bridge uses common port 443 to make outbound requests to Tableau Cloud. For more information, see Network access section in the Install Tableau Bridge topic.

See also

Thanks for your feedback!Your feedback has been successfully submitted. Thank you!