What Is Tableau Cloud? The Managed SaaS Platform for Tableau Analytics

Tableau Cloud (formerly Tableau Online) is the fully managed, SaaS-hosted version of Tableau's analytics platform. It provides all the analytical and visualization capabilities of Tableau Server — publishing, collaboration, governance, scheduled extracts, embedded analytics, and the Tableau REST API — without the infrastructure management overhead of running and maintaining an on-premises or self-hosted server deployment.

Tableau announced the end-of-life for Tableau Server in early 2024, with support ending in 2027. This announcement accelerated the existing trend of organizations migrating from on-premises Tableau Server to Tableau Cloud. Understanding what Tableau Cloud provides, how it differs from Server, and what migration involves is now a critical planning question for every Tableau Server organization.

What Tableau Cloud Provides

**Fully managed infrastructure.** Tableau Cloud runs on Salesforce's infrastructure. Tableau (Salesforce) handles hardware provisioning, server software installation, patching, security updates, version upgrades, and disaster recovery. Customers do not manage server processes, disk space, or server configuration.

**Automatic version upgrades.** Tableau Cloud is always on the current Tableau version. There are no upgrade windows to plan, no compatibility testing to execute, and no version debt to accumulate. Customers on Tableau Cloud automatically receive new features as they are released.

**Site administration, not server administration.** In Tableau Cloud, customers administer their site — managing users, projects, content, permissions, data sources, and extract schedules — but do not administer the underlying server infrastructure. The distinction is significant: Tableau Server administration requires dedicated technical staff; Tableau Cloud site administration can be handled by a data team lead or analytics manager without deep server expertise.

**Scale without capacity planning.** Tableau Cloud scales automatically with demand. There is no need to size backgrounder processes for peak extract loads, configure VizQL processes for concurrent users, or plan server expansion for growth.

**Regional deployments.** Tableau Cloud is available in multiple regions (US West, US East, EU, APAC) to address data residency requirements. EU organizations with GDPR data residency constraints can deploy to Tableau Cloud EU.

Tableau Cloud vs. Tableau Server: Key Differences

**Infrastructure ownership.** Tableau Server: the customer owns and operates the server infrastructure. Tableau Cloud: Salesforce/Tableau operates the infrastructure.

**Administration scope.** Tableau Server: server admin covers server process configuration, hardware, OS, patching, network, disaster recovery. Tableau Cloud: site admin covers users, content, permissions, data connections, extract schedules.

**Customization.** Tableau Server allows deeper customization: custom fonts, custom identity providers not on the supported list, integration with systems that require network-level access. Tableau Cloud has a more constrained environment — some customizations available on Server are not available on Cloud.

**Connectivity.** Tableau Cloud connects to cloud databases (Snowflake, BigQuery, Redshift, Azure SQL) natively. For on-premises data sources, Tableau Cloud requires Tableau Bridge — a lightweight connector installed in the customer's network that proxies data connections between the on-premises source and Tableau Cloud.

**Pricing model.** Tableau Server is licensed per user (Creator, Explorer, Viewer) with additional licensing for the server capacity (core-based licensing for the server software). Tableau Cloud is priced per user with the cloud hosting included — no separate server licensing.

**Embedded analytics.** Tableau Cloud supports embedded analytics via the Tableau Embedding API v3. Organizations building customer-facing or internal application embedding need to use the Connected App feature for authentication and the Embedding API for integration. The licensing model for external embedding (customers outside the organization) is Tableau Embedded Analytics, which has separate pricing.

Tableau Bridge: Connecting Cloud to On-Premises Data

Organizations that have on-premises databases (Oracle, SQL Server, SAP HANA, on-premises PostgreSQL) need Tableau Bridge to connect Tableau Cloud to these sources.

Tableau Bridge is a lightweight Windows or Linux process installed inside the customer's network. It maintains a persistent outbound connection to Tableau Cloud and routes data queries from Tableau Cloud to the on-premises source through that connection. No inbound firewall rules are required — Bridge uses an outbound connection.

Bridge supports both live connections (queries pass through Bridge in real time) and scheduled extract refreshes (Bridge executes the extract query against the on-premises source and uploads the resulting .hyper file to Tableau Cloud).

For organizations with significant on-premises data infrastructure, Bridge management becomes an operational responsibility — ensuring Bridge processes are running, monitoring for failures, and managing Bridge version upgrades. This is the primary ongoing operational overhead of a Tableau Cloud deployment for organizations that have not fully moved their data to the cloud.

Migrating from Tableau Server to Tableau Cloud

The Tableau Server to Cloud migration is a significant project for organizations with large, long-standing Tableau deployments.

**Content migration.** Workbooks, published data sources, flows, and projects can be migrated using Tableau's Content Migration Tool (CMT). CMT maps projects and permissions from the Server environment to the Cloud environment. Large environments may have thousands of workbooks requiring validation after migration.

**Permission migration.** User groups, project permissions, and content permissions must be recreated in Tableau Cloud. Permission structures that rely on Active Directory groups need to be mapped to equivalent identity management in Tableau Cloud (SAML SSO with an IdP that provides group claims).

**Data connection migration.** Live connections to cloud data sources typically migrate without significant changes. Connections to on-premises sources require Bridge installation and configuration. Embedded database credentials must be re-entered.

**Extract schedule migration.** Extract schedules on Tableau Server run as part of the Server's backgrounder configuration. On Tableau Cloud, extract schedules are set per data source. Schedules must be recreated — CMT does not migrate extract schedules.

**Identity and authentication.** Tableau Cloud supports local authentication, SAML (for SSO with enterprise identity providers like Okta, Azure AD, Ping), and MFA. Organizations migrating from Server-with-AD typically configure SAML SSO in Cloud.

**Validation.** After migration, workbooks and data sources must be validated: do the dashboards load? Are the numbers correct? Are permissions applied correctly?

Our managed BI services include Tableau Server-to-Cloud migration planning and execution, including content migration, permission migration, Bridge setup, and post-migration validation. Contact us to discuss your Tableau Cloud migration.

A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.