Skip to content
Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Winter '27 overview
Top 10

Top 10 Winter '27 Features

From Agentforce on by default to the February 2027 OAuth deadline, the ten changes that matter most in Winter '27.

In the first week of September 2026, admins in orgs with Agentforce licences started finding the Agentforce platform already switched on. No ticket, no toggle, no change to the bill. That is the right way into Winter '27, because the release is less about any single feature and more about Salesforce turning agents, MCP and headless development into defaults rather than options.

Salesforce published its own Top 10 for the release: Slack Code, Adaptive Experiences and Dynamic Plans, Agentforce Contact Center, Tableau Knowledge, Informatica Headless, Agentic Segmentation and Activation, Autonomous Scheduling with Agentforce Voice, Agent Skills and Plugins, Third-Party Agent Orchestration, and Agentic Commerce Search. Our list overlaps with it but ranks differently. These are the ten changes that alter decisions for admins, developers, architects and consultants, ordered by how many orgs they touch. Release notes first published the week of August 17, 2026, sandbox preview began the weekend of August 28-29, and production upgrades finished the weekend of October 9-10, 2026.

1. Agentforce Is On by Default

The release note "Agentforce Platform Enabled by Default" says the Agentforce platform is enabled for every org with Agentforce access granted by SKUs, licensing and editions. New orgs are enabled at creation. Existing orgs were enabled on a rolling basis from the first week of September 2026. Removing the Agentforce setting from the Agentforce Agents page in Setup is planned for later in Winter '27, and the note says there is no additional cost and no billing change.

Two details matter more than the headline. The only off switch the note names is the Einstein setting on the Einstein Setup page. And enabling the platform does not activate any agent: an agent reaches end users only when someone activates it in Agentforce Builder, and users other than admins need the Manage AI Agents permission to build.

The same default-on pattern appears elsewhere. Automated field updates for Agentforce Pipeline Management auto-enable from November 14 through November 16, 2026, for orgs with the Agentforce for Sales licence and at least 10 call transcripts. Agent Memory is generally available, with an org-wide switch to turn conversational memory off.

What to do: write an agent activation policy now, decide who holds Manage AI Agents, and tell sales managers what Pipeline Management will suggest before their reps see it. Our news coverage of the auto-enable rollout has the timeline.

2. Agent Orchestration Goes GA, Then Goes Cross-Vendor

Multi-Agent Orchestration is generally available. You build an orchestrator agent and connect other Agentforce agents in the same org as subagents, with variables mapped between them and an optional After Response section for inline actions. The practical effect is that small, specialized agents become the normal design. A billing agent, a shipping agent and a knowledge agent are each easier to test than one agent that knows all three jobs.

Salesforce's Top 10 adds Third-Party Agent Orchestration. Agentforce can orchestrate agents built on AWS, Azure, Google and other A2A-compliant ecosystems, or act as a subagent under someone else's orchestrator. We did not find a separate Help release note with configuration detail, so plan a proof of concept before you promise it in a design.

Testing keeps pace with composition. Agent Optimizer (Beta), the renamed assistant inside Agentforce Builder, runs simulated conversations to check its own suggested changes. Testing Center can generate tests with context variable values, and Draft History records every save as a draft you can restore.

Agents also became easier to move. From API 68.0, the AiAgentDefinition and AiAgentDefinitionVersion metadata types let Salesforce CLI retrieve an agent and its dependencies in one go. Managed packaging of agents is still not supported.

What to do: pick two existing agents with clear lanes and connect them under an orchestrator in a sandbox. You will learn more about delegation descriptions in an afternoon than from any slide.

3. Agent Skills, Plugins and the Coding Agent Toolchain

Salesforce's Top 10 says Agent Skills and Plugins launched with more than 100 prebuilt skills, and customers can author and publish their own to the same registry. Plug-ins bundle skills with MCP connectors, hooks and configuration. The first is the Salesforce Development plug-in for Claude Code, which can now discover more specialized plugins when a project needs them, with the developer approving each install.

For developers, the skills are already on GitHub. npx skills add forcedotcom/sf-skills installs curated skills for LWC, Flow and Apex into Claude Code, Codex or another compatible CLI, and Agentforce Vibes installs them automatically. Skills also cover sandboxes, scratch orgs, Dev Hub and package upgrades.

Salesforce paired the tooling with governance. Lifecycle Center, the new name for Next Generation DevOps Center, adds Governance (Beta): policies that apply to coding agents in Agentforce Vibes, mapped to checks such as Code Analyzer rules. And Salesforce's number one Top 10 item, Slack Code, brings coding agents into dedicated Slack channels where teams review diffs and live previews before shipping.

What to do: install the skills in one developer's environment, run them against a real backlog item, and decide which policies your coding agents must pass before anything merges.

4. MCP Runs Both Ways

Model Context Protocol is now an integration tier on Salesforce, inbound and outbound.

