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.

Logging In with a My Domain

Users can log in to your org with your My Domain login 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.
  

  Note Salesforce doesn’t recommend instance URLs for logging in to Salesforce. Your instance name can change during regular maintenance, such as an instance refresh, or during a migration to the latest infrastructure, such as Hyperforce. And incorrect instanced URLs aren’t redirected starting in Spring ’26.

My Domain in Non-Production Orgs

My Domain URL formats differ in non-production orgs. All qualifying non-production orgs get partitioned domains, a feature that includes a word related to the org type in the URLs that Salesforce serves for that org. For example, URLs for developer edition orgs include the word develop and URLs for sandboxes include the word sandbox. Also, dev-ed is appended to the My Domain name in Developer Edition orgs. An example login URL for a Developer Edition org is https://mycompany-dev-ed.develop.my.salesforce.com.

With partitioned domains, a non-production org other than a Developer edition org and a production org can have the same My Domain name without causing any conflicts. For more information, see Partitioned Domains.

My Domain and Sites Subdomains

With enhanced domains, the latest version of My Domain, your My Domain name is used as the subdomain for URLs across your org, including Salesforce Sites and Experience Cloud sites.

For more information, see My Domain URL Formats.

Note To use a custom domain such as https://www.example.com to serve content from your org’s sites, see Custom 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 host names to the host names 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 Redirections section of the My Domain page. For more information, see My Domain Redirections.

Revert a My Domain Deployment

After you save a My Domain change, you can cancel your request before you deploy the new domain. On the My Domain Step 3: Deploy New Domain screen, click Cancel New Domain.

To revert to your previous My Domain hos names 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.

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 more information, see Set the My Domain Login Policy and Single Sign-On.

For information about updating authentication after your My Domain login URL or sites URL changes, see Update Authentication After a My Domain Change.

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, deploy enhanced domains.

Note Enhanced domains were enforced in Winter ’24. Only a limited number of orgs are using legacy My Domain without enhanced domains.

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 in a Hyperforce org with enhanced domains: MyDomainName--PackageName.vf.force.com.

Here’s the format of a Visualforce URL with the My Domain setting Stabilize Visualforce, Experience Builder, Site.com, and content file URLs disabled: MyDomainName--PackageName.InstanceName.visual.sfdc-HyperforceLocation.force.com.

And here’s the format of a Visualforce URL in a Hyperforce org with the My Domain setting Stabilize Visualforce, Experience Builder, Site.com, and content file URLs enabled: MyDomainName--PackageName.visualforce.com.

To simplify your org’s application URLs, we recommend that you enable and deploy enhanced domains before moving to Hyperforce.