AI newsOctober 27, 20262 min · updated November 7, 2026

Gemini Enterprise adds VPC connectivity and static IP egress for MCP

Daillac research

Google: Gemini Enterprise release notes for October 27

Written by

Daillac

Editorial and software engineering team

Photographic illustration of a small network cabinet inside a secured glass room beside business offices

Gemini Enterprise release notes dated October 27, 2026 announce general availability of VPC connectivity and static IP egress for custom MCP servers. Regional scope requires attention: this feature supports Agent Gateway in us-central1 and europe-west1. A Canadian business should verify the complete data path before selecting the architecture for its own operational systems.

Two different network requirements

The Google release notes describe access to private MCP servers through Private Service Connect and egress to public servers through Cloud NAT using static addresses. A fixed outgoing IP can meet a network allowlist requirement. It does not replace user authentication or permission checks on individual business records.

The prerequisites documentation maps global or us applications to us-central1 and eu applications to europe-west1 for the network attachment. Associate each region with this specific connectivity feature. The availability of a different Gemini feature in Canada does not establish that the same network path is supported there.

Implications for a business integration

For CRM and ERP automation, begin with permitted business actions. Identify what the MCP server can read, create or change, then check the identity used for each request. Private connectivity can still carry an overly broad request when application permissions have been defined incorrectly.

Consider a fictional sales team that needs to view an order without seeing other customers' accounts. That restriction must be enforced by the business service even when every request arrives through one gateway. A custom CRM and ERP can provide a bounded API when the existing software lacks suitable controls.

Prepare a restricted trial

Map the path between the user, Gemini Enterprise, gateway and MCP server. Record regions, logs and identities at each step. Start with synthetic data and a read operation. Verify denied access as deliberately as authorized responses, including a request for a record outside the user's scope. Preserve evidence of the outcome for review.

A custom web application can handle approvals and exceptions alongside the integration. Before real use, confirm regional scope, network prerequisites and the costs of the chosen architecture. The announcement establishes GA status for the described feature. It does not validate your configuration or settle compliance obligations for the data involved.

Assign a network owner and an application owner to review the trial together. Each should approve the part they can verify, and record unresolved dependencies before the next stage.