--- schema_version: "1" id: 3253832b43bf991bc3e784d918d096515d9947ee1086fc1981a856bdd5b216bc title: My Domain Considerations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/domain_name_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.domain_name_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 57b43084c0003bf21d46b50824108b177359950b63a638d137487472dcd1e230 description: When you deploy a change to your My Domain, it’s important to understand the impact on URLs across your Salesforce org. Review these considerations about URL changes, feature testing, and reducing the impact to your users. products: - Salesforce Platform - Cross Cloud release: "264" --- # My Domain Considerations When you deploy a change to your My Domain, it’s important to understand the impact on URLs across your Salesforce org. Review these considerations about URL changes, feature testing, and reducing the impact to your users. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
## 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](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan.htm&release=264.0.0&type=5 "Whether you change your My Domain to update your brand, to adopt enhanced domains, or to enable partitioned domains, the URLs that Salesforce hosts for your org change. Those changes can have a large impact, and making the required updates can seem like a daunting project. To make the process as smooth as possible for you, your users, and your customers, review the high-level steps, the recommended practices, and how to reduce the impact on your users and customers."). ## 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_note.png) 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](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_partitioned_domains.htm&release=264.0.0&type=5 "With partitioned domains, My Domain host names for your Developer Edition org, demo org, patch org, sandbox, scratch org, or Trailhead Playground include a word related to the org type. For example, partitioned domains for Developer Edition and patch orgs include the word develop. Partitioned domains allow Salesforce to maximize the availability of your orgs by gradually rolling out delivery changes. And it’s easier to identify an org by a URL when the domain is partitioned."). ## 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](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_app_url_changes.htm&release=264.0.0&type=5 "Your My Domain name is a subdomain used in login URL and application URLs across your Salesforce org, including sites and Visualforce pages. Understand what determines your org’s URL formats and the structure of those formats."). ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_note.png) Note To use a custom domain such as https://www.example.com to serve content from your org’s sites, see [Custom Domains](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt.htm&type=5&language=en_US). ## 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](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_redirections.htm&release=264.0.0&type=5 "When you deploy a change to your My Domain, Salesforce redirects multiple host names automatically. Learn about the types of redirections, how to log redirections for the host names that Salesforce hosts for your org, and how you can control these 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](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_plan.htm&release=264.0.0&type=5 "Whether you change your My Domain to update your brand, to adopt enhanced domains, or to enable partitioned domains, the URLs that Salesforce hosts for your org change. Those changes can have a large impact, and making the required updates can seem like a daunting project. To make the process as smooth as possible for you, your users, and your customers, review the high-level steps, the recommended practices, and how to reduce the impact on your users and customers."). ## 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_note.png) 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](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_setting_login_policy.htm&type=5&language=en_US) and [Single Sign-On](https://help.salesforce.com/s/articleView?id=xcloud.sso_about.htm&type=5&language=en_US). For information about updating authentication after your My Domain login URL or sites URL changes, see [Update Authentication After a My Domain Change](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_auth_update.htm&release=264.0.0&type=5 "Determine whether your My Domain change requires that you update your authentication settings. Then learn about the authentication settings that can be impacted after a My Domain change and make the required updates. If your My Domain login host name or sites host name changed when you deployed a My Domain change, update your authentication settings."). ## 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_note.png) 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. #### See Also - [My Domain](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_overview.htm&release=264.0.0&type=5 "Showcase your company’s brand with a customer-specific subdomain name in your Salesforce org URLs. With My Domain, you can include your company name in your URLs, for example, https://mycompany.my.salesforce.com. With these org-specific URLs, you can set up a custom login page, set a custom login policy, offer single sign-on, and allow users to log in with a social account. My Domain also allows you to work in multiple Salesforce orgs in the same browser at the same time.")