Enhanced Domains Timeline

To check which release you’re running on and when you get the next release, see Get Your Org Status and Upcoming Maintenance Dates with My Domain.

Summary of Recent and Upcoming Releases

Here’s the timeline for this release and future releases. For more details, see the section for each release.

To prevent disruption for your customers and users, enable redirection logging and update all references to your previous non-enhanced domains.

For more information, including the specific host name formats for legacy (non-enhanced) host names, see Prepare for the End of Redirections for Non-Enhanced Domains.

Spring ’26: Legacy Host Name Redirections Stop

Spring ’26 deployment starts in January 2026 for production and demo orgs. In this release, Salesforce disables redirections for legacy (non-enhanced) host names in production orgs and demo orgs. With that enforcement, those redirections can’t be reenabled in any org.

Note The end of redirections for legacy (non-enhanced) host names is enforced through a release update. Release updates are completed gradually after the major release. Usually the enforcement processes finishes within a few hours after you get the release, but it can take up to 24 hours. To control the timing of when legacy host name redirections stop in your production or demo org, disable legacy host name redirections before your org gets Spring ’26.

Summer ’26: Testing Available for Incorrect Instanced URLs in API Traffic

Summer ’26 deployment starts in April 2026 for sandboxes and in May 2026 for production orgs. Starting June 19, 2026, you can test the end of support for instanced URLs in API traffic. In Setup, find and select My Domain, then enable Block API traffic that uses an incorrect instanced URL in the Redirections section of the My Domain page in Setup.

Warning If you enable “Block API traffic that uses an incorrect instanced URL” before the related known issue is resolved, SOAP login URLs via Visualforce pages can return a 400 Bad Request error. Salesforce plans to deploy a fix for that issue June 16–18, 2026, so we recommend that you test this change after June 18, 2026.

For more information, see End-of-Support Schedule for Incorrect Instanced URLs in API Traffic.

Winter ’27: Support Ends for Incorrect Instanced URLs in API Traffic

Winter ’27 deployment starts in August 2026 for sandboxes and in Septembmer 2026 for production orgs. Shortly after your org gets this release, API traffic that uses an incorrect instanced URL is no longer supported.

This change is enforced on a rolling basis. For specific dates, see End-of-Support Schedule for Incorrect Instanced URLs in API Traffic.

To control the timing of when API traffic that uses an incorrect instanced URL stops working in your org, disable that traffic before that change is enforced in your org. Disable the Block API traffic that uses an incorrect instanced URL My Domain setting.

Previous Releases and Milestones

• Winter ’26—Release deployment started in September 2025 for production and demo orgs. In those orgs , customers retained the ability to enable and disable redirections for legacy (non-enhanced) host names. To test that change in a sandbox, customers could create a sandbox from a production org with the “Redirect previous My Domain URLs to your current My Domain" My Domain setting enabled.

  Legacy host name redirections remained disabled in all other orgs. To prevent Salesforce from disabling legacy redirections with this release, customers could enable a My Domain setting before their org got that release.

  Also in this release, customers could test the end of support for instanced URLs in API traffic via a My Domain setting.

• Summer ’25—Release deployment started in May 2025 for production and demo orgs. In those orgs, customers retained the ability to enable and disable redirections for legacy (non-enhanced) host names. Legacy host name redirections remained disabled in all other orgs. To prevent Salesforce from disabling legacy redirections with this release, customers could enable a My Domain setting before their org got that release.

  Also in Summer ’25, Salesforce introduced the “Use Your Org’s My Domain Login URL in API Calls” release update, which is enforced in Summer ’26. With that release update, you can test disabling incorrect instanced URLs in API traffic.

• Spring ’25—Release deployment started in January 2025 for production and demo orgs. In those orgs, customers retained the ability to enable and disable redirections for legacy (non-enhanced) host names. Customers could prevent Salesforce from disabling legacy redirections when those orgs got Summer ’25. Legacy host name redirections remained disabled in all other orgs.
• Winter ’25—Release deployment started in August 2024 (sandboxes) and September 2024 (production). In this release, redirections for legacy (non-enhanced) domains stopped in sandboxes, Developer Edition orgs, patch orgs, scratch orgs, and Trailhead Playgrounds. Those redirections remained in place only for production and demo orgs.
• Winter ’24—Release deployment started in August 2023 (sandboxes) and September 2023 (production). In this release, the Deploy Enhanced Domains release update was enforced. With that enforcement, enhanced domains were deployed in all remaining orgs, and the feature can’t be disabled in any org.
• Summer ’23—Release deployment started in May 2023 (sandboxes) and June 2023 (production). With this release, Salesforce deployed enhanced domains in all orgs that didn’t have enhanced domains yet. Customers retained the ability to disable and enable enhanced domains in this release.
• Spring ’23—Release deployment started in January 2023 (sandboxes) and February 2023 (production). With this release, Salesforce deployed enhanced domains in all remaining orgs, including production orgs, unless you opted out of that deployment before the release. Customers retained the ability to disable and enable enhanced domains in this release.
• Winter ’23—Release deployment started in August 2022 (sandbox) and October 2022 (production). With this release, Salesforce deployed enhanced domains in sandboxes and non-production orgs unless you opted out before the release. Non-production orgs include Developer Edition, demo, free, patch, and scratch orgs, plus Trailblazer Playgrounds. Production orgs were unaffected. Customers retained the ability to disable and enable enhanced domains in this release.
• Summer ’22—In this release, enhanced domains were available in all orgs, including orgs without Hyperforce or Salesforce Edge Network. In June 2022, a few customer-specific orgs were the last group of orgs to get the ability to enable enhanced domains. Starting in early July 2022, enhanced domains were enabled by default in new orgs.
• Spring ’22—Release deployment started in January 2022 (sandboxes) and February 2022 (production). With this release, enhanced domains were available in all sandbox orgs except a few customer-specific sandboxes. For production orgs, enhanced domains were available in Hyperforce orgs and in orgs with a deployed My Domain routed through Salesforce Edge Network.
• Winter ’22—Release deployment started in August 2021 (sandboxes) and September 2021 (production). With this release, enhanced domains were available in Hyperforce orgs and in orgs with a deployed My Domain routed through Salesforce Edge Network, including scratch orgs and Developer Edition orgs.
• Summer ’21—Release deployment started in May 2021 (sandboxes) and June 2021 (production). With this release, enhanced domains were available in Hyperforce orgs and in orgs with a deployed My Domain routed through Salesforce Edge Network. They weren’t available in scratch orgs or in Developer Edition orgs.