Skip to main content
AI NewsAI NewsSalesforceEnterprise AI HarnessAI Control Plane

Salesforce unifies enterprise AI context, action, governance, security, and models in a new Harness

The proposed control plane combines capabilities already available with new features and a unified experience planned to begin rolling out in early FY28.

ENHE AI5 min4 views
Salesforce unifies enterprise AI context, action, governance, security, and models in a new Harness

Key takeaways

Salesforce introduced its Trusted Enterprise AI Harness on September 10, combining six capabilities for context, agency, action, governance, security, and model choice with an AI Control Plane for managing agents and AI across an enterprise. The company says customers can use the architecture with Salesforce technology, existing technology, or third-party models and systems, and describes headless access through MCP, APIs, Skills, and Plug-ins. Many technologies forming the foundation are available today. However, Salesforce explicitly says new capabilities and the unified experience are planned to begin rolling out in early fiscal FY28; pricing, packaging, regional availability, and upgrade paths will follow closer to general availability. Teams should treat this as an integration direction and validate current product availability before making architecture or purchasing commitments.

Salesforce defines the Harness as a composable architecture across Trusted Context, Agency, Action, Governance, Security, and Models that can work with third-party models, agents, and systems.
The AI Control Plane is intended to discover and register AI capabilities, establish identity and policy, manage lifecycle, evaluate performance, observe behavior and outcomes, and control cost.
Salesforce says many foundation technologies are available today.

Direct answer

Salesforce introduced its Trusted Enterprise AI Harness on September 10, combining six capabilities for context, agency, action, governance, security, and model choice with an AI Control Plane for managing agents and AI across an enterprise. The company says customers can use the architecture with Salesforce technology, existing technology, or third-party models and systems, and describes headless access through MCP, APIs, Skills, and Plug-ins. Many technologies forming the foundation are available today. However, Salesforce explicitly says new capabilities and the unified experience are planned to begin rolling out in early fiscal FY28; pricing, packaging, regional availability, and upgrade paths will follow closer to general availability. Teams should treat this as an integration direction and validate current product availability before making architecture or purchasing commitments.

Verified facts

Salesforce defines the Harness as a composable architecture across Trusted Context, Agency, Action, Governance, Security, and Models that can work with third-party models, agents, and systems.

The AI Control Plane is intended to discover and register AI capabilities, establish identity and policy, manage lifecycle, evaluate performance, observe behavior and outcomes, and control cost.

Salesforce says many foundation technologies are available today. New capabilities and the unified experience are planned for early fiscal FY28; pricing, packaging, regions, and upgrade details are not yet announced.

Salesforce unifies enterprise AI context, action, governance, security, and models in a new Harness cover infographic
ENHE AI original composite: a topic-specific real-work scene with fact-checked editorial copy.

What changed

  • Dispersed agent capabilities are organized into six reusable enterprise layers
  • A common control plane brings together identity, policy, evaluation, observability, and cost
  • Headless access is planned through MCP, APIs, Skills, and Plug-ins
  • The unified experience remains a planned rollout rather than a fully available product bundle
Salesforce unifies enterprise AI context, action, governance, security, and models in a new Harness team operating flow
A four-step path from announcement to testable, reversible, auditable operations.

Impact for AI users

The announcement frames governed proprietary context and secure action, rather than one model choice, as the enterprise differentiator. For teams already using Salesforce, it provides an integration direction for data, workflows, permissions, and agents. A direction is not a delivery commitment: technical and procurement owners should separately validate what is available now, what is planned for FY28, regional constraints, and third-party integration requirements. Do not make a near-term launch dependent on the future unified experience.

Operating checklist

  1. Inventory each current agent's context, tools, workflows, permissions, models, and cost sources to find controls without a single owner.
  2. Mark every proposed capability as available now, planned for FY28, or unconfirmed, and request regional and entitlement evidence from the vendor.
  3. Validate identity, policy, evaluation, audit, and cost correlation across systems in one reversible business workflow first.
  4. Define minimum data, tool, and action scopes for third-party models and agents so a unified entry point does not broaden default access.

AI frontier news and analysis, AI software and model tools, AI skill tutorials and validation methods, and AI account and permission guidance

FAQ

Is the Enterprise AI Harness fully purchasable now?

No. Salesforce says many foundation technologies are available, while new capabilities and the unified experience are planned to begin rolling out in early FY28; detailed pricing and packaging will follow.

Can it connect only Salesforce models and agents?

No. Salesforce says the architecture can use its technology, existing technology, or both, including third-party models, agents, and systems.

Does the AI Control Plane automatically guarantee compliance?

No. It centralizes capabilities for identity, policy, evaluation, observability, and cost; an enterprise still defines its applicable permissions, data governance, audit, and approval rules.

Summary

