Google has put Data Cloud connectors for Gemini into preview, allowing business users to ask natural-language questions of live enterprise data under their own credentials. Its 6 November announcement describes preview connections to BigQuery, Spanner, Cloud SQL, AlloyDB and Looker, with existing row- and column-level database permissions governing query execution.
The attraction for analysts is a route from a business question to a database result without first identifying the right tables themselves. But authorised access and a correct answer remain different questions. Google’s connection documentation warns that query accuracy can vary on complex transactional schemas and that the connectors are not restricted to a particular dataset, table or database instance.
Data Cloud connectors query in place through user identity
In federated query mode, the connector queries the underlying source without copying or indexing the data into a Gemini Enterprise data store. That is different from data ingestion mode, which the documentation also describes and which does copy data. The in-place claim belongs to the federated path, not every possible Google data connection.
Each connector is powered by a first-party Model Context Protocol server. Google says requests authenticate with the user’s own credentials, through IAM permissions or OAuth 2.1, before queries execute against the source. The announcement says an employee cannot use natural-language prompts to query records their account is not permitted to access.
Knowledge Catalog supplies the discovery and interpretation layer. Gemini searches accessible data assets and retrieves context such as schemas, business glossary terms, technical metadata and table relationships. It then formulates SQL and invokes the connector’s tools. This is more than a new search box: interpreting the organisation’s vocabulary is part of the path from a question to a query.
Broad access differs from a curated data agent
Google positions direct connectors for exploratory and ad hoc work, alongside conversational analytics agents that data teams curate for specific domains. The documentation’s resource-scope warning means a connector can reach all resources of its source type that the authenticated user has permission to query. Attaching it to an app is not itself a deterministic table-level allowlist.
For workloads requiring tightly defined tables or business metrics, the docs point to scoped data agents with curated schemas and verified queries. Catalog metadata and instructions can guide a broad connector toward relevant data, but guidance is different from a fixed resource boundary. The docs also note that broad discovery can introduce latency and depends on well-maintained metadata and skills.
Administrators configure default read-only connections in the Gemini admin console, according to the announcement. Users can then carry results into a Google Doc, a Gmail draft or Google Slides. These are output destinations for the findings; they are not evidence that the preview automatically validates the underlying business conclusion.
Permissions answer who can query, not whether SQL is right
For an enterprise evaluating the preview, the central distinction is between access governance and analytical quality. Executing as the user preserves the database’s existing permission boundary. It does not establish that the agent chose the intended table, understood a business term correctly or generated the right join. The documentation’s complex-schema caveat is therefore material even when row- and column-level permissions work exactly as described.
Resource scoping is a third question. A user can legitimately have wide access while a particular reporting task needs only a narrow subset. The broad connector and curated-agent approaches make different trade-offs here: one reduces upfront selection and supports exploration, while the other requires data-team preparation to narrow the task. Choosing between them depends on whether the immediate need is discovery or repeatable analysis of a defined business metric, rather than assuming that one permission-aware connection supplies both automatically.
The same distinction explains why in-place querying is not a guarantee of correctness. Avoiding another copied index describes where the query runs and how data is accessed. It leaves schema interpretation and answer checking as separate parts of the workflow.
TSN’s coverage of Google’s connected-apps platform preview provides the wider integration context. ServiceNow workflows connected to Gemini Enterprise concerns business processes rather than direct database discovery, while Databricks Genie One and Snowflake’s agentic previews offers a comparison with other conversational data tools.
The next practical decision for adopters is which questions can tolerate broad exploration and which need a curated data agent. Google’s preview opens the former route while its own documentation preserves that distinction.
Sources
- Google Cloud: Data Cloud connectors announcement, 6 November 2026
- Google Cloud docs: Connect to Data Cloud
Related stories
Databricks Lets Genie One Run Code as Snowflake Starts Two Previews compares alternative approaches to asking enterprise data questions through agents.
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X