Salesforce hosts more servers. The Metadata Grounding MCP Server (Beta) gives AI clients permission-aware, read-only access to metadata across more than 60 types. The CRM Analytics MCP Server (Beta) lets Claude, Cursor, GitHub Copilot and ChatGPT query governed analytics data through an External Client App with OAuth and PKCE. Salesforce in Claude can now create and update records in beta, with Lightning field validation, for Claude Enterprise customers whose MCP Dispatch API setting is Needs Approval or Always Allowed. You can also create custom Salesforce-hosted MCP servers through the API Catalog Connect REST API, which is generally available.

Product teams joined in. The Data 360 MCP server can build and publish segments from a described audience, Marketing Cloud Engagement added 40 MCP server tools, and Salesforce CMS has read-only and write MCP servers for content.

Outbound, Agentforce Employee agents can call external MCP servers with each user's own OAuth credentials instead of a shared service user. Salesforce's platform blog adds MCP Risk Scores in Security Center, which rate every third-party MCP server Low, Medium or High and let admins block the risky ones.

What to do: inventory which AI tools your users already connect to Salesforce, then register approved MCP servers in API Catalog with per-user authentication. Treat an unregistered MCP connection the way you would treat an unregistered API key.

5. Flow Builder Gets Tests, History and Tags

Flow Test Mode began as a beta in September, and Help now lists it as generally available. Turn it on under Setup, Process Automation Settings, then build reusable scenarios with assertions for autolaunched and record-triggered flows. Mock outputs stand in for Action and Subflow elements, so a test no longer needs the real callout behind it.

Maintenance gets the same attention. Edit History shows every save of a flow version, lets you preview what changed, and restores a past save as a new version or a new flow. It needs Enterprise Edition or above. The Unused Resources filter lists every resource nothing references. Flow tags and categories, managed on the Tags tab of the Automation app, were pulled in September and re-added the week of November 2. Screen flows on mass quick actions run against the records a user selects in a list view or related list.

Two building aids round it out: Split by Field Value and Split by Date as Decision types, and a Collection Filter Criteria resource that finds a record in a collection without a Loop. Approvals improved as well, with a Request Approvals component that offers up to 10 flow approval processes on a record page. And a new run option, User Context - Enforces User Permissions, stops a flow from inheriting elevated access when Apex or another flow calls it from system context. One early preview item did not ship: the redesigned element search and categories panel was removed from the notes on September 14.

What to do: pick the three record-triggered flows you would least like to break and write Test Mode scenarios for them. Our Flow testing guide explains what these tests do and do not count toward.

6. The Authentication Deadlines

The least glamorous item on this list will cause the most outages if ignored.

  • December 1, 2026: every user who authenticates through SOAP login() needs the Use Any API Auth permission, enforced across production and sandboxes.
  • February 20, 2027: the OAuth username-password flow for connected apps retires, moved from Winter '27, along with the user-agent and hybrid user-agent flows.
  • Summer '27: SOAP login() retires in API versions 31.0 through 64.0, and connected apps stop receiving bug fixes and support.

Around those dates sit smaller changes that break quietly. Refresh tokens idle for 30 days now expire, enforced in production from November 4, 2026. The OAuth device flow works only with local External Client Apps from November 30, 2026. API traffic must use your My Domain login URL, with enforcement phased from October 2026 in sandboxes and January 2027 in production.

Identity changes reach email and sign-on too. The Maintain Your Email Verification Exception update, which replaced Adopt Authorized Email Domains, ends Support-granted exemptions from user email verification on December 1, 2026. Orgs that require single sign-on are migrated to a simpler configuration from January 7, 2027 in sandboxes and February 4, 2027 in production. Orgs that received MFA extensions now see their own enforcement dates in Setup.

What to do: query Login History for SOAP logins and username-password OAuth grants over the last 90 days, list every integration user, and migrate each to an External Client App with the web server flow with PKCE or the client credentials flow.

7. More Apex Heap and Real Integration Tests

Synchronous Apex heap rose from 6 MB to 10 MB and asynchronous heap from 12 MB to 25 MB, applied automatically. Nonproduction orgs get an "Enforce the Summer '26 Apex heap limit" setting for testing code that must still deploy to a production org on the old limit, and the higher limits apply everywhere in Spring '27.

Apex integration tests, a Developer Preview in scratch orgs, let tests call real HTTP endpoints and External Services through named credentials, using @IntegrationTest, @BeforeClass and @TearDown. The Apex Symbol API (Beta) exposes type information through a new Tooling API resource that Salesforce built partly to feed AI coding agents. Setup can now recompile only invalid classes and triggers instead of the whole org. Elastic limits extend to Batch Apex in beta, and packaged SOQL can resolve namespaces explicitly when a subscriber creates a field with the same name as yours.

What to do: delete one heap workaround in a preview sandbox and see whether your tests still pass. Our guides to the heap increase and integration tests go deeper.

8. AIforce, Microfrontends and a New In-Org IDE