Salesforce is consolidating existing enterprise capabilities into an AI control and execution architecture. Use it now to assess whether your own control plane is complete, while preserving clear timing and procurement boundaries around the unified experience planned for FY28.

This AI-assisted article is checked by ENHE AI automation for official sources, bilingual fields, media rights, page safety, and historical duplication before publication.

What this means for everyday users

The announcement frames governed proprietary context and secure action, rather than one model choice, as the enterprise differentiator. For teams already using Salesforce, it provides an integration direction for data, workflows, permissions, and agents. A direction is not a delivery commitment: technical and procurement owners should separately validate what is available now, what is planned for FY28, regional constraints, and third-party integration requirements. Do not make a near-term launch dependent on the future unified experience.

Tools you may use

Related tutorials

Related Tools And Tutorials

Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.

Related reading

Salesforce introduces Slackforce Surfaces for AI-built dashboards, reports, and interactive work inside Slack

Salesforce introduced Slackforce Surfaces on September 11, allowing people to ask Slackbot to turn conversations, Salesforce records, Slack history, and connected enterprise data into dashboards, reports, executive HTML decks, calculators, and other interactive interfaces. A Surface can be pinned to a channel so a team can filter, explore, discuss, and act from one shared workspace. Salesforce says Surfaces operate under existing permissions, limiting users to information they are already allowed to see. The product is available for customers on Enterprise+, Business+, Pro, Legacy, and Free Teams when Slackbot is enabled. However, the company separately states that the live-data feature begins rolling out in October. Teams should therefore verify workspace eligibility, refresh behavior, record-level grounding, and downstream actions rather than assume every demonstrated live capability is active immediately.

Cloudflare Unifies Workers AI and AI Gateway: Choosing an AI Control Plane

Cloudflare announced on August 7, 2026 that Workers AI and AI Gateway are moving toward one AI control plane. The announcement describes unified bindings, observability, billing, and dynamic routing across Cloudflare-managed GPUs and external providers. That can simplify multi-model operations, but it does not guarantee lower cost, consistent quality, or compliance. Choose the control plane around a real task: define model and latency needs, data sensitivity, budget, routing and fallback requirements, then test one low-risk endpoint with read-only logs. Preserve the actual model and version, latency, error, cost, permission, and fallback evidence before moving broader traffic. Small applications may be better served by one provider and clear logs until routing complexity has a measurable benefit.

NVIDIA Expands DGX Spark With 64GB: Evaluate a Local AI Workstation

On October 2, NVIDIA announced a 64GB unified-memory DGX Spark configuration and said partner availability would begin October 23 at a starting price of $4,999. NVIDIA says one unit can run models up to 100 billion parameters and that two systems can pool 128GB; it reports up to 1.7x performance in its own Qwen 3.8 27B test. Availability is forward-looking, and performance figures are vendor results. Model choice, quantization, context length, and concurrency change outcomes. This article offers a practical evaluation checklist for teams comparing local inference with cloud services. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.

Microsoft’s 2026 Defense Report: AI Is Changing the Pace of Cybersecurity

In its October 1 commentary on the 2026 Microsoft Digital Defense Report, Microsoft says threat actors are using AI in parts of existing workflows, including reconnaissance and social engineering. The post does not claim that attacks have become fully autonomous; it highlights changes in speed and scale. Identity controls, least privilege, data protection, monitoring, testing, and secure development remain central. This article separates Microsoft’s observations from independent conclusions and turns the post into a practical checklist. Teams should compare the claims with their own telemetry and incident history before changing priorities. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.

A One-Week AI Agent Security Review Using the OWASP Risk Framework

The OWASP Gen AI Security Project published its 2026 Top 10 for Agentic Applications in December 2025 as a risk framework for systems that plan, call tools, or act across services. It is a starting point for security discussion, not a certification, compliance attestation, or guarantee of safety. This article turns it into a one-week baseline review: inventory agent identities and tools, narrow permissions, treat external content as untrusted input, record consequential actions, test shutdown and revocation, and define approval and recovery for high-impact operations. Teams should extend the checklist to match their architecture and threat model. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.

Microsoft Announces Streaming Transcription: Voice Agents Can Respond Earlier

On October 1, Microsoft AI announced MAI-Transcribe-2-Streaming, MAI-Voice-2.1, and a Flash variant. Microsoft says the streaming transcription model supports 60 languages with continuous language detection, and that initial partials can appear just over 100 milliseconds after audio arrives. Its speech-generation models are described as supporting 23 languages and 26 locales. Rankings, accuracy, speed, and price claims come from Microsoft’s announcement and do not predict results for every workload. This article explains the interaction changes and suggests tests for latency, revisions, accents, privacy, and total cost. Teams should check applicability against their own environment, record assumptions, and validate decisions with representative operational evidence.

Sources

Table of contents

Latest Insights