AI agents are forcing Google to rethink data architecture
AI agents promise to search for information, make decisions and act directly within company systems, but this autonomy depends on one essential condition: accessing the right data and, above all, understanding its context. Google Cloud is tackling this challenge with its Agentic Data Cloud, an AI-native architecture designed to move traditional data platforms towards what Google calls a “System of Action”, capable of powering agents that perceive, reason and act on the organisation’s information.¹ The stakes therefore go far beyond adding Gemini to a database: Google is seeking to bring together structured and unstructured data, metadata, business rules, governance and analytics engines so that agents can make use of scattered information without having to rebuild its context for every new task.
A Cross-Cloud Lakehouse to fetch data wherever it lives
The first major building block of this architecture is a Cross-Cloud Lakehouse based on Apache Iceberg, an open format that keeps the architecture interoperable rather than locking data into a proprietary environment. Google Cloud wants its engines and agents to be able to access data hosted directly in other clouds, notably AWS and Azure, without first requiring it to be migrated to Google Cloud.² The architecture can federate catalogues such as AWS Glue, Databricks Unity Catalog and Snowflake Horizon, while BigQuery and other engines can query the remote data. This approach is particularly important for large enterprises whose information assets are already spread across several clouds, data warehouses, lakehouses and SaaS applications: asking an agent to act across the organisation assumes it can cross these silos without multiplying copies and ETL pipelines.
Google wants to avoid moving petabytes to feed an AI
This approach also addresses an economic and operational problem. Continuously moving large volumes of data between clouds incurs egress costs, adds latency and forces teams to maintain additional pipelines. For its cross-cloud architecture, Google relies in particular on Cross-Cloud Interconnect, federation of Iceberg catalogues and caching mechanisms to let analytics engines work on remote data without systematically duplicating files.² For an agent, this capability can prove decisive: a complex task may require combining sales data in one environment, operational data in another and information from business applications, sometimes within seconds. Data architecture thus becomes a direct prerequisite for AI autonomy.
The Knowledge Catalog aims to give meaning to company data
Yet accessing all the data is not enough. An agent may find a column called “margin” without knowing whether it refers to gross, net or forecast margin, or one calculated according to a rule specific to the company. This is precisely the role of the Knowledge Catalog, an evolution of Dataplex Universal Catalog, which Google presents as a universal context engine for agents.¹ It aggregates metadata from Google Cloud environments and partner platforms, continuously enriches its meaning based on usage and uses Gemini in particular to extract meaning from unstructured content and generate some missing semantic information. Google also links this layer to Looker, LookML and BigQuery Measures to incorporate more business logic into the context available to agents. The aim is to turn the traditional data catalogue, long used to inventory and govern assets, into an active layer that enables AI to understand what it is handling.
Governance becomes part of the agent’s reasoning
This contextualisation must also respect access rights. Google states that Knowledge Catalog search takes access controls into account, so that an agent can only find and use the assets it is authorised to access.¹ This is essential as agents begin to go beyond simple text generation and take part in operations: an AI tasked with analysing sales should not automatically gain access to HR files or confidential financial information simply because that data sits in the same lakehouse. Governance must therefore follow information from its discovery to its use by the agent, covering aspects such as quality, lineage, permissions and business meaning. The Agentic Data Cloud thus brings together two disciplines that have long been treated separately: data governance and AI system governance.
Without reliable context, an agent remains blind
This development directly transforms Data Management. Data engineers and data professionals no longer simply prepare tables for analysts, dashboards or machine learning models: they must now build information that is reliable and contextualised enough for an agent to interpret it without constant human intervention. Data quality, metadata, semantic models, cataloguing, lineage and access policies therefore become integral parts of the AI’s reasoning. A poor business definition or outdated data can now cause not only a flawed analysis but also a wrong action, if the agent uses that information to trigger an operation automatically. In the agentic enterprise, the quality of the AI’s decisions depends directly on the quality of the data architecture that feeds it.
The battle of the agents is also a battle of data architectures
Google is therefore no longer simply trying to offer better-performing models. With the Agentic Data Cloud, the group wants to control a much larger part of the chain linking information to action: storage, databases, lakehouse, analytics, business context, search, governance, Gemini models and the agentic platform. This strategy reflects a significant shift in the market: companies may find that their difficulties in industrialising agents stem less from model capabilities than from data that is fragmented, poorly documented or hard to connect to AI systems. A Google Cloud study published in 2026 indeed found that 43% of IT leaders surveyed see difficulties integrating with legacy APIs and data sources as their main infrastructure gap for agentic AI.³
The next critical infrastructure could be the one that gives AI context
Ultimately, the Agentic Data Cloud shows that the age of agents will not simply be about multiplying autonomous assistants. For an agent to manage a sales process, analyse a supply chain or work within a business application, it needs to know where the information is, what it means, whether it is reliable enough and whether it has the right to use it. The Cross-Cloud Lakehouse addresses the problem of accessing distributed data, while the Knowledge Catalog seeks to provide the layer of context and governance needed to interpret it. Google Cloud is thus betting on a simple yet far-reaching idea: in the next phase of enterprise AI, the advantage may not go only to whoever has the best agent, but to whoever can supply it with the most reliable data and the most precise business context.
360° IT News — decoding technology to understand the jobs of tomorrow.
Further reading
This development extends a transformation already visible in modern data architectures. Read our CCCLX article “ AWS strengthens OpenSearch to connect AI to enterprise data ”, which looks at another central challenge of professional AI: enabling models and intelligent applications to find and make effective use of information scattered across the organisation’s systems.
References
1. Google Cloud. (2026). What's new in the Agentic Data Cloud: Powering the System of Action.
https://cloud.google.com/blog/products/data-analytics/whats-new-in-the-agentic-data-cloud
2. Google Cloud. (2026). The future of data lakehouse: Open and interoperable for the agentic era.
https://cloud.google.com/blog/products/data-analytics/the-future-of-data-lakehouse-for-the-agentic-era
3. Google Cloud. (2026). State of AI infrastructure report and the Agentic Data Cloud.
https://cloud.google.com/blog/topics/ai-infrastructure/state-of-ai-infrastructure-report-and-the-agentic-data-cloud
4. Google Cloud. (2026). About cross-cloud data access.
https://docs.cloud.google.com/lakehouse/docs/about-cross-cloud-data-access
GitHub Copilot bulks up for business: coding agents come under IT control
Copilot is no longer just there to suggest the next line GitHub Copilot is continuing its transformation. Originally known mainly for completing code in the editor, the tool is now evolving towards agents capable of exploring a project, modifying files, using tools...
PDFs, presentations, audio: Adobe wants to turn Acrobat into a content factory
Acrobat no longer just wants to open your documents For more than thirty years, Acrobat has mainly been used to read, create, edit, sign and share PDFs. Adobe now wants to give it a much broader role. On 9 September 2026, the company announced new capabilities based...
Salesforce plugs Claude into its CRM: Claudeforce prepares for life after the interface
What if the CRM soon no longer needed to be opened? For decades, using a CRM meant navigating between customer records, dashboards, menus and forms. With Claudeforce, Salesforce and Anthropic want to change this logic: rather than forcing users to go into Salesforce...
Kimi K3, Mistral, DeepSeek: Oracle turns OCI into an AI model hub
Oracle wants to make OCI a one-stop shop for AI Oracle is stepping up its efforts in the AI cloud battle by significantly expanding the catalogue of models available in OCI Enterprise AI. On 4 September 2026, the group announced in particular the integration of Kimi...
Google Cloud tackles the hidden bill of AI agents
AI agents raise a new problem: how much does a task really cost? As companies move from chatbots to AI agents able to work through multiple steps, the question of cost becomes much more complex. A chatbot generally handles a request and generates an answer, whereas an...
Workday, Navan, Avalara: ChatGPT Work moves into business software
ChatGPT Work is gradually leaving the chat window With GPT-6 Astra, OpenAI is no longer simply trying to improve the quality of ChatGPT’s answers. The company wants to bring its AI closer to the applications in which employees actually work. With the arrival of GPT-6...
From chip to cloud: Groq raises 350 million to scale up
Groq now wants to sell cloud rather than just chips Groq is pursuing a major strategic transformation. Long seen as one of Nvidia’s challengers thanks to its LPUs (Language Processing Units) specialised in artificial intelligence model inference, the group is now...
Muse Code: Meta launches its AI agent to tackle giant codebases
Meta wants to bring AI agents into complex software projects Meta is stepping up its efforts in AI-assisted software development with Muse Code, a new agent designed to work on large codebases, where traditional assistants can quickly lose the context needed to...
Qwen3.8-Max reportedly coded for 16 days without human intervention
Alibaba tests how far an autonomous AI developer can go Alibaba claims to have reached a new milestone in agentic software development with Qwen3.8-Max, its new flagship model launched in early August 2026. In an internal test, the model reportedly worked fully...
Two months, $1.1 billion: River AI is already exciting investors
A spectacular raise for a start-up barely out of the shadows Two months after emerging from stealth mode, River AI has just completed one of the most spectacular funding rounds of the year in artificial intelligence. The start-up founded by Igor Babuschkin, a former...
