Private Network Access
Antares connection tests run from the Antares environment. A Tableau URL working from a user laptop does not guarantee that Antares can reach it.
Access patterns
Section titled “Access patterns”| Environment | Access pattern |
|---|---|
| Tableau Cloud | Antares connects to Tableau Cloud over HTTPS. Private-network access is usually not required. |
| Public Tableau Server | Antares connects to the Tableau Server API over HTTPS. Firewall or IP allowlist changes may be required. |
| Private Tableau Server | Antares must have a network path to the Tableau Server API endpoint from the environment where Antares runs. |
| Tableau Server Repository | When usage data is enabled, Antares must also reach the Tableau Server PostgreSQL repository host and port. |
| Microsoft Fabric | Antares connects to Microsoft Fabric cloud endpoints over HTTPS for workspace browsing and deployment. |
| Closed internal environment | Antares can be rolled out inside an internal customer environment so Tableau Server, repository, and related endpoints remain accessible only on the private network. |
Internal rollout
Section titled “Internal rollout”For closed environments, Antares can be deployed internally instead of relying on public network access to private systems.
Use an internal rollout when Tableau Server, the Tableau Server Repository, or required supporting services cannot be exposed through public endpoints, VPN access, or IP allowlists.
In this model, Antares runs inside the customer’s network boundary and connects to internal Tableau and repository endpoints using the organization’s existing DNS, firewall, proxy, and certificate controls.