Tableau Cloud Help

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

Source	Publish options	Freshness options	Authentication
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) user name 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 authorization

As a security measure, cloud data providers might require you to supply authorized 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 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.

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 you to regularly check this topic or monitor the https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window) text file directly for new IP addresses to add to your allowlist. New IP addresses are posted to the text file 30-45 days before they’re enabled.

You can find the IP addresses for your pod by using the tables below. You can also find the IP addresses by searching the https://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window) text file for 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-ca", 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)	Location	Hyperforce Region Name	Initial IP Address and Range after Hyperforce Migration
prod-ca-a (prod-ca-a.online.tableau.com)	Canada - Quebec	ca-central-1	155.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))

Pods not migrated to Hyperforce

Location	Pod Name (Host Name)	Hyperforce Region Name	Initial IP Address and Range after Hyperforce Migration
Europe - UK	prod-uk-a	eu-west-2	145.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))
US East - Virginia	useast-1	us-east-1	155.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 - Oregon	10AY	us-west-2	155.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))
Europe - Ireland (moving to Europe - Germany)	DUB01	eu-central-1	145.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))
US East - Virginia	prod-useast-b	us-east-1	155.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))
US West - Oregon	UW2B	us-west-2	155.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 - Australia	prod-apsoutheast-a	ap-southeast-2	141.163.192.0/23 (Alternatively, search for "ap-southeast-2" region inhttps://ip-ranges.salesforce.com/ip-ranges.json(Link opens in a new window))
US East - Virginia	prod-useast-a	us-east-1	155.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 - Ireland	EW1A	eu-central-1	145.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 - Japan	prod-northeast-a	ap-northeast-1	141.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 - Oregon	10AZ	us-west-2	155.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:

• About the Hyperforce migration, see Tableau Cloud Migration to Hyperforce(Link opens in a new window) knowledge article

• About the Hyperforce migration schedule, see the Schedule for Tableau Cloud Migration to Hyperforce(Link opens in a new window) knowledge article

• About alternative methods for maintaining hard-coded IP allowlists, see the Preferred Alternatives to IP Allowlisting on Hyperforce(Link opens in a new window) knowledge article

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:

• About the Hyperforce migration, see Tableau Cloud Migration to Hyperforce(Link opens in a new window) knowledge article

• About the Hyperforce migration schedule, see the Schedule for Tableau Cloud Migration to Hyperforce(Link opens in a new window) knowledge article

Find authorization steps for your data provider

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

Amazon:

• Redshift(Link opens in a new window)

• RDS(Link opens in a new window)

• EC2(Link opens in a new window)

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

• Manage Data

• Best Practices for Published Data Sources(Link opens in a new window) (Tableau Help)

• Notify Owners When Extract Refreshes Fail

• Edit Connections on Tableau Cloud