Salesforce My Domain Considerations
Plan Your My Domain Change
Whether you change your My Domain to update your brand or to adopt enhanced domains, the URLs that Salesforce hosts for your org change. These changes require planning, coordination, and testing. For high-level steps, recommendations, and checklists, see Plan for a My Domain Change in Salesforce Help.
Logging In with a My Domain
Your users can log in to your org with its My Domain URL.
Alternatively, users can use these methods to log in to Salesforce.
https://login.salesforce.com, unless an admin prevents logins through the My Domain policies options.
Your org’s instance URL, such as https://InstanceName.salesforce.com/, unless an admin prevents logins through the My Domain policies options.
My Domain in Non-Production Orgs
My Domain URL formats differ in sandboxes and Developer Edition orgs. My Domain URLs in a Developer Edition org end in dev-ed.my.salesforce.com, and sandbox URLs include the sandbox name.
If enhanced domains are enabled and deployed, sandbox URLs include the sandbox name and the word “sandbox.” If partitioned domains are enabled and deployed in a Developer Edition org, free org, patch org, scratch org, demo org, or Trailblazer Playground, that org’s URLs contain the partition name.
Because of the difference between production and sandbox My Domain login URLs, a sandbox org and production org can have the same My Domain name. So you can set your sandbox org to use the same My Domain name as your production org without causing any conflicts.
My Domain and Sites Subdomains
With enhanced domains, your My Domain name is used as the subdomain for URLs across your org, including Salesforce Sites and Experience Cloud sites.
If enhanced domains aren’t enabled and deployed in your org, your My Domain subdomain isn’t used for Experience Cloud sites or Salesforce Sites. You specify separate subdomains when you set up those features.
For more information, see My Domain URL Formats.
NOTE To use a custom domain such as https://www.example.com to serve your org’s Salesforce Sites and Experience Cloud sites, see Manage Your Domains.
Redirections After a My Domain Change
Each time that you deploy a change to your My Domain details, Salesforce redirects your previous My Domain hostnames to the hostnames for your current My Domain unless you disable those redirects. However, if you change your My Domain more than one time, only the last set of My Domain URLs for your org are redirected. To see if redirects are in place for a previous My Domain, check the Routing section of the My Domain page. For more information, see My Domain Redirections in Salesforce Help.
Revert a My Domain Deployment
After you save a My Domain change, you can cancel your request before deploying the new domain. On the My Domain Step 3: Deploy New Domain screen, click Cancel New Domain.
To revert to your previous My Domain hostnames after you deploy a My Domain change, repeat the steps to change your My Domain. Review and follow the high-level steps, recommendations, and checklists for a My Domain change, see Plan for a My Domain Change in Salesforce Help.
My Domain Rename and Service Cloud Voice
When you enable Service Cloud Voice, Salesforce uses your My Domain login URL to configure single sign-on (SSO) to Amazon Connect. Changing your org’s My Domain name or suffix breaks that configuration and disables Voice.
Also, if enhanced domains are enabled and deployed, renaming your My Domain changes your Visualforce page URLs. After you deploy the change, add your new Visualforce page format to the allowlist for Amazon Connect. For more information, see Update Your Org for My Domain Changes in Salesforce Help.
My Domain and Single Sign-On
For inbound SSO requests, My Domain URLs allow deep linking directly to pages in the org. No changes are required for the identity provider. The Salesforce SAML endpoint, login.salesforce.com, continues to work for SAML and OAUTH requests, even if you deploy My Domain and select Prevent login from https://login.salesforce.com in your My Domain Settings.
NOTE If you’re using external Chatter groups along with SSO for employees, users outside your company are redirected to a SAML identity provider that they can’t access. To get SSO to work, migrate external Chatter groups to Experience Cloud sites. Or to allow users to continue to log in through login.salesforce.com, don’t select the My Domain login policy, Prevent login from https://login.salesforce.com.
For information about updating authentication after your My Domain login URL or sites URL changes, see Update Authentication After a My Domain Change in Salesforce Help.
Enhanced Domains, Stabilized URLs, and Blocked Third-Party Cookies
Salesforce org URLs that don’t contain instance names are easier to remember and prevent disruption during org migrations. With enhanced domains, no Salesforce org URLs contain your instance name.
Enhanced domains are the latest version of My Domain that meets the latest browser requirements. To understand how enhanced domains help your org work with blocked third-party cookies, see Why Enhanced Domains in Salesforce Help. To understand when enhanced domains are deployed and enforced, see Enhanced Domains Timeline in Salesforce Help.
If enhanced domains aren’t enabled, many My Domain URLs, such as your login URL, don’t contain your Salesforce instance name. However, your Visualforce, Experience Builder, Site.com Studio, and content file URLs can contain the instance name. To remove the instance names from these URLs, enable and deploy enhanced domains.
Hyperforce and Stabilized My Domain URLs
To avoid instance names and your org’s Hyperforce location in your URLs, we recommend that you stabilize your My Domain URLs before moving to Hyperforce. To stabilize your URLs, enable enhanced domains or enable a My Domain setting. Otherwise, your My Domain URLs for content files, Experience Builder, and Visualforce pages include your Salesforce instance name and your Hyperforce location.
In a Hyperforce org without enhanced domains enabled, the My Domain setting, Stabilize Visualforce, Experience Builder, Site.com, and content file URLs, controls whether those URLs contain your Salesforce instance and your org’s Hyperforce location. If that setting is disabled, the URLs contain your instance name and sdfc-HyperforceLocation before the .force.com domain suffix. If the setting is enabled, instance names and your org’s Hyperforce location aren’t included in the URL.
For example, here’s the format of a Visualforce URL with the setting disabled: MyDomainName--PackageName.InstanceName.visual.sfdc-HyperforceLocation.force.com.
Here’s the format of a Visualforce URL in a Hyperforce org with the setting enabled: MyDomainName--PackageName.visualforce.com.
And here’s the format of a Visualforce URL in a Hyperforce org with enhanced domains: MyDomainName--PackageName.vf.force.com.
To simplify your org’s application URLs, we recommend that you enable and deploy enhanced domains before moving to Hyperforce.
Contact Summit Technologies for assistance implementing My Domain in your Salesforce org.