Looker Studio Pro support for VPCSC and Private connectivity

Looker Q&A Looker
1

Hi, we currently have Looker Google Cloud Core with below configuration

version 25.20.11, platform edition is Embed (Production), Private IP enabled and a custom domain.

Context: From the screenshot uploaded here, we can enable Looker Studio Pro complimentary licenses. I checked the documentation page here Accept complimentary Looker Studio Pro licenses for a Looker (Google Cloud core) instance  |  Google Cloud Documentation which provides steps selecting the licenses.

image
image1873×402 39.2 KB

Question: Before we start the steps mentioned in the document link above, I wanted to check whether Looker Studio Pro supports VPCSC and private connection - I did not find any documentation specifically for Looker Studio pro. I checked https://docs.cloud.google.com/looker/docs/looker-core-vpcsc this but this doesn’t mention about Looker Studio Pro.

  • Data processing (global or local to where Looker Google Cloud core is hosted) ? - From this section, https://docs.cloud.google.com/looker/docs/looker-core-lsp#prerequisites, I noticed the note there mentioning we need to vend a dedicated project so the Looker Studio Pro content can be stored local to the region selected.

  • Authentication/Authorisation: currently all our users using Looker (Google Cloud Core) are authenticated using our organisation Saml identity provider. How will Looker Studio Pro users will login, will it inherit all the roles from google cloud core?

Thanks

Bihag

2

Hey,

Hope you’re keeping well.

Looker Studio Pro is a separate product from Looker (Google Cloud Core) and does not run inside your Looker Core VPC or inherit its VPC-SC configuration. At this time, Looker Studio and Looker Studio Pro do not support VPC-SC or private IP connectivity in the same way Looker Core does, as they are hosted as a Google-managed SaaS service accessed over the public internet. Data generated in Looker Studio Pro is stored in the Google Cloud project you select during license setup, so you can choose a region-local project to meet residency requirements. Authentication is handled via Google Identity, so if your users are already in Google Workspace or Cloud Identity federated with your SAML IdP, they will log in with the same credentials, but permissions in Looker Studio Pro are managed separately from Looker Core roles. You’ll need to configure sharing and access in Looker Studio Pro explicitly after enabling the licenses.

Thanks and regards,
Taz