--- schema_version: "1" id: 6410ac5fb345441d9b1f65e8be95a554fed08533cfa208d899bfd1b3c3819336 title: Update Your Org for My Domain Changes collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/domain_name_guidelines.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.domain_name_guidelines.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: e3ec718a91cd21167899f779ab704a7a45950eb511087081fa5f2a42953aebd9 description: When you deploy a change your My Domain, your Salesforce org’s login URL and application URLs change. URLs that are dynamically constructed—for example, URLs generated via the DomainCreator Apex class—use the new URLs automatically. However, some Salesforce functionality requires an update to work with your new URLs. Similarly, custom code, your network configuration, and third-party integrations that use the old URLs require updates. To ensure a smooth transition to your new URLs, update references to your old URLs. products: - Salesforce Platform - Cross Cloud release: "264" --- # Update Your Org for My Domain Changes When you deploy a change your My Domain, your Salesforce org’s login URL and application URLs change. URLs that are dynamically constructed—for example, URLs generated via the `DomainCreator` Apex class—use the new URLs automatically. However, some Salesforce functionality requires an update to work with your new URLs. Similarly, custom code, your network configuration, and third-party integrations that use the old URLs require updates. To ensure a smooth transition to your new URLs, update references to your old URLs. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions
![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 For high-level steps and recommended practices for a My Domain change, plus how to reduce the impact on your users and customers, 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."). ## Pre-Deployment Tasks Complete these tasks before you deploy a My Domain change.

Feature or Configuration

Task
Allowlists Review your allowlists, and ensure that they include the required Salesforce domains.
Cross-Org Links and Redirections

Create an inventory of links and redirections that take the user from a different Salesforce org to the org in which you plan to change the My Domain. Search across all your Salesforce orgs.

For example, a hard-coded link on a Visualforce page in a sandbox takes a user to a production URL, such as a file or another Visualforce page. Or, if you have multiple production orgs and use redirections to route users to the correct org, note the places in your code where those redirections occur.

Plan to update these links and redirections after you deploy your My Domain change.

If the redirection includes a redirection parameter in code or within a URL, also plan to update the Trusted URLs for Redirects allowlist in the org that contains the redirection. For more information, see Trust Redirections to Your Other Salesforce Orgs.

Custom Visualforce pages or custom apps

Replace references to the org’s instance URL with relative URLs and dynamically generated host names. Note any URLs that require a hard-coded reference.

For more information, see the knowledge article Updating Hard-Coded References.

To search your Salesforce code, download the metadata for each of your Salesforce orgs. Then use a code editor such as Microsoft Visual Studio to search for URLs that belong to the org in which you plan to change the My Domain.
Einstein Bots

Identify the web pages and sites that use your chatbots so that you can update them after you deploy the change.

For each bot, review the Permitted Domains field in the chat deployment settings. Optionally, you can update the permitted domains and update your deployment code before you deploy the My Domain change. For more information, see Create Chat Deployments.
External software that accesses your Salesforce org

After you deploy a My Domain change, Salesforce redirects your previous My Domain URLs. In some cases, external software calls can’t process the redirection, and the call to the Salesforce URL fails.

Before you deploy your My Domain change, verify that the external software that uses your Salesforce URLs, including site URLs, can process redirections. If the software can’t process those redirects, work with the software owner to get that redirection functionality in place or plan to update your use of the software with your new URLs after you deploy the change.
Firewalls and proxy servers that filter by host name Update trust settings to include all applicable URL formats for your new configuration, as described in My Domain URL Formats.
Hard-coded Salesforce org URLs

With a hard-coded URL, the URL exists in plain text in your code. Those URLs require a manual update when the URL changes. For this reason, Salesforce recommends that you use relative and dynamically created URLs instead of hard-coded URLs whenever possible.

The first step to addressing hard-coded URLs is to find where they exist in your Salesforce orgs. An inventory can help you complete the required updates to your org and include the relevant functionality in your testing.

To search your Salesforce code, download the metadata for each of your Salesforce orgs. Then use a code editor such as Microsoft Visual Studio to search for URLs that belong to the org in which you plan to change the My Domain. To determine what to search for, you can use your Salesforce instance and reference the My Domain URL formats.

Before you deploy your My Domain name, reduce your post-deployment effort by replacing hard-coded links with relative URLs and dynamically generated URLs. To generate My Domain URLs, use the DomainCreator Class in Apex.

Note the hard-coded URLs to update after you deploy your My Domain change.
Identity providers on your My Domain login page Note the authentication options available to your users. For example, the ability to log in to Salesforce with Google credentials. For more information, see Update Authentication After a My Domain Change.
Installed packages from AppExchange To get the latest fixes, including potential fixes for enhanced domains, install the latest version of each package. Note the package providers so that you can report any issues detected during testing. For more information, see Manage Installed Packages in Salesforce Help, and visit AppExchange.
My Domain settings Document your configuration on the My Domain Setup page for reference after you deploy the My Domain change. To capture all settings, view or edit each section on the Setup page.
If the change to your My Domain updates your My Domain login URL, complete these tasks before you deploy the My Domain change. Your My Domain login URL changes when you change your My Domain name or suffix, deploy enhanced domains in a sandbox, or deploy partitioned domains in a non-production org.

Feature or Configuration

Task
Authentication options such as single sign-on (SSO), authentication providers, and named credentials

If any authentication methods use your login URL, plan to update authentication after you deploy the My Domain change. We recommend that you document your existing settings before you deploy your My Domain change. This snapshot of your earlier configuration is a valuable reference for your rollback plan.

For more information about the settings to capture, see Determine the Required Authentication Updates After a My Domain Change.
Knowledge articles served on your *.my.salesforce.com URL Search for hard-coded references to the knowledge article URLs.
Lightning Out (beta)

Identify the Visualforce pages, web pages, and other locations that call your Lightning Out app. Identify who can update the markup embedded in those pages.

Determine whether authenticated users can access Lightning Out and whether the external client app for Lightning Out uses your My Domain login URL.
Multi-factor authentication (MFA) for logging in to Salesforce Preserve login access for your admins and end users.
Open Computer-Telephony Integrations (CTIs), such as Salesforce Call Center and Click to Dial
  • Work with your telephony provider to add your new URLs to the telephony provider’s allowlists.
  • Review your configuration for any hard-coded references to your URLs. Whenever possible, update these references to relative URLs instead. For examples, see the Knowledge Article Enhanced Domains and Open CTI with Visualforce (Spring ‘23). If you find any hard-coded references that you can’t convert to a relative URL, note them and prepare to update them after you deploy your new My Domain.
Service Cloud Voice

When you enable Service Cloud Voice, Salesforce uses your My Domain URLs to configure single sign-on (SSO) to your telephony provider. The required action depends upon your configuration.

  • If you use Service Cloud Voice with Amazon Connect or Service Cloud Voice with Partner Telephony from Amazon Connect, Salesforce updates your configuration, including the Amazon Connect allowlist, when you deploy your new My Domain. No action is required before you deploy the new My Domain.
  • If you use Service Cloud Voice with Partner Telephony, work with your telephony provider to add your new URLs to their allowlist. Also identify hard-coded connect API URLs, allowlists, and references to the Next generation Omni-Channel engagement URL that ends in *.my.salesforce-scrt.com. With your telephony provider, prepare to update those hard-coded references after you deploy your new My Domain.
If the change to your My Domain updates your Visualforce URL, complete these tasks before you deploy the My Domain change. Your Visualforce URL changes when you deploy enhanced domains or change your My Domain name. ![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 the change to your My Domain also updated your My Domain login URL changed, these steps are covered in the corresponding list of pre-deployment tasks in this Help topic.

Feature or Configuration

Task
Open Computer-Telephony Integrations (CTIs), such as Salesforce Call Center and Click to Dial
  • Work with your telephony provider to add your new Visualforce URL to the telephony provider’s allowlists.
  • Review your configuration for any hard-coded references to your Visualforce URL. Whenever possible, update these references to relative URLs instead. For examples, see the knowledge article Enhanced Domains and Open CTI with Visualforce (Spring ‘23). If you find any hard-coded references that you can’t convert to a relative URL, note them and prepare to update them after you deploy your new My Domain.
Salesforce Maps Determine whether you show nearby maps in Salesforce records or on sites. If so, prepare to update the Maps Nearby Map component after you deploy your new My Domain. See Add Nearby Maps to Salesforce Record Pages and Add Nearby Maps to Sites.
Service Cloud Voice

If you use Service Cloud Voice with Partner Telephony, work with your telephony provider to add your new Visualforce URL to their allowlist. Also identify hard-coded references to your Visualforce URL in your configuration. With your telephony provider, prepare to update those hard-coded references after you deploy your new My Domain.

If you use Service Cloud Voice with Amazon Connect or Service Cloud Voice with Partner Telephony from Amazon Connect, no action is required. Salesforce updates your configuration when you deploy your new My Domain.
If your Experience Cloud sites or Salesforce Sites URL change with your My Domain change, complete these tasks before you deploy your My Domain change. Site URLs change when you deploy enhanced domains, change your My Domain name in an org with enhanced domains, or deploy partitioned domains in a non-production org.

Feature or Configuration

Task
Authentication options such as single sign-on, authentication providers, and named credentials

If any authentication methods use your site URL, plan to update authentication after you deploy the My Domain change. We recommend that you document your existing settings before you deploy your My Domain change. This snapshot of your earlier configuration is a valuable reference for your rollback plan.

For more information about the settings to capture, see Determine the Required Authentication Updates After a My Domain Change.
Embedded Service Deployment (Chat) Identify the web pages that include chat and identify who can update the code snippet embedded in those pages.
Identity providers on your site login page Note the authentication options available to your users. For example, the ability to log in to your site with their Salesforce or Google credentials. For more information, see Update Authentication After a My Domain Change.
Knowledge articles served on your Experience Cloud site URL Search for hard-coded references to the knowledge article URLs.
A Mobile Publisher for Experience Cloud app

To support redirections of your current My Domain URLs after you deploy the My Domain change, check your Mobile Publisher for Experience Cloud Apps version. If you’re running a version lower than 10.0, follow the instructions in the knowledge article Mobile Publisher for Experience Cloud Apps and Enhanced Domains, to upgrade to the latest version before you deploy your My Domain change.

If you use a custom domain such as https://www.example.com to host your Experience Cloud site and use that custom domain for your Mobile Publisher app, this task doesn’t apply. Also, this task doesn’t apply to Mobile Publisher for Lightning apps.
Lightning Out (beta) Identify the external client app for Lightning Out that use your Experience Cloud sites URL. Determine whether authenticated users access Lightning Out.
Multi-factor authentication for logging in to your site Preserve login access for your admins and end users.
If you have Experience Cloud sites or Salesforce Sites and the My Domain change includes enabling enhanced domains, complete these tasks before you deploy the new My Domain.

Feature or Configuration

Task
External integrations Salesforce uses the Server Name Indication (SNI) protocol to serve the *.my.site.com and *.my.salesforce-sites.com domains. If an integration doesn’t support that protocol, the integration can fail. Work with third parties that currently integrate with your *.force.com site URL to ensure that they support SNI.
IP restrictions are configured in Salesforce with only IPv4 addresses

After you deploy enhanced domains, your new *.my.site.com Experience Cloud site host name supports both IPv4 and IPv6. If a profile includes IP restrictions and only IPv4 addresses are allowed, users assigned to that profile can see an error when they access your site that ends in *.my.site.com via IPv6. To prevent that error, update your IP allowlists or restrictions to allow IPv6 source addresses for authorized users. In particular, review and update the login IP range restrictions for the relevant profiles, including the site’s guest user profile. For more information on setting IP restrictions in Salesforce, see the knowledge article Network Access, Session Settings, and Profile-based IP restrictions.

These three IP ranges cover the entire IPv4 and IPv6 internets. 

:: to ::fffe:ffff:ffff
0.0.0.0 to 255.255.255.255
::1:0:0:0 to ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
Network restrictions that use IP allowlists only

When you deploy enhanced domains, your new system-managed Experience Cloud site *.my.site.com domain includes the Experience Cloud content delivery network (CDN), which uses the Salesforce CDN partner. The IP addresses used by the Salesforce CDN partner aren’t published. Therefore, if your network settings include IP allowlisting, users can lose access to your site that uses the Salesforce CDN. For example, if your users log in via a VPN that exclusively uses IP allowlisting, the users on that VPN can’t access your site, because it uses the Salesforce CDN partner's IP address.

To ensure that your users can access your Experience Cloud site on the Salesforce CDN, allowlist your site’s domain, or serve your site via a custom domain. For more information, see the knowledge article Access Experience Sites via an IP-Restricted VPN After Enhanced Domains Deployment.

If you can’t allowlist your domain at the network level or configure a custom domain to serve your site, plan to contact Salesforce Customer Support to disable the Salesforce CDN for your *.my.site.com site URL after you deploy enhanced domains.

Trusted domains for inline frames

If the Clickjack protection level for your site is Allow framing of site pages on external domains (Good protection), review and update the list of trusted domains. In particular, ensure that *.my.salesforce.com is trusted.

For more information, see Enable Clickjack Protection in Experience Cloud Sites and Enable Clickjack Protection in Site.com.

Visualforce pages with embedded Lightning components If the Visualforce page is published through an Experience Cloud site, trust your Lightning components URL for scripts on your site. For each site with Visualforce pages that include embedded Lightning components, edit the Security & Privacy settings in Experience Builder and add your Lightning Components URL to the Trusted Sites for Scripts. For example, add https://*.container.force.com or https://*.force.com. For more information, see Where to Allowlist Third-Party Hosts for Experience Builder Sites.
## Post-Deployment Tasks Complete these tasks after you deploy a My Domain change. Post-deployment tasks require your new My Domain URLs.

Feature or Configuration

Task
Incomplete pre-deployment tasks Review the pre-deployment tasks, and complete any incomplete items.
Allowlists

If you deployed enhanced domains, you can remove the domains that only apply to orgs without enhanced domains from your allowlist. However, we recommend that you keep those domains in your allowlist for redirection until all users and integrations are using your new domains successfully.

For the list of required domains and their purposes, see Allow the Required Domains.
Changed URLs With almost every My Domain change, the URLs that Salesforce serves for your org change. Salesforce redirects these URLs by default. To help your users update outdated links and bookmarks, we recommend that you enable a brief message during the redirection that provides the current URL.
Cross-Org Links and Redirections

Update references to your old My Domain URLs in your cross-org links and redirections.

If the redirection includes a redirection parameter in code or within a URL, also plan to update the Trusted URLs for Redirects allowlist in the org that contains the redirection. For more information, see Trust Redirections to Your Other Salesforce Orgs.
Chatter Review and update bookmarks and links on Chatter groups that you own.

Custom Visualforce pages or custom apps

Replace hard-coded references to the org’s instanced URL, such as https://na170.salesforce.com, or your My Domain login URL with your new My Domain login URL.

For more information, see the knowledge article Updating Hard-Coded References.

Einstein Bots For each bot, regenerate the deployment code and update it on each web page that uses the bot. As part of the process, review and update the Permitted Domains field in the chat deployment settings. For more information, see Create Chat Deployments.
External software that accesses your Salesforce org Update the references to your Salesforce URLs within the external software, then log in to Salesforce again via the software.
Hard-coded references to URLs

Update these references to your current My Domain URLs. Ideally, generate the host names via a dynamic method, such as the DomainCreator Class in Apex.

If you deployed enhanced domains, review the temporary host names redirections. If you find any of those host name formats in your org, update them to the enhanced domain format.

For more information about updating hard-coded references, see the knowledge article Updating Hard-Coded References.
Installed packages from AppExchange Verify the package functionality. In necessary, log in to Salesforce again to access the package features. Note the features that require users to reconnect, and include those features in your end-user notifications. For more information, see Notify Users and Customers About a My Domain Change.
Firewalls and proxy servers that filter by host name Optionally, you can remove the host names that no longer apply to your org from your trust settings. However, we recommend that you allow those host names for redirection until all users and integrations are using your new domains successfully.
Pinned certificates We don’t recommend certificate pinning. Consider updating your policies to exclude pinned certificates. Otherwise, if you changed your My Domain suffix or deployed enhanced domains, review your pinned certificates against your new My Domain URLs, and update them as needed. If your software or policies require pinning, we recommend that you pin the intermediate certificate and not the leaf certificate.
Complete these tasks if your My Domain login URL changed. Your My Domain login URL changes when you change your My Domain name or suffix, deploy enhanced domains in a sandbox, or deploy partitioned domains in a non-production org. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_important.png) Important When your My Domain login URL or site URL changes, authentication methods such as SSO and MFA can stop working. Before you deploy a change to your My Domain, [preserve login access](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_login_change_preserve_access.htm&release=264.0.0&type=5 "When your My Domain or site login URL changes, two multi-factor authentication (MFA) verification methods stop working: built-in authenticators and security keys. Without those methods, single sign-on (SSO) can also stop working. To preserve admin access to Salesforce and prevent end-user frustration, verify your backup authentication methods. In preparation for your My Domain change, determine the post-deployment steps to reestablish authentication for your org, including resetting the affected verification methods for your users.") for your admins and users.

Feature or Configuration

Action

API integrations into your org

Check whether the API client references the server endpoint. For the API client, use the metadataServerUrl or serverURL value returned by a login request. Don’t use a hard-coded server URL.

After you deploy a My Domain change that affects your login URL, Salesforce returns the server URL containing your new My Domain name or suffix. If your org has been moved to another instance or you require SOAP API logins to use your My Domain in My Domain policies, old calls to instanced URLs fail. And API logins to a Hyperforce org can’t use an instanced URL. To avoid disruption, use the value returned by Salesforce.
Branding If your brand changed, update your login page branding. For more information, see Customize Your My Domain Login Page with Your Brand.
Desktop links Update the desktop links with your new My Domain login URL.
DevOps Center Update the named credentials used to authenticate users that access your org through DevOps Center. For more information, see Update Named Credentials After a My Domain Change.

Email templates

Replace references to the old URL with your new My Domain login URL. If the template uses a hard-coded URL, which is more common in email templates created in Salesforce Classic, we recommend that you update the template to use a dynamically generated URL.
Enablement sites (myTrailhead) If your enablement site’s login URL is your My Domain login URL in the format https://MyDomainName.my.salesforce.com, contact Salesforce Customer Support to update your authentication provider. For more information, see Configure Your Enablement Site.
Identity providers on your login page Update your identity providers with your new My Domain login URL or new site login URL. For more information, see Update Authentication After a My Domain Change.
Knowledge articles served on your *.my.salesforce.com URL Update any hard-coded references to the knowledge article URLs.
Enhanced Chat To update your Enhanced Web Chat configuration with your My Domain login URL, republish your Enhanced Web Chat deployment. For more information, see Update Your Enhanced Web Chat Deployment After Upgrading to Enhanced Domains.
Lightning Out (beta)

Update external client apps that use your My Domain login URL.

Refresh the Lightning Out markup on Visualforce pages, web pages, and other locations that call your Lightning Out app.

If authenticated users access Lightning Out, generate a new Session ID or authentication token for those connections.
Multi-factor authentication for accessing Salesforce Update your authentication configuration. For more information, see Update Authentication After a My Domain Change.
Named credentials

Review the URL field for your named credentials. If a named credential uses your My Domain login URL, update the URL field with your new My Domain login URL. For more information, see Update Named Credentials After a My Domain Change.

If users access functionality that relies on an updated named credential, instruct them to reauthenticate.
Marketing Cloud Account Engagement (Pardot)

If your Account Engagement configuration uses the Pardot Connector User, update the login URL that Account Engagement uses. In Account Engagement, update the Pardot Connector User. To use the same user, save the user again in Account Engagement. Then log out and back in to your org to complete the process.

If you’re using the Account Engagement Integration User, no changes are needed.

When you deploy enhanced domains, no change to the Account Engagement tracker domain configuration is required.

Open Computer-Telephony Integrations (CTIs), such as Salesforce Call Center and Click to Dial
  • Verify with your telephony provider that your new URLs are included in the telephony provider’s allowlists. Optionally, work with the provider to remove your previous URLs from to their allowlists.
  • Update any hard-coded references to your previous URLs. Whenever possible, update these references to relative URLs instead. For examples, see the knowledge article Enhanced Domains and Open CTI with Visualforce (Spring ‘23).
A personalized version of the Salesforce mobile app published on the Google Play or Apple App stores If your personalized version of the Salesforce app uses your My Domain login URL, update your app to use your new My Domain login URL.
Service Cloud Voice

When you enable Service Cloud Voice, Salesforce uses your My Domain URLs to configure single sign-on (SSO) to your telephony provider. The required action depends upon your configuration.

  • If you use Service Cloud Voice with Amazon Connect or Service Cloud Voice with Partner Telephony from Amazon Connect, no action is required. Salesforce updates your configuration, including the Amazon Connect allowlist, when you deploy your new My Domain. Optionally, remove your old URL formats from the Amazon Connect allowlist.
  • If you use Service Cloud Voice with Partner Telephony, work with your telephony provider to update your configuration with your new URLs after you deploy the new My Domain. In particular, update hard-coded connect API URLs, allowlists, and references to the Next generation Omni-Channel engagement URL that ends in *.my.salesforce-scrt.com. Optionally, work with your telephony provider to remove your previous URL formats from their allowlist.
Single sign-on for accessing Salesforce Update your authentication configuration. For more information, see Update Authentication After a My Domain Change.
Streaming API

To ensure continuity during instance refreshes and org migrations, we recommend using My Domain URLs with Streaming API. If you follow this recommendation, replace your previous My Domain login URL with your new login URL.

If you don’t follow this recommendation yet, use your My Domain login URL with Streaming API. For example, replace https://login.salesforce.com and https://InstanceName.salesforce.com​/ with https://MyDomainName.my.salesforce.com​/.

For more information on logging in to Salesforce with your My Domain URL, see Log In to Salesforce with Code.
Third-party external client apps Work with the third party to update the URLs in the app, including SSO and other authentication configuration settings. For more information, see Update Authentication After a My Domain Change.
Zones for Experience Cloud sites (Ideas, Answers, Chatter Answers) Update the email notification URL. From Setup, in the Quick Find box, enter Zones, and then select Zones under Answers, Ideas Zones or Chatter Answers Zones. Then, next to the zone that you want to change, click Edit. To update the Email Notification URL, clear the existing URL so that the field is blank. Save the page, and the system populates the field with the new My Domain URL.
If the URL for your Visualforce pages changed, complete these tasks. Your Visualforce URL changes when you deploy enhanced domains or change your My Domain name. ![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 your My Domain login URL changed, these steps are covered in the corresponding list of post-deployment tasks in this Help topic.

Feature or Configuration

Task
Open Computer-Telephony Integrations (CTIs), such as Salesforce Call Center and Click to Dial
  • Verify that your new Visualforce URL is included in the telephony provider’s allowlists. Optionally, work with the provider to remove your previous Visualforce URL from to their allowlists.
  • Update any hard-coded references to your previous Visualforce URL. Whenever possible, update these references to relative URLs instead. For examples, see the knowledge article Enhanced Domains and Open CTI with Visualforce (Spring ‘23).
Salesforce Maps If you show nearby maps in Salesforce records or on sites, update the corresponding Maps Nearby Map component. See Add Nearby Maps to Salesforce Record Pages and Add Nearby Maps to Sites.
Service Cloud Voice

If you use Service Cloud Voice with Partner Telephony, work with your telephony provider to update your configuration, including allowlists, with your new Visualforce URL. Optionally, work with your telephony provider to remove your previous Visualforce URL from their allowlist.

If you use Service Cloud Voice with Amazon Connect or Service Cloud Voice with Partner Telephony from Amazon Connect, no action is required. Salesforce updates your configuration when you deploy your new My Domain. Optionally, you can update your Amazon Connect allowlist to remove your old Visualforce URL format.
Complete these tasks if your content URL changed. That URL changes when you change your My Domain name or suffix, deploy enhanced domains in any org, or deploy partitioned domains in a non-production org.

Feature or Configuration

Task
Email and other document templates that use files hosted in Salesforce Update the embedded content or images. For example, an icon or image that is hosted in your org and used in email footer templates. Instruct users to update their local templates.
Enablement sites (myTrailhead) URLs for badge art stored in your Salesforce org changed. Update your modules and trails with the new badge art URLs. For more information, see Configure Your Enablement Site.
Web content that uses files hosted in Salesforce Update the content links. For example, an image used on your website or externally published PDFs.
Complete these tasks if your Experience Cloud sites or Salesforce Sites URL changed. Site URLs change when you deploy enhanced domains, change your My Domain name in an org with enhanced domains, or deploy partitioned domains in a non-production org. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_important.png) Important When your My Domain login URL or site URL changes, authentication methods such as SSO and MFA can stop working. Before you deploy a change to your My Domain, [preserve login access](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_login_change_preserve_access.htm&release=264.0.0&type=5 "When your My Domain or site login URL changes, two multi-factor authentication (MFA) verification methods stop working: built-in authenticators and security keys. Without those methods, single sign-on (SSO) can also stop working. To preserve admin access to Salesforce and prevent end-user frustration, verify your backup authentication methods. In preparation for your My Domain change, determine the post-deployment steps to reestablish authentication for your org, including resetting the affected verification methods for your users.") for your admins and users.

Feature or Configuration

Task
Authentication that uses your site URL If you configured a Salesforce authentication provider so that your users can log in to your custom external web app using their Salesforce credentials, verify your configuration. If your setup uses your site URL, update the configuration. For more information, see Update Authentication After a My Domain Change.
Branding If your brand changed, update the branding for your Experience Cloud site login page. For more information, see Brand Your Pages from the Administration Workspace.
Desktop links Update the desktop links with your new site login URL.
Email templates Replace references to your old site URLs with the new site login URLs. Hard-coded URLs are more common in email templates created in Salesforce Classic.
Embedded Service Deployment (Chat) Regenerate the Embedded Service code snippet with your new site URL. Update the web pages that include chat with the new snippet. See Add Your Embedded Chat to a Website.
Enablement sites (myTrailhead) If your enablement site’s login URL is your site URL, contact Salesforce Customer Support to update your authentication provider. For more information, see Configure Your Enablement Site.
External integrations Update external integrations that reference your sites.
External links to the site Update external-facing links such as publicly available Experience Cloud sites and Salesforce Sites. For example, a site URL can be used on your website, social media pages, marketing materials, and templates such as email signatures and automated responses.
Hard-coded references to your site within your sites and custom pages

Update any hard-coded links to Experience Cloud sites and Salesforce Sites in your sites and custom pages. For example, if you host knowledge articles on an Experience Cloud site, update the URLs that include your old site URL. These links are redirected to the equivalent current site URL until you disable those redirections or until Salesforce stops those redirections. See Prepare for the End of Redirections for Non-Enhanced Domains.

When you update these hard-coded links, use relative paths and dynamically generated host names whenever you can. If your site URL changes again in the future, relative paths and dynamically generated host names continue to work.
Identity providers on your site login page Update your identity providers with your new site URL. For more information, see Update Authentication After a My Domain Change.
Knowledge articles served on your Experience Cloud site URL Update any hard-coded references to the knowledge article URLs.
Lightning Out (beta)

Update external client apps that use your Experience Cloud URL.

If authenticated users access Lightning Out, generate a new Session ID or authentication token for those connections.
Enhanced Web Chat If you use Enhanced Web Chat in an Experience Builder site, update your allowlisted URLs. For more information, see Update Your Enhanced Web Chat Deployment After Upgrading to Enhanced Domains.
A Mobile Publisher for Experience Cloud app

Update your app to use your new Experience Cloud sites URL before Salesforce stops redirections for your old site URL. For more information, see Prepare for the End of Redirections for Non-Enhanced Domains and Mobile Publisher for Experience Cloud.

If you use a custom domain such as https://www.example.com to host your Experience Cloud site and use that custom domain for your Mobile Publisher app, this task doesn’t apply. Also, this task doesn’t apply to Mobile Publisher for Lightning apps.
Multi-factor authentication for accessing your site Update your authentication configuration. For more information, see Update Authentication After a My Domain Change.
Named credentials Update named credentials that use your site login URL. For more information, see Update Named Credentials After a My Domain Change.
Single sign-on for accessing your site If you configured SSO for your Experience Cloud sites, update the configuration. SSO options for sites include users logging in to your site with their Salesforce credentials or with an external provider’s credentials. For more information, see Update Authentication After a My Domain Change.
If you have Experience Cloud sites and the My Domain change included enabling enhanced domains, complete this task.

Feature or Configuration

Task
Network restrictions that use IP allowlists only

When you deploy enhanced domains, your new system-managed Experience Cloud site *.my.site.com domain includes the Experience Cloud content delivery network (CDN), which uses the Salesforce CDN partner. The IP addresses used by the Salesforce CDN partner aren’t published. Therefore, if your network settings include IP allowlisting, users can lose access to your site that uses the Salesforce CDN. For example, if your users log in via a VPN that exclusively uses IP allowlisting, the users on that VPN can’t access your site, because it uses the Salesforce CDN partner's IP address.

To ensure that your users can access your Experience Cloud site on the Salesforce CDN, allowlist your site’s domain, or serve your site via a custom domain. For more information, see the knowledge article Access Experience Sites via an IP-Restricted VPN After Enhanced Domains Deployment.

If you can’t allowlist your domain at the network level or configure a custom domain to serve your site, contact Salesforce Customer Support to disable the Salesforce CDN for your *.my.site.com site URL.

Complete these steps if the Experience Cloud sites or Salesforce Sites URL that Salesforce hosts changed and a custom domain such as https://www.example.com serves the site. Site URLs that Salesforce hosts change when you deploy enhanced domains, change your My Domain name in an org with enhanced domains, or deploy partitioned domains in a non-production org. ![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 Enabling or disabling enhanced domains doesn’t change the Salesforce internal \*.live.siteforce.com CNAME for your custom domain.

Feature or Configuration

Task
Your custom domain uses the External HTTPS option: Use a third-party service or CDN to serve this domain. Update the target host name used when forwarding requests from your domain’s proxy or CDN. For more information, see Prerequisites for a Custom Domain That Uses a Third-Party Service or CDN.
The custom domain serves the site via a non-Salesforce host or service. Review and update the domain configuration, such as CDN settings and hard-coded references to Salesforce URLs.
#### 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.") - [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.") - [My Domain Considerations](https://help.salesforce.com/s/articleView?id=xcloud.domain_name_considerations.htm&release=264.0.0&type=5 "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.")