In Winter ’24 Salesforce, Salesforce will enforce enhanced domains for all orgs, therefore organisations need to take action to enable enhanced domains to avoid any potential disruption.
The first question you may have is why are enhanced domains a requirement? Salesforce advises that enhanced domains are the current version of My Domain that meets the latest browser requirements. Effectively they have increased levels of security for the existing My Domain standard.
With enhanced domains, all of the URLs across your org will contain your company-specific My Domain name. This includes Experience Cloud sites, Salesforce Sites, Visualforce pages and content files. The enhanced domains feature changes the domain suffix (i.e. the part after the My Domain name) to meet the latest security requirements.
Salesforce has provided a wealth of documentation around the enabling of enhanced domains, which for smaller organisations could be overwhelming. The process for smaller organisations should be far simpler, and as My Domain was made a requirement in the Winter ’22 release, its should be even easier, as URLs are likely to remain the same.
If you do not have an Experience Cloud Site, Salesforce Site, Visualforce pages or content files (or anything else on the Salesforce list), you can simply go to the My Domain page in the setup area and verify that your URL will remain the same once Enhanced Domains are enabled. There will be no impact to the Login URL, Lightning Pages etc – these will remain the same provided you do not change the My Domain or suffix.
For those of you with an Experience Cloud Site, Salesforce Site etc, Salesforce will automatically configure a redirect from your old URL to the new Enhanced Domain URL to minimalise impact. This will be in place until Winter ’25 (i.e. around October 2024), so this gives you plenty of time to ensure that links to your Experience Cloud on your website, for example, are updated and ready for that redirect to no longer function.
Now, if you lost me, don’t worry – I am going to walk you through the process of enabling enhanced domains.
Enabling Enhanced Domains
In Setup go to ‘My Domain’
Select Edit, this will open up more settings, check the ‘Use enhanced domains’ checkbox and leave the two URL Stabilization checkboxes checked.
You can now see the Current My Domain URL and Your chosen new My Domain URL with enhanced domains.
These match, therefore, I have no concerns over the enablement of Enhanced Domains.
Deploying Enhanced Domains
Salesforce will now start the registration and provisioning of the new domain.
Once this is complete you can select ‘Deploy New Domain’.
You will then be forced to log out and log back in – and if you go back to My Domain Settings, you will see enhanced domains is now enforced:
Do you have an Experience Cloud Site, Salesforce Site or anything else impacted by Enhanced Domains?
A full list can be found in Salesforce help, but for those of you with an Experience Cloud Site, Salesforce Site etc. will have a new domain to access those.
The change for Experience Cloud and Salesforce Sites are:
For example, for a change of Salesforce Sites: hazledenesolutions.secure.force.com would now be hazledenesolutions.my.salesforce-sites.com
Don’t forget: Salesforce will configure a temporary redirect, but you will want to ensure that these links are updated in the coming months so that they don’t stop working once this is removed.
Need to roll back?
If you need to roll back the move to enhanced domains, you can unselect the ‘Use enhanced domains’ checkbox, but please note, this cannot be done immediately as Salesforce may still be processing the initial change.
Note: If you want to change your My Domain Name or suffix, check out the Salesforce support documentation for further details and potential impact.
Final words and roll out approach
Finally, it goes without saying, there is a risk of not completing all of the checks that Salesforce provide when completing the rollout of functionality. However, the time and resources of exploring every avenue may not balance with the minimal risk for your users.
Salesforce would, for example, always urge you to complete this in the sandbox prior to production. Whilst I would usually agree with the approach, as the deployment in production is very clear on what change may occur, and sandboxes often do not have the links to active Experience Cloud sites (for example) for you to test, I would look at using a risk-based approach.
Our top tips would be:
- a) do it outside of hours to minimise any impact
- b) ensure you have an understanding of what might be impacted i.e. do you have an Experience Cloud or a Salesforce Site
- c) be ready to ‘rollback’ the change if needed (i.e. go back to not using enhanced domains)
From chatting with many Nonprofit consultants on this enablement, this is the approach they have used, and none have had any challenges. Please note, however, this should be completed at your own risk, and we are not liable should any challenges arise!
If you are a small nonprofit that requires support with this enablement, please contact us, we would be more than happy to assist you with this piece of work – however, please note, we will more than likely recommend this approach.