Loading
Prepare for Email to Become the Default Login ExperienceRead More
Set Up and Maintain Your Salesforce Organization
Considerations for Salesforce Edge Network

Considerations for Salesforce Edge Network

Learn how to maintain access to your custom domain during the move to Salesforce Edge Network.

Required Editions

Available in: both Salesforce Classic and Lightning Experience
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions

Understand the Exceptions in URL Routing

When your org adopts Salesforce Salesforce Edge Network, your My Domain URLs are routed through it. However, review these exceptions.

  • URLs that contain your Salesforce instance name.
  • URLs associated with custom domains, such as https://www.example.com, that serve your org’s Salesforce sites or Experience Cloud sites and don’t use the HTTPS option: Serve the domain with your HTTPS certificate on Salesforce servers.
  • Salesforce sites and Experience Cloud sites with domains ending in .force.com.
  • URLs associated with Customer 360 Data Manager that end with .admin.salesforce-hub.com and .my.salesforce-hub.com.
  • URLs associated with Live Agent Chat that end with .my.salesforcescrt.com.
  • URLs associated with untrusted content domains.
  • URLs associated with orgs in Government Isolated Architecture (GIA) data centers.

Route Custom Domains Through Salesforce Edge Network

All your custom domains that serve your Experience Cloud, Digital Experiences, or Salesforce sites, such as https://www.example.com, can route through the Salesforce Edge Network. Review what’s needed to maintain domain availability based on your domain configuration option.

  • With the Serve the domain with your HTTPS certificate on Salesforce servers option, Salesforce automatically manages HTTPS delivery and routing for your domain by using Salesforce Edge Network. To determine whether your qualifying custom domain uses Salesforce Edge Network, inspect the domain’s HTTP response headers or resolve the domain name to look for references to edge.
  • With the Use a third-party service or CDN to serve the domain option, the routing path uses a third-party CDN. Work with your third-party provider to update the target host name. If you don’t update the target host name, your domain doesn’t get the always-on threat protection provided by Salesforce Edge Network. Third-party services use a target hostname to point your domain to your org. To find the target host name for your custom domain, from Setup, in the Quick Find box, enter My Domain, and then select My Domain. Select the custom domain. On the Domain Detail page, review the Target Hostname.Work with your third-party provider to update the target host name. If you don’t update the target host name, your domain doesn’t get the always-on threat protection provided by Salesforce Edge Network.

Routing Considerations for Sandboxes

Review how sandbox refreshes and environment inheritance affect your Salesforce Edge Network routing configurations.

  • Because the org ID changes, a sandbox refresh disables Regional routing. If your production org uses Regional routing, re-enable it from the My Domain Setup page after every refresh. To know more about Regional Routing, see Route My Domain Through Salesforce Edge Network.
  • If Global Selective Routing is required for custom domains, enable it in the production org before creating or refreshing associated sandboxes. Sandboxes inherit the production org’s routing settings for custom domains. To know more about Global Selective Routing, see Route My Domain Through Salesforce Edge Network.
 
Loading
Salesforce Help | Article