Enterprise Agents
Salesforce Plans One Control Plane Across Enterprise Agents
Salesforce introduced an Enterprise AI Harness on September 10, bringing business context, agent actions and governance into a common architecture. Its proposed AI Control Plane would manage agents across vendors. Many underlying products already exist; new capabilities and the unified experience are planned to begin rolling out in early fiscal FY28.
Citation-ready: Salesforce plans new Enterprise AI Harness capabilities and a unified experience for early fiscal FY28, while many underlying technologies are already available.
Evidence boundary: Vendor architecture and availability statements. No deployed cross-vendor control test, price quotation or independent reliability finding.
What happened and why it matters
The announcement puts reusable business controls around agents, but its availability section matters more for implementation planning than the shared architecture diagram.
Primary evidence
Primary reference: Salesforce announcement. Kaleido Field checked the event date and the article's attributed facts against this source.
| Source date | September 10, 2026 |
|---|---|
| Checked by Kaleido Field | September 11, 2026, CST |
| Source function | enterprise agents -> shared control planes and release readiness |
Six capabilities do not mean six new products
Salesforce groups the architecture around business context, planning, action, governance, security and model access. It draws from products including Data 360, MuleSoft, Tableau and Agentforce. The company says customers can combine those components with third-party technology.
For a migration plan, map each required function to a currently available product and an owner. Mark any dependency on the forthcoming unified experience explicitly so it cannot become an unnoticed launch assumption.
An agent registry is only the beginning
The proposed control plane covers agent discovery, identity, lifecycle, observation, performance and cost. Those are useful categories for an inventory, but an inventory is not itself proof that a disallowed action will be blocked.
A pilot should keep one permitted action, one denied action and their actual results. Our identity-aware evaluation report explains why a successful quality test may not test authorization.
Budget against current availability
Salesforce leaves packaging, pricing and upgrade details for a later announcement. Its release language also allows regional and contractual differences. Early fiscal FY28 should be quoted as the company states it, not silently converted into a calendar-quarter promise.
The useful follow-up is a dated release note naming the available surface and limits. Until then, the announcement supports a direction of travel, not a completed enterprise rollout.
Evidence boundary
Vendor architecture and availability statements. No deployed cross-vendor control test, price quotation or independent reliability finding.
FAQ
Is the whole unified harness generally available now?
No. Salesforce distinguishes existing foundations from new capabilities and a unified experience planned to start rolling out in early fiscal FY28.