Skip to main content

To ensure customers have adequate time to prepare, test, and make necessary adjustments for enhanced domains, the deployment timeline for this feature changed. The new timeline is as follows:

 

  • Spring ’23: Enhanced domains deployed in all orgs that don’t have enhanced domains deployed, with options to opt-out & disable the feature. 
  • Summer ’23: Enhanced domains deployed in all orgs that don’t have enhanced domains deployed, with an option to disable the feature.
  • Winter ’24: Enhanced domains enforced in all orgs.

 

For additional timeline details, see Enhanced Domains Timeline in Salesforce Help. (Tip: If you get a 404 error, clear your browser’s cache or open the link in an incognito window.)

 

Important: Because many browsers block third-party cookies by default, Salesforce will adhere to the new enforcement timeline, even if some browsers further delay their plans to fully block third-party cookies.

 

Actions Required

Because enhanced domains affect all application URLs, we recommend that you test and deploy enhanced domains before they’re automatically deployed in your orgs in the Spring ’23 release. For guidance on how to plan for this change and example checklists, see Plan for a My Domain Change in Salesforce Help.

 

If you need additional time to prepare for the deployment of enhanced domains, follow the steps in the Opt Out of the Automatic Deployment of Enhanced Domains in Spring ’23 Knowledge Article before your org gets Spring ’23.

 

Additional Resources

If you have questions after you view the webinars and review the documentation, you can post in this Trailblazer Community group or  sign up for Enhanced Domains Office Hours.

4 respuestas
  1. 7 nov 2022, 21:43

    @Elaine Rose Perfect thanks! I was just preparing some material on this for our crew so updated timeline is appreciated and I'll keep a link to that page for reference.

0/9000