Top 10 Spring '26 Features

Spring '26 packs more than 200 features. Most of them are tactical. Ten are not. These are the items that change how your org is built, deployed, secured, or sold over the next six months. Pick the ones that apply to you, plot them on a sandbox roadmap, and ignore the rest until next release.

The ten that matter

1. Sales, Service, and Field Service rename to Agentforce. Sales Cloud becomes Agentforce Sales, Service Cloud becomes Agentforce Service, Field Service becomes Agentforce Field Service. Functionality is unchanged but every customer-facing artifact (decks, SOWs, training, dashboards, internal wiki) needs an audit. Plan two to four weeks of update work per major customer engagement.

1. Setup with Agentforce (Beta). A conversational agent inside Setup that creates custom objects and fields, manages user access from the Setup Audit Trail, generates flows directly in Flow Builder, and surfaces org-health metrics. Beta in 12 languages. Requires the Use Setup with Agentforce permission. The first credible challenger to point-and-click Setup since Lightning shipped.

1. Email-domain verification is mandatory. Every sending domain requires an active DKIM key or an Authorized Email Domains entry. Cutover dates: new domains added after Feb 25, 2026 verify immediately. Sandboxes enforce on Apr 14, 2026. Production enforces on May 4, 2026. This is the most-likely-to-break-production change in the release. Enable Use a substitute email address for unverified domains on the Deliverability Setup page as a safety net before the cutover.

1. Agentforce Vibes adds React app support. Multi-Framework (Beta) lets you build React apps with Vibes, deploy them to your org, and access them from the App Launcher on desktop or mobile. Data SDK + GraphQL handle record I/O. React Live Preview ships GA for single-LWC previews. The pattern Salesforce is signaling: Lightning is the platform, React is the runtime for greenfield UI.

1. Apex `RunRelevantTests` (Beta). A new Apex test level that analyzes the deployment payload and runs only the tests that touch the changed code. Annotate test classes with @IsTest(critical=true) to always run, or @IsTest(testFor='ApexClass:Foo') to bind tests to specific components. Supported by sf project deploy start --test-level RunRelevantTests, the Metadata API, and the REST deployRequest resource. Long deploys are about to get short.

1. Apex cursors and pagination cursors are GA. Cursor.fetch() lets queueable jobs handle batch-Apex-class workloads with variable batch sizes, capped at 100 million cursor rows per 24 hours. The new PaginationCursor class drives multipage UIs. @AuraEnabled methods accept and return cursors. The first real alternative to Batch Apex in years.

1. TLS certificate lifespans are shrinking. From the current 398-day cap to 200 days on Mar 15, 2026, 100 days on Mar 15, 2027, and 47 days on Mar 15, 2029. Salesforce will also stop publishing rotation announcements via the Trailblazer Community on a yet-to-be-announced date (90+ day notice). Audit every mTLS endpoint, integration, and custom domain. Stop using certificate pinning. Automate rotation now or you will be paged later.

1. Connected app creation is disabled by default. All new orgs require External Client Apps instead. SAML connected apps must migrate. AppExchange partners must follow new security requirements for both connected apps and ECA solutions. Existing connected apps continue to work, but a migration path is now homework, not optional.

1. Salesforce Functions is retired for new purchase and renewal. Migrate workloads to Heroku, MuleSoft, External Services, or Apex callouts. If you have a Functions-backed integration in production, this is a top-of-stack architectural item for the next quarter.

1. Hyperforce expands to 17 countries with IPv6 on the horizon. New Data 360, Marketing Cloud, Platform, MuleSoft, and Tableau regions in Italy and Sweden. Hyperforce public IP ranges now include inbound addresses. IPv6 rolls out starting in Government Cloud (early 2026, with 60-day notice for each subsequent stage). Plan dual-stack allowlists or move to domain allowlists or SNI before your firewall team gets surprised.

What to pilot first

Pick by team. Customer-facing teams get the rebrand audit. Security and platform teams get the certificate and email-verification roadmap. Dev teams pilot RunRelevantTests and React Vibes in scratch. Sales teams test one of the four new Agentforce Sales agents in a sandbox. Everything else can wait for the next release.