AlloyDB for PostgreSQL
Feature
Hot standby enhances the AlloyDB high availability (HA) architecture to improve failover times and to ensure consistent performance after failover. AlloyDB continuously replicates transactions to the standby node to keep caches warm and to ensure that the node is ready to take over quickly during a failover. This feature is generally available (GA) in PostgreSQL 18 and is automatically enabled for all new instances. For more information, see the AlloyDB high availability overview.
Apigee X
Feature
General Availability (GA) launch of Model Context Protocol (MCP) in Apigee
With this release, Model Context Protocol (MCP) in Apigee is generally available, enabling you to expose your Apigee APIs as MCP tools to agentic applications.
Any MCP client that supports remote MCP endpoints over HTTP/S can access these tools. Because the endpoints are managed, you don’t need to install or manage local MCP servers, remote MCP servers, or additional infrastructure to enable agentic applications to access your services.
MCP in Apigee is available for Subscription, Pay-as-you-go, and Evaluation organizations, including organizations with Data Residency and VPC Service Controls enabled.
For more information on using MCP in Apigee, see MCP in Apigee overview.
Change
Updated MCP server target endpoint for MCP Discovery Proxies
With the GA launch of Model Context Protocol (MCP) in Apigee, the structure of the MCP server target endpoint for MCP Discover Proxies has changed to ORG_NAME.mcp.apigee.internal.
Private preview customers using the previous format (mcp.apigee.internal) are encouraged to update their proxies to reflect the new structure. Existing endpoints using the old format will continue to work, but new endpoints will use the new structure.
Announcement
On March 31st, 2026, we released an updated version of Apigee.
Feature
Enhanced OAS server URL path handling for MCP in Apigee
With this feature enhancement, your OpenAPI specification (OAS) configurations behave exactly
as defined in the OAS standard, automatically combining the server.url base path value with individual operation paths.
For example, a server URL ofhttps://example.com/api/v1 paired with a path of /users will now correctly route to https://example.com/api/v1/users without additional manual intervention.
If you previously prepended base paths to your OAS paths entries, remove the path segment from your servers.url field to prevent
duplication. For example, change https://example.com/api/v1 to https://example.com.
For more information, see Create an OpenAPI 3.0 specification.
Issue
Known Issue 496552286: Deployment fails for MCP Discovery Proxies in regions with capacity limitations.
For more information, see Apigee known issues.
BigQuery
Feature
BigQuery ObjectRef values
now support the following:
- You can run
ObjectReffunctions with either direct access or delegated access. - The
OBJ.MAKE_REFfunction automatically fetches the latest Cloud Storage metadata and populates this in theref.detailsfield. - The
OBJ.GET_READ_URLfunction returns aSTRUCTvalue with a read URL and status columns and renders image results in the Cloud console. Use this function when you don’t require a write URL.
These features are generally available (GA).
Cloud NAT
Announcement
The default TCP TIME_WAIT
timeout for Cloud NAT is scheduled to decrease from 120 seconds to 30 seconds,
across all regions, as follows:
- From June 30 to September 29, 2026: new Cloud NAT gateways will use either the 120-second or 30-second default, depending on when the update is deployed in a specific region.
- On or after September 30, 2026: all new Cloud NAT gateways in all regions will use the 30-second default.
Impact on gateways
- New gateways: after the update is deployed in a region, all new Cloud NAT gateways created in that region will use the 30-second default. This change also applies if a pre-update gateway is deleted and then recreated.
Existing gateways: Cloud NAT gateways created before the regional update will retain the 120-second default. You can adjust this value by using the –tcp-time-wait-timeout flag at any time.
Cloud NAT gateways configured with a custom
TIME_WAITvalue aren’t affected and will continue to use your configured custom value.
The following table outlines the applicable default timeout for new gateways throughout the deployment timeline.
| Gateway type | Default timeout (before June 30) |
Default timeout (June 30—September 29) |
Default timeout (on or after September 30) |
|---|---|---|---|
| New | 120 seconds | 30 or 120 seconds | 30 seconds |
Cloud SQL for MySQL
Feature
You can now migrate a subset of databases from an external server to a destination Cloud SQL for MySQL instance.
For more information, see Configure Cloud SQL and the external server for replication.
Cloud TPU
Feature
Generally available: TPU7x is generally available (GA). TPU7x is the first release within the Ironwood family, Google Cloud’s seventh generation TPU. TPU7x supports large-scale AI training and inference, providing performance and cost-effectiveness for demanding workloads such as large language (LLMs), mixture of experts (MoEs), and diffusion models. For more information, see the TPU7x (Ironwood) documentation.
Compute Engine
Feature
Generally available: The maximum throughput for a Hyperdisk ML disk is increased to 2,097,152 MiB/s from 1,200,000 MiB/s. Hyperdisk ML provides the highest throughput per disk for machine learning and for workloads that require high read throughput on immutable datasets.
For more information, see About Hyperdisk ML.
Document AI
Feature
Upgrading fine tuned custom extractor processors is now available in Preview.
The feature allows you to fine tune a new processor version with a newer base version, while keeping the configurations of the previously fine-tuned processor version selected. This is available through the UI in the Deploy & use tab in the console.
This is currently supported for upgrading pretrained-foundation-model-v1.4-2025-02-05
to pretrained-foundation-model-v1.5-2025-05-05.
For more information, see training overview.
Gemini Enterprise
Feature
Gemini Enterprise and NotebookLM Enterprise: BSI C5:2020 compliance
Gemini Enterprise and NotebookLM Enterprise are certified for BSI C5:2020 compliance.
Feature
Gemini Enterprise: Connect Salesforce data using data federation (Preview)
You can connect Salesforce data stores to Gemini Enterprise using data federation.
This feature is in Public Preview. For more information, see Connect Salesforce.
Feature
Gemini Enterprise: Federated connector error logs in Logs Explorer
You can view detailed error logs for your federated connectors in Logs Explorer. These logs include connection problems, data transformation issues, or API errors.
For more information, see Access Gemini Enterprise connector error logs with Cloud Logging.
Google SecOps
Feature
Multi-stage queries in YARA-L
The Multi-stage queries feature is now GA. This feature lets you feed the output of one query stage into the input of another, providing more granular data transformation than a single, monolithic query.
You can use multi-stage queries in both Dashboards and Search to build sophisticated detection and visualization logic. No action is required to enable this feature.
Learn more about how to create multi-stage queries with YARA-L 2.0.
Google SecOps SIEM
Feature
Multi-stage queries in YARA-L
The Multi-stage queries feature is now GA. This feature lets you feed the output of one query stage into the input of another, providing more granular data transformation than a single, monolithic query.
You can use multi-stage queries in both Dashboards and Search to build sophisticated detection and visualization logic. No action is required to enable this feature.
Learn more about how to create multi-stage queries with YARA-L 2.0.
Identity and Access Management
Feature
Gemini assistance in the IAM role picker is generally available.
For more information, see Get predefined role suggestions with Gemini assistance.
Oracle Database@Google Cloud
Feature
Oracle Database@Google Cloud supports VPC Service Controls. For more information, see Configure VPC Service Controls. This feature is Generally Available (GA).
SAP on Google Cloud
Announcement
ABAP SDK for Google Cloud version 1.13 (On-premises or any cloud edition)
Version 1.13 of the on-premises or any cloud edition of the ABAP SDK for Google Cloud is generally available (GA). For the latest Gemini 3.1 Pro models, this version includes support for function calling with thought signatures and enhanced thinking configurations to optimize model reasoning.
Additionally, this version introduces support for the Parameter Manager API and fixes an issue with the recordstamp field in the BigQuery toolkit for SAP when multiple records with the same primary key are replicated to BigQuery.
For more information, see What’s new with the on-premises or any cloud edition of the ABAP SDK for Google Cloud.
Security Command Center
Feature
Risk Engine now supports aiplatform.googleapis.com/ReasoningEngine in both attack paths and high value resource sets.
Source: Google Cloud Platform
![(Updated) New enrollment dashboard and data deletion controls in Teams Admin Center [MC1191921]](https://mwpro.co.uk/wp-content/uploads/2025/06/metro-station-3714290_1920-96x96.webp "(Updated) New enrollment dashboard and data deletion controls in Teams Admin Center [MC1191921] 7")