Loading

Updating Marketing Cloud Endpoints to Tenant Specific Endpoints: FAQ

게시 일자: Aug 20, 2023
상세 설명

The Marketing Cloud has begun a program to have all customers update their REST, Auth, SOAP, SSO, SFTP and Device endpoints from legacy Stack-Specific Endpoint architecture and replace it with Tenant Specific Endpoints (TSEs). This change will affect all Marketing Cloud Customers who are using legacy APIs and other endpoints.

As part of our ongoing commitment to customer trust and security, integrations into Marketing Cloud are recommended to utilize tenant-specific endpoints for improved stability and scalability

In addition, this current list of impacted endpoints may be updated in the future as we continue to improve the Marketing Cloud Architecture.

These updates will not affect customers who currently have all of their API traffic on the TSE-enabled routes.

NOTE: If you are a Hyperforce customer, Tenant Specific Endpoints are mandatory. If your Org is about to be migrated to Hyperforce, you must follow the instruction below before the Org Migration, to avoid unintended disruption to Marketing Cloud API access. For more information, please refer to the Retain uninterrupted access to Salesforce services on Hyperforce article.

Tenant Specific Endpoints, also known as Tenant Specific Subdomains , were introduced in the Marketing Cloud as part of the October 2018 release, concurrent with the EU stack (S50) launch. The goal of the TSE architecture is to provide our customers improved security, service reliability, availability, and performance.

Legacy Stack-Specific Endpoints leverage a mesh-replication architecture that bounces an incoming request from one stack to another until the request lands in the right stack. In contrast, TSEs directly route the incoming request to the customer-specific stack, which is much more secure and efficient than bouncing a request between stacks until it hits the right one. TSEs do this by giving each tenant a unique identifier for their API endpoints, which also identifies the stack on which that tenant is hosted.

Below are some examples of the differences between stack-specific endpoints and TSEs:
 

EndpointStack-SpecificTSE
API Auth
auth.exacttargetapis.commc123.auth.marketingcloudapis.com
REST API
www.exacttargetapis.commc123.rest.marketingcloudapis.com
Device API
consumer.exacttargetapis.commc123.device.marketingcloudapis.com
SOAP API
http://webservice.s7.exacttarget.commc123.soap.marketingcloudapis.com
솔루션

Based on customer feedback, we have adjusted the migration timelines into two phases. Customers must migrate Phase 1 endpoints to Tenant Specific Endpoints by taking the required actions by September 30th, 2022.

We will continue to listen to customer feedback on timelines for migrating Phase 2 endpoints to TSEs. We recommend customers evaluate and migrate to tenant specific endpoints for Phase 2 services for improved latency, reliability and future compatibility with Hyperforce.

 
EndpointQualifying CriteriaPhase
Migration Deadline
Action Required
Marketing Cloud Connect
See ArticlePhase 1September 30, 2022Enable Tenant-Specific OAuth Endpoints
Mobile Push SDK

SDK version
iOS 6.1.4 or older

Android 6.1.0 or older using Global Endpoints

Phase 1September 30, 2022Update Mobile Application with latest Mobile Push SDK to Utilize Your Tenant’s Endpoints
REST APIs
Clients utilizing Global Endpoints listed below
Phase 22023+For these endpoints in Phase 2, we recommend customers utilize tenant specific endpoints for improved latency, reliability and future compatibility with Hyperforce.

 

SOAP APIs
Clients utilizing Global Endpoints listed below
Phase 22023+
SSO
Clients utilizing Global Endpoints listed below
Phase 22023+
CloudPages
Clients utilizing Global Endpoints listed below
Phase 22023+
GroupConnectClients utilizing Global Endpoints listed belowPhase 22023+
SFTPClients utilizing Global Endpoints listed belowPhase 22023+For SFTP use cases, we recommend customers utilize our AWS S3 or Azure Blob Storage (Beta) capabilities for improved performance and future compatibility with Hyperforce.


SOAP: REST/Auth: SSO: SFTP:
  • sftp://ftp1.exacttarget.com
  • sftp://ftp.s4.exacttarget.com
  • sftp://ftp.s6.exacttarget.com
  • sftp://ftp.s7.exacttarget.com
  • sftp://ftp.s10.exacttarget.com
  • sftp://ftp.s11.exacttarget.com
  • sftp://ftp.s50.exacttarget.com
  • Any SFTP integration that uses a hardcoded, specific IP address
Mobile Push SDK:
  1. If your application is using the following MobilePush SDK versions, then it needs to be updated. The following versions of the SDK do not use tenant-specific endpoints and are hard-coded to use the “legacy” device.exacttargetapis.com endpoint:
    • iOS 6.1.4 or older
    • Android 6.1.0 or older
  1. If your application is using the following MobilePush SDK versions, then please confirm your development team has configured the SDK to use your app’s tenant-specific endpoint. If you are using these versions of the SDK and you have confirmed that your app configured the SDK to use your app’s tenant-specific endpoint, then no further action is required.
    1. iOS 6.0.0
    2. Android 6.0.2
    3. Note: While the above represent the minimum versions of the MobilePush SDK to support tenant-specific endpoints, we always recommend best practice of updating your app to the latest version of the SDK.
 

Why are we retiring these endpoints?

At Salesforce, Trust is our #1 value when serving our customers. We need to update the legacy stack-specific endpoints with TSEs to improve security, service reliability, availability, and performance.
 

Why are TSEs better than the legacy endpoints?

As noted above, TSE improves the overall reliability, availability, and performance of Marketing Cloud services by avoiding the bouncing of requests between stacks. Below are a few of the targeted benefits that TSEs offer:

Enhances Security Posture
Each customer using their own endpoint gives us a higher level of security and makes it easier for us to manage updating security elements, such as certificates.

Lowers Latency When Routing Customer Requests
TSEs help to route customer requests directly to their stack, minimizing global replication and bouncing requests across stacks.

Improves Disaster Recovery
In the event of a service outage, TSE-only stacks can improve recovery time by isolating the impact of the repairs to only the specific stacks(s) that had the outage.

Minimizes Performance Issues, Improves Uptime
Whether it’s a customer employing frequent token requests, unthrottled retries, or there is an issue with a stack or with a pool of machines, TSE can minimize the impact to a specific set of customers instead of causing a global outage.
 

How do I know if I am using TSEs or the legacy endpoints?

As noted above, the legacy endpoints have a different nomenclature than the legacy endpoints. The old legacy endpoints may have a stack designation as part of the endpoint, such as the “s4” in this REST/Auth example:
https://auth-s4.exacttargetapis.com

In some cases, they may not have the stack designation, as in this example:
https://auth.exacttargetapis.com/

However, the Tenant-Specific Endpoint version will always have a tenant ID as part of the URL, such as this:
mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com
 

I need to update my endpoints. Where do I go to find information on what I need to do?

Below are links to Knowledge Articles that will guide you on how to update your relevant endpoints:

 

I don’t know what endpoints I need to change, or where they are. What do I do?

If you have questions after reviewing the Knowledge Articles listed above, create a support case through the Help & Training Portal.

Knowledge 기사 번호

000392227

 
로드 중
Salesforce Help | Article