# Removing the Security Barrier to Agentforce Adoption

[Salesforce](https://yomu.fyi/company/salesforce) · Scott Nyberg · Aug 3, 2026

**Type:** Problem & solution

## Summary

Enterprise AI adoption across regulated industries stalls when internal governance mandates private, dedicated network paths for sensitive data. To eliminate the need for manual VPN tunnels and complex proxy layers, Salesforce re-engineered Private Connect into a multi-cloud networking platform connecting customer environments to Hyperforce services. The Private Connect v2.0 architecture utilizes private links, transit gateways, and direct endpoint routing alongside an automated control plane for rapid Hyperforce regional rollouts. In addition to supporting cross-substrate interconnects for Azure and decoupling endpoint management, the platform incorporates a generic connector framework supporting tools like Snowflake, Databricks, and Kafka. Today, the system provisions secure connectivity in under 30 minutes while processing roughly 120 TB of data and 683 million requests monthly across 15 AWS regions.

## Context

Regulated enterprises in healthcare, banking, and government require sensitive data to travel over private, dedicated network paths rather than traversing the public internet. Initial connectivity deployments forced teams to spend weeks or months configuring site-to-site VPNs, firewall rules, and proxy layers to handle cross-region traffic, creating massive operational overhead and failing to meet the throughput and latency demands of Data 360 and Agentforce.

## Approach / What changed

Salesforce redesigned the system into Private Connect v2.0, replacing proxy layers with private links, transit gateways, and direct endpoint connectivity. The team automated the control plane via APIs so downstream services and new Hyperforce regions could onboard without manual coordination. They also decoupled endpoint management to support diverse hybrid networking configurations across AWS and Azure, and introduced a generic connector framework for external data stores.

## Takeaways

- Redesigning Private Connect around shared infrastructure, automation, and a managed control plane dropped connectivity provisioning time from weeks or months to under 30 minutes.
- Private Connect v2.0 replaced multi-region site-to-site VPNs and virtual machine proxy layers with direct private links and transit gateways to improve throughput and reduce operational complexity.
- The multi-cloud platform currently handles approximately 120 TB of data and 683 million requests per month across 15 AWS regions while supporting 12+ connectors including Snowflake, Databricks, Redshift, and Kafka.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [AWS](https://yomu.fyi/topic/aws), [Azure](https://yomu.fyi/topic/azure), [Scalability](https://yomu.fyi/topic/scalability)

[Read original post](https://engineering.salesforce.com/removing-the-security-barrier-to-agentforce-adoption)