Enabling Tenant-Specific OAuth Endpoints for Marketing Cloud Connect during Hyperforce Migration

1. Action Required: Enable Tenant-Specific Endpoints

When a Sales/Service org migrates to Hyperforce, you must ensure that Tenant-Specific OAuth Endpoints (TSE) are enabled if you are using the Marketing Cloud Connect functionality. Note: Currently, almost all environments use TSE, so it is rare that new action is required to enable it.

Reference: Retain uninterrupted access to Salesforce services on Hyperforce

2. How to Verify and Enable TSE

Follow the steps in the documentation below to check the status of your OAuth Endpoints. If TSE is disabled, follow the guide to enable it immediately.

Reference:

• Connect to Marketing Cloud

• Marketing Cloud Connect - Attempt to de-reference a null object error after selecting Connect to Marketing Cloud

  • The article above includes screenshots to help identify the correct settings.

FAQ

Q1. Will my Marketing Cloud account also migrate to Hyperforce at the same time?

A. No. The migration schedule for your Sales organization is independent of your Marketing Cloud account.

Q2. We do not use Marketing Cloud Connect. Do we need to take any action?

A. No. If Marketing Cloud Connect is not installed or used, no action is required.

Q3. How can I check if we are using Marketing Cloud Connect?

A. You can verify whether Marketing Cloud Connect is in use by checking the following page. If the Marketing Cloud tab is missing, or the Marketing Cloud Connector settings page is not visible, it is likely not in use.

Reference::Enabling Tenant-Specific OAuth Endpoints for Marketing Cloud Connect

You can also verify if "MC Connect" is installed by checking Installed Packages in Sales/Service.

Reference::View Installed Package Details

Q4. Our Remote Site Settings contain hardcoded instance names for Marketing Cloud Connect. Do we need to update these?

A. Although this is distinct from TSE configuration, it is a frequently asked question. Please refer to the details below:

• ET4AE5_MCC_TokenService (or SFRestAPI)

  Action: generally, no pre-work is needed. This URL typically updates automatically after the instance migration.
  Verification: After the Hyperforce migration, check if the URL has updated to https://[NewInstanceName].salesforce.com. If it has not updated automatically, manually update it.

  Note: SFRestAPI is a remote site that may be created automatically if the system cannot read ET4AE5_MCC_TokenService during migration. Treat it the same way as above.

• MetadataAPI
  Action: Recommended. If the instance name is hardcoded in this Remote Site Setting, update it to use your My Domain URL (https://[MyDomain]--et4ae5.vf.force.com). 
  Reason: Updating this is recommended because it prevents issues with any future instance migrations, regardless of whether the target is Hyperforce or not.

How to Update Remote site setting (Lightning Experience):

1.Log in to Salesforce and click the Gear icon > Setup.

2.In the Quick Find box, enter "Remote Site Settings" and select Remote Site Settings.

3.Click Edit next to "MetadataAPI".

4.Update the Remote Site URL to the following format:

   https://[MyDomain]--et4ae5.vf.force.com

5.Click Save.