On September 4, 2026, Headless 360 became AIforce, a top-level section of the release notes for Agentforce Vibes, Salesforce Multi-Framework and Salesforce MCP Servers. React and Angular apps built with Multi-Framework can now run as microfrontends inside Lightning pages and Experience Cloud pages through the lightning-ui-embedding base component, and Help removed the beta disclaimer the week of November 9. Embedding requires Hyperforce.

Two natural-language builders arrived in beta. Quick Pages builds a React-based page grounded in Salesforce data from a description, and Builder Central plans, builds and previews apps and agents, validating changes in an ephemeral preview org before they deploy to a sandbox.

Developers will notice a smaller change first. Developer Console is hidden by default and in maintenance mode, and Web Console, a browser IDE built on VS Code for Web, is the in-org replacement. Admins can switch Developer Console back on under Setup if a team still needs it. Next Generation DevOps Center also has a new name, Lifecycle Center, with a generally available migration from the DevOps Center managed package and validate-only deployments that let a promotion finish within 10 days without rerunning tests.

What to do: open Web Console in a sandbox before your developers find Developer Console missing, and confirm who holds the Web Console User permission.

9. Agentforce Contact Center Goes Global

Salesforce's Top 10 says Agentforce Contact Center, the fully native option with telephony, routing and AI in one product, now covers more than 30 countries. The release notes add Bring Your Own Carrier, automatic call recording redaction of card numbers and personal data, scheduled callbacks and an In-Queue Experience flow. The partner model got a new name: Salesforce Voice is now Partner Contact Center, for third-party contact centers such as Amazon Connect.

Partner Contact Center did not stand still. It adds Voicemail Drop with personalized greetings, self-service phone number assignment for reps, and an audit trail of voice call changes as a pilot. Agentforce Voice also changed behaviour: Auto-Hangup is now on by default, and Amazon Connect can transfer calls through real-time streaming without a dedicated number or SIP trunk.

Two more service items sit in Salesforce's Top 10. Autonomous Scheduling with Agentforce Voice books appointments around the clock and, by Salesforce's account, cuts 15-minute booking calls down to seconds. Adaptive Experiences and Dynamic Plans let the Service Rep Assistant listen to case and messaging conversations and update a resolution plan as the issue changes.

What to do: if a client runs Service Cloud Voice on Amazon Connect, map which features now live in Partner Contact Center and which only in Agentforce Contact Center before the next renewal conversation.

10. Sales Agents That Work From Call Data

Agentforce Sales, the new name for Sales Cloud, gets agents that turn conversation data into pipeline work.

  • Forecasting Agent analyses pipeline changes, flags deals that put quota at risk and helps reps complete forecast submissions. It began rolling out October 19, 2026, with the Agentforce for Sales add-on or Agentforce 1 Edition.
  • Deal Insights reads call transcripts, opportunity data and email signals to flag objections, competitor risk and engagement health. It rolled out in early November and is switched on through Salesforce Go.
  • Momentum captures meetings, emails and recorded calls, then delivers Executive Briefs in Slack, call coaching and Smart Clips of customer praise.
  • Pipeline Management auto-enables field update suggestions from call transcripts, as described in item 1.

The sales surface widened as well. Agentforce Sales runs inside Slackbot with Pipeline Management functionality, and Salesforce in Claude can create and update opportunities, contacts and other records in beta for Claude Enterprise customers. Agentforce Engagement, which handles lead outreach, now offers a pay per lead worked pricing option alongside pay per action.

What to do: confirm your call recording consent model covers how these agents use transcripts, then pilot Forecasting Agent with one sales team before rolling it out wider.

Also worth a look

A few items missed the ten but deserve a line. Tableau Knowledge builds knowledge graphs to ground agents in governed business context. Informatica Headless exposes Informatica's data management back end to coding tools and MCP clients. Agentic Segmentation and Activation builds audiences from plain language in Data 360. Agentic Commerce Search trains a small language model on each merchant's catalog, and Salesforce reports a 13% conversion lift in early results. Hyperforce on Google Cloud is generally available in North America from November 1, 2026. And Enable Profile Filtering is now enforced, so users see only their own profile name unless they hold View All Profiles.

What this release means

Winter '27 moves Salesforce from offering agents to assuming them. Agentforce is on by default, agents orchestrate other agents, MCP connects AI tools in both directions, and the developer toolchain expects a coding agent in the loop. Underneath, the platform keeps tightening identity, with three authentication dates between December 2026 and Summer '27 that will break integrations nobody remembers building.

Read the ten items as a sequence: govern the defaults first, then build on the new composition and tooling, then clear the authentication backlog before February 20, 2027. The role articles go deeper: Admins, Developers, Architects and Consultants. For the pillar-by-pillar walkthrough, read the Winter '27 release notes highlights.

Sources

Related dictionary terms

Read overall highlights →See Admins take →See Developers take →See Architects take →See Consultants take →

Practise it

Five questions on Administrator

Exam-style questions with an explanation after each one. No account needed, and your answers build a weak-topic map once you have one.