Security & access

Salesforce Spring '27 release updates: the admin checklist, in deadline order

By the orgadmin.ai team8 min read

Spring '27 arrives in production orgs in early 2027, but two of its release updates do not wait for it. Salesforce enforces the OAuth device flow restriction on 30 November 2026 and both the SOAP login() permission and the email verification exception changes on 1 December 2026. If an integration depends on any of them, it stops working in the next two weeks, release weekend or not.

This checklist lists every release update we could confirm in Salesforce's release notes as due before or with Spring '27, sorted by deadline, with what breaks and how to check your org. To find your org's actual Spring '27 upgrade date, search your instance or My Domain on Trust Status and open the Maintenance tab.

The deadlines at a glance

DeadlineRelease updateWho is affected
30 Nov 2026Restrict the OAuth 2.0 device flow to local External Client AppsAnything using the device flow through a connected app or packaged app
1 Dec 2026Assign Use Any API Auth for SOAP login()Integrations and users that log in with SOAP login()
1 Dec 2026Maintain Your Email Verification ExceptionOrgs where Salesforce Support turned off email verification for a domain
Spring '27Async sharing recalculation after group and role changesLarge-data orgs with ownership skew and code that expects shares immediately
Spring '27Remove non-public fields from Aura action responsesCustom Aura/Lightning components reading undocumented fields
Spring '27View Setup Audit Trail permissionNew profiles and permission sets that need audit trail access
Spring '27Conceal personal information fields from guest usersExperience Cloud sites with guest access
Spring '27Roll back platform event trigger transactions on unhandled exceptionsPlatform event Apex triggers
Spring '27Salesforce to Salesforce fully retiredOrgs still sharing records with S2S
Spring '27Salesforce Connect cross-org adapter legacy auth retiredCross-org external data sources using password or OAuth auth
20 Feb 2027OAuth username-password and user-agent flows retiredIntegrations still using grant_type=password or the user-agent flows

Every one of these appears in Setup → Release Updates, where most have a test-run option. Start there: an update that is not listed in your org usually does not apply to it.

Before the release: 30 November and 1 December 2026

1. OAuth device flow, only for local External Client Apps (30 Nov)

The device flow is meant for things with no keyboard, such as smart TVs, kiosks and IoT devices. From 30 November it works only for local External Client Apps whose callback URL is one of: https://localhost, a custom URL scheme, your My Domain, a custom domain configured in Setup, or a Salesforce domain.

What breaks: the device flow through connected apps, through packaged External Client Apps, and through local ones whose callback URL doesn't qualify.

What to do: find who uses the device flow (Login History is the place to look, and it only keeps about six months, so a rarely used device may not show). For each one, create a local External Client App that meets the callback rule and move the device to it. Connected apps have no path to keep using the device flow.

2. SOAP login() needs Use Any API Auth (1 Dec)

From 1 December 2026, every user who authenticates with the SOAP API login() call needs the Use Any API Auth permission, in every org and every environment, sandboxes included. Without it, the login fails.

What to do: check Login History for SOAP logins, then assign the permission through a permission set to the integration users who need it. Treat that as a stopgap: login() itself is being retired in later releases. Our Winter '27 security checklist covers the follow-on retirement dates.

3. Email verification exceptions move to authorized email domains (1 Dec)

This one affects only orgs where Salesforce Support once turned off user email verification for a domain. If that is you, the Maintain Your Email Verification Exception update is on your Release Updates page.

What breaks: on 1 December Salesforce removes those old domain allowlists. Users whose email or return address isn't verified can no longer send email from Salesforce, and address changes only take effect after the user confirms the new address.

What to do: set up authorized email domains in Setup and use the new Require Address Verification to Send Email field to keep your exception. If you turned on the deliverability setting that uses DKIM keys to skip verification, Salesforce recommends moving to authorized email domains and turning that setting off.

With Spring '27

4. Sharing recalculation becomes asynchronous after group and role changes

To speed up large group and role changes, Salesforce now recalculates some sharing in the background. Salesforce says this affects your org only if all three are true: large data volumes with heavy ownership skew (for example one user owning hundreds of thousands of records of one object), Apex or flows that change group membership or roles, and code that expects the new share records to exist straight away.

What to do: if that describes you, search your Apex and flows for role and group changes followed by queries on share objects or record access, and test them in a sandbox with the update on.

5. Aura actions stop returning non-public fields

Records returned by Aura actions will no longer include internal system fields that are not part of the public API. Documented system fields such as Id, CreatedDate and all custom fields are unaffected; if a field is in the object's describe, it's safe.

What to do: turn the update on in a sandbox and click through your custom Lightning pages and components. Missing data or JavaScript errors point to a component reading an undocumented field.

6. A dedicated View Setup Audit Trail permission

Setup Audit Trail gets its own permission. Salesforce adds it automatically to every profile and permission set that already has View Setup, so existing access is preserved. The catch is new profiles and permission sets: grant it explicitly to auditors and support staff who need it.

7. Conceal personal information fields from guest users

Guest users on Experience Cloud sites get their own field set, Guest_PersonalInfo_EPIM, separate from the one used for logged-in portal users. That lets you hide more personal fields from anonymous visitors without changing what customers see after logging in.

What to do: review which user fields your public pages actually need, configure the guest field set, and test the site logged out. It requires Enhanced Personal Information Management (EPIM) and Digital Experiences to be on.

8. Platform event triggers roll back on unhandled exceptions

Today, a platform event trigger that throws an unhandled exception can leave partly written records behind. After Spring '27 the whole transaction rolls back.

What to do: look for platform event triggers that rely on partial work being saved, for example writing an error log record and then throwing. Catch the exception, or log through a separate mechanism.

9. Salesforce to Salesforce stops working

S2S has been frozen since Spring '26. In Spring '27 it is fully retired in all orgs. Salesforce points to Partner Cloud, Data Cloud One, MuleSoft Anypoint or MuleSoft for Flow as replacements. If any record sharing still runs on S2S, it needs a replacement live before your upgrade date.

10. Salesforce Connect cross-org adapter: legacy auth retired

The password and OAuth authentication options for the cross-org adapter depend on SOAP login() and are retired in Spring '27. Move each cross-org external data source to named credentials.

And the one right after: 20 February 2027

The OAuth username-password flow and the user-agent / hybrid user-agent flows are retired on 20 February 2027. That is a separate deadline but the same audit: find every integration that logs in the old way. We wrote a full guide: OAuth username-password flow retirement.

How to work through the list

  1. Today: open Setup → Release Updates in production and note which of these are listed. Anything that isn't listed probably doesn't apply.
  2. This week: handle the 30 November and 1 December items. Assign Use Any API Auth to integration users and move device-flow apps.
  3. Before your sandbox preview: turn each Spring '27 update on in a full or partial copy sandbox and run your Apex tests, key flows and a smoke test of your Lightning pages and Experience sites.
  4. Before release weekend: activate the tested updates in production outside working hours, with someone watching integration errors and a note of how to undo what can be undone.

Three of these changes are about who and what can log in to your org: the device flow, SOAP login() and the OAuth flow retirements. They are a good prompt for a wider look at your integrations. A security review lists OAuth tokens held by deactivated users, tokens unused for 90 days, connected apps with broad scopes and integration users with admin rights, and the SOQL Assistant can query Login History directly when you need to see which integration still uses an old login method.

Try it on your own org

orgadmin.ai puts an AI assistant, a security review and 21 more tools on your Salesforce org. 14-day free trial, no credit card.

Start free trial