The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

What is being enforced or retired, and when, from the official release notes.

In your calendar: subscribe, or download the file. Each update falls on its day and each release on its dates; a date that moves here moves there.

Due soonWithin 30 days. Each is set out in full below.

Winter '27Dates not yet announced · first deadline in 9 days

1 Dec 2026 · in 9 days

Assign Use Any API Auth permission for SOAP login() (opens in a new tab)

To authenticate with the SOAP API login() operation, all users must have the Use Any API Auth user permission assigned to them. Users without the Use Any API Auth user permission can no longer authenticate with SOAP API login() and will encounter an error.

What to do Assign the Use Any API Auth permission to every user who calls SOAP API login(), since users without it will get an error.

In the paper: Spring '27 release updates that need testing before enforcement, part one, Winter 27 release brings Headless Toolkit, Multi Framework support, and Data SDK extensions

Enable accessibility enhancements for cards, docked containers, menu lists, and panels (opens in a new tab)

To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of cards, docked containers, menu lists, and panels when viewed at high magnification. This release update is dependent on the Enable Accessibility Enhancements for Page Headers and Modal Windows When Zoom Is Greater Than 200% release update.

What to do Test cards, docked containers, menu lists, and panels at high magnification (above 200% zoom) in Lightning Experience to confirm they behave correctly.

Enable accessibility enhancements for date pickers, popovers, bottom utility bars, record headers (opens in a new tab)

To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of date pickers, popovers, bottom utility bars, and record headers when viewed at high magnification. This release update is dependent on the Enable Accessibility Enhancements for Page Headers and Modal Windows When Zoom Is Greater Than 200% release update.

What to do Test date pickers, popovers, bottom utility bars, and record headers at high magnification (above 200% zoom) in Lightning Experience.

Enable accessibility enhancements for page headers and modal windows when zoom is greater than 200% (opens in a new tab)

To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of page headers and modal windows when viewed at high magnification. This is the beginning of our effort to comply with WCAG 2.2 Resize and Reflow guidelines.

What to do Test page headers and modal windows at zoom levels above 200% in Lightning Experience, since this is the first step toward WCAG 2.2 compliance.

Enable Profile Filtering (opens in a new tab)

To improve the security of your Salesforce org, the Profile Filtering setting is enabled by default. Profile filtering prevents users from viewing profile names other than their own unless they’re assigned the View All Profiles permission.

What to do Confirm which users need the View All Profiles permission, since profile names will otherwise be visible only to each user's own profile.

Before Spring '27Any time before Spring '27 arrives · Sandboxes 6 Feb 2027 · Production 19 to 20 Feb 2027 · first deadline in 8 days

30 Nov 2026 · in 8 days

Restrict the OAuth 2.0 device flow to local External Client Apps (opens in a new tab)

To secure the OAuth 2.0 device flow, Salesforce is restricting this flow to local external client apps with a localhost callback URL. To prepare for this change, review your usage of the device flow and update your connected apps and external client apps to meet the new criteria.

What to do Review any use of the OAuth 2.0 device flow and update Connected Apps and External Client Apps to use a localhost callback URL before Spring '27.

In the paper: Spring '27 release updates that need testing before enforcement, part one, Winter ’27 release guides architects through security enforcement and agent scaling

1 Dec 2026 · in 9 days

Maintain your email verification exception (opens in a new tab)

If you previously disabled user email verifications through Salesforce Customer Support, configure an authorized email domain setting to maintain your exception and to preserve your users' ability to send email. When this release update is enforced, Salesforce removes the existing domain allowlists that disable email verification.

What to do Configure an authorized email domain setting before Spring '27 to keep your email verification exception and preserve users' ability to send email.

In the paper: Spring '27 release updates that need testing before enforcement, part one

Finish preparing for MFA enforcement for all employee users (opens in a new tab)

Changed 8 Nov New to the notes, filed under "Scheduled To Be Enforced Before Spring ’27".

To help protect your org from security threats such as phishing, credential stuffing, and account takeovers, Salesforce requires multi-factor authentication (MFA) for all employee logins, including direct UI and Single Sign-On (SSO). This release update applies only to orgs that received an extension for MFA enforcement.

What to do Enable multi-factor authentication for all employee logins before Spring ’27 enforcement.

In the paper: Rolling out multi-factor authentication across a Salesforce org in stages, How Salesforce Guardian's AIforce security tools govern admin and agent access, Salesforce confirms MFA enforcement timelines and extension options for administrators

Finish preparing for MFA enforcement for previously Exempt Users (opens in a new tab)

Changed 8 Nov New to the notes, filed under "Scheduled To Be Enforced Before Spring ’27".

To help protect your org from security threats such as phishing, credential stuffing, and account takeovers, Salesforce requires multi-factor authentication (MFA) for all employee logins, including direct UI and single sign-on (SSO). This release update applies only to orgs that received an extension to use the “Waive Multi-Factor Authentication for Exempt Users” permission.

What to do Remove the waive multi-factor authentication permission and enforce MFA for exempt users.

In the paper: Rolling out multi-factor authentication across a Salesforce org in stages, How Salesforce Guardian's AIforce security tools govern admin and agent access, Salesforce confirms MFA enforcement timelines and extension options for administrators

Finish preparing for phishing-resistant MFA enforcement for privileged users (opens in a new tab)

Changed 8 Nov New to the notes, filed under "Scheduled To Be Enforced Before Spring ’27".

To help protect your org's most privileged accounts from phishing and account takeover risks, Salesforce requires phishing-resistant multi-factor authentication (MFA) for users with the System Administrator profile or privileged permissions. This release update applies only to orgs that received an extension for phishing-resistant MFA enforcement.

What to do Configure phishing-resistant multi-factor authentication for system administrators before Spring ’27.

In the paper: Threat actors are using the ARTEX framework against Salesforce orgs; here is how to defend

Finish preparing for step-up authentication enforcement on report exports (opens in a new tab)

Changed 8 Nov New to the notes, filed under "Scheduled To Be Enforced Before Spring ’27".

To help protect your org's data from unauthorized exfiltration, Salesforce requires users to complete a step-up authentication challenge when they export reports. This release update applies only to orgs that received an extension for step-up authentication enforcement.

What to do Implement step-up authentication challenges for all report exports before Spring ’27.

In the paper: Working around the 2,000-row cap on report exports after step-up authentication, Threat actors are using the ARTEX framework against Salesforce orgs; here is how to defend

Spring '27Sandboxes 6 Feb 2027 · Production 19 to 20 Feb 2027 · in 3 months

20 Feb 2027 · in 3 months

OAuth user-agent and hybrid user-agent flows retirement (opens in a new tab)

Salesforce is retiring the OAuth user-agent flow and the OAuth hybrid user-agent flow. For better security, update your integrations to use the OAuth web-server flow or hybrid web-server flow with the Proof Key for Code Exchange (PKCE) extension.

What to do Update integrations that use the OAuth user-agent or hybrid user-agent flows to use the web-server or hybrid web-server flow with PKCE before Spring '27.

20 Feb 2027 · in 3 months

Retirement of OAuth 2.0 username-password flow for Connected Apps (opens in a new tab)

When this release update is enforced, we'll stop supporting the OAuth 2.0 username-password flow for connected apps. This update will break all connected app integrations that use this flow.

What to do Move Connected App integrations off the OAuth 2.0 username-password flow before Spring '27, since those integrations will break when it is retired.

In the paper: Spring '27 release updates that need testing before enforcement, part one, Salesforce retires the OAuth username password flow and guides migration to client credentials

Conceal personal information fields from Guest users (opens in a new tab)

Set field visibility for guest users without affecting your settings for other external users. Turn on Independent Guest Field Masking to hide certain fields specifically from guest users.

What to do Turn on Independent Guest Field Masking and set field visibility so personal information is hidden from guest users without changing other external users' settings.

In the paper: Spring '27 release updates to Test before enforcement, part two

Enable accessibility enhancements for To Do lists and Lightning dual listboxes when zoom is greater than 200% (opens in a new tab)

To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of To Do lists and Lightning dual listboxes when viewed at high magnification. This is part of our effort to comply with WCAG 2.2 Resize and Reflow guidelines.

What to do Test To Do lists and Lightning dual listboxes at zoom levels above 200% in Lightning Experience before Spring '27 enforcement.

In the paper: Spring '27 release updates that need testing before enforcement, part one

Remove non-public fields from Custom Object data in Aura action responses (opens in a new tab)

To improve security, Salesforce is removing non-public system fields from custom object data returned in Aura action responses. This update filters out internal system fields that aren’t part of the public Salesforce API.

What to do Check Aura components that rely on non-public system fields in Custom Object data, since those fields will be removed from action responses in Spring '27.

In the paper: Spring '27 release updates that need testing before enforcement, part one

Render Visualforce Pages as Accessible (Tagged) PDFs (Beta) (opens in a new tab)

With this update enabled, Visualforce pages rendered with renderAs="pdf" use the accessible PDF rendering engine, which produces tagged PDF/UA output. Tagged PDFs include the document structure and metadata that assistive technologies such as screen readers rely on.

What to do Evaluate Visualforce pages that use renderAs="pdf" in the beta accessible PDF rendering engine to produce tagged PDF/UA output before Spring '27.

Roll back Platform Event trigger transactions on unhandled exceptions (opens in a new tab)

This update rolls back the transaction of a platform event Apex trigger when it throws an unhandled exception, so that partially written records are no longer committed.

What to do Review Platform Event Apex triggers for unhandled exceptions, since their transactions will roll back instead of committing partial records in Spring '27.

In the paper: Spring '27 release updates to Test before enforcement, part two

Salesforce to Salesforce is being retired (opens in a new tab)

Salesforce to Salesforce is being retired in Spring ’27. Salesforce has more powerful and integrated solutions that align with modern business needs.

What to do Plan a migration away from Salesforce to Salesforce before Spring '27, since the feature is being retired.

In the paper: Choosing replacements for Salesforce to Salesforce before its Spring '27 retirement, Spring '27 release updates that need testing before enforcement, part one, Winter ’27 release guides architects through security enforcement and agent scaling

Update Apex code and flows for changed sharing recalculation behavior (opens in a new tab)

To optimize performance after large-scale updates to groups or roles, Salesforce now performs some sharing recalculations asynchronously. If Apex code and flows require that share records be updated immediately, the code and flows can break when this release update is enforced.

What to do Review Apex code and flows that need share records updated immediately after group or role changes, and make them handle asynchronous sharing recalculation.

Update instanced URLs in API traffic (opens in a new tab)

To prevent disruption when Salesforce ends support for API traffic that uses an incorrect instanced URL, make sure that API traffic to your org uses the org’s My Domain login URL. First available in Summer ’25, this release update was scheduled to be enforced in Spring ’26, but we postponed enforcement to a phased schedule that starts in October 2026 in sandboxes and January 2027 in production.

What to do Update API traffic to use the org's My Domain login URL instead of incorrect instanced URLs, starting with sandboxes in October 2026 and production in January 2027.

View Setup Audit Trail permission to access Setup Audit Trail (opens in a new tab)

Control access to Setup Audit Trail with the dedicated View Setup Audit Trail permission. Admins can provide access without granting the broader View Setup permission, supporting the principle of least privilege.

What to do Assign the View Setup Audit Trail permission to users who need Setup Audit Trail access, instead of granting the broader View Setup permission.

In the paper: Spring '27 release updates to Test before enforcement, part two

Summer '27Dates not yet announced

Block Apex anonymous code execution from managed packages (opens in a new tab)

To strengthen subscriber org security, block managed package session IDs from authenticating anonymous Apex code. If you enable this update, installed managed packages can no longer use UserInfo.getSessionId() to obtain a session ID and then use the session ID to execute anonymous Apex.

What to do Check that installed managed packages do not rely on UserInfo.getSessionId() to run anonymous Apex, since this will be blocked in Summer '27 if enabled.

Optimize performance for revenue management (opens in a new tab)

This update optimizes the Configuration API to speed up processing times in Product Configurator. Enable the test run in a sandbox environment to confirm that the optimizations work with your setup.

What to do Enable the test run in a sandbox to confirm the Configuration API optimizations work with your Product Configurator setup before Summer '27.