Enable Enhanced Domains
  • 26 Apr 2023
  • 1 Minute to read
  • Contributors
  • Dark

Enable Enhanced Domains

  • Dark

Article Summary


Enhanced domains are the next version of My Domain. My domain replaces the standard sub domain in the URL of your Salesforce Org with your company-specific sub domain including URLs for your Experience Cloud sites, Salesforce Sites, Visualforce pages, and content files.

Do I need enhanced domains?

Salesforce is requiring customers to use enhanced domains by Winter ’23 release to comply with the latest browser and security standards.

How do I enable enhanced domains?

Enhanced domains affect all application URLs, testing in a sandbox before deployment is recommended and should be done before Winter ’23 release, starting in August 2022 for sandboxes and October 2022 for production orgs.

Reference: https://help.salesforce.com/s/articleView?id=sf.domain_name_enhanced.htm

  1. Access Setup from Salesforce and select My Domain.
  2. Select Edit under My Domain Details.
  3. Select the checkbox: Use enhanced domains.
  4. Click Save.

If you don't see the Use enhanced domains option, your org doesn't qualify for enhanced domains.

What if I do not enable the enhanced domain?

If enhanced domains aren't deployed before the Winter ’23 release, Salesforce will automatically set one for you based on your org’s ID.

Points to Consider in ARM

Before you perform any deployment or CI activities in ARM, make sure you reauthenticate your registered org via the Salesforce Org Management page. Reauthentication will update the most recent org changes.

Use Cases

Query 1: How is the backup request ID hitting the redirect URL successfully while deployment on the other hand is failing (before Salesforce Org is reauthenticated to update the URL under ARM)?

Answer: The deployment is carried out on the agent side based on the configured CI job, and the backup is carried out on the ARM server side with an updated refresh token. The Salesforce Org's redirection was modified during this process, and because the re-authentication was not yet complete, the deployment failed.

Solution: Once Salesforce Org has been reauthenticated, save the job again.

Query 2: If considered the possibility of just the build package being backed up, why is the deployment log referencing to the target org?

Answer: Backup is packaged from the target org only for the deployable components.

Was this article helpful?

What's Next