Confirm Sydney data residency before you sign for Marketing Cloud Next
Marketing Cloud Growth and Advanced launched in the Sydney region with data residency in 2025. What to confirm at provisioning, and where WhatsApp fits.
Salesforce's June 2025 announcement lists Sydney (Australia and New Zealand) among seven new regions where Marketing Cloud Growth and Advanced Editions launched in 2025 with data residency, alongside Tokyo, Singapore, Jakarta, Mumbai, Sao Paulo and Zurich. The same post lists WhatsApp as an add-on, and states that Advanced adds Unified Conversations for WhatsApp, meaning two-way conversations that can be handed to service agents.
- Product
- Marketing Cloud Next
- Edition
- Advanced and Growth
- Topic
- Setup
- Confidence
- High - documented by Salesforce
- Last verified
Who this applies to
- Australian and New Zealand organisations evaluating or provisioning Marketing Cloud Next
- Both editions: the source names Growth and Advanced for the regional launch. Unified Conversations for WhatsApp is stated as Advanced only
- Whoever signs the order form and whoever owns the privacy register. Residency is set at provisioning, not switched on later
Why it matters
For regulated Australian buyers, banks, insurers, health and government, offshore customer data is often the single question that stalls a marketing platform decision. Before 2025 it stalled Marketing Cloud Next too. Now the answer exists, but only if the org is provisioned in the Sydney region, and that is a conversation to have before the contract, not after the first data stream is mapped.
Try it
- Before signing, ask your Salesforce account team to confirm in writing that the Marketing Cloud Next org will be provisioned in the Sydney region with data residency.
- Confirm the same for Data 360, since Marketing Cloud Next audiences live there. Residency for the marketing app alone is not the whole answer.
- Record the residency commitment in your privacy impact assessment or vendor register so the next audit does not reopen the question.
- If WhatsApp is on the roadmap, budget it as an add-on. If you need two-way WhatsApp conversations handed to service agents, the source ties that to Advanced.
- Ask what, if anything, still processes outside the region (for example, AI features). The announcement covers the platform launch; it does not itemise every service.
Example use case
A superannuation fund moving off Marketing Cloud Engagement runs its Marketing Cloud Next evaluation with the privacy team in the room from the start. Sydney residency is confirmed on the order form for both the marketing app and Data 360, WhatsApp is deferred to phase two as a priced add-on, and the residency clause is filed against the APRA-related controls the fund already maintains, so the platform decision clears risk in one pass.
Prerequisites, limitations and risks
- Residency depends on where the org is provisioned. An org created in another region is not moved by a setting; treat it as a new provisioning decision
- The source states the 2025 regional launch and the WhatsApp add-on. It does not state which individual services (AI, analytics) process in-region; confirm with Salesforce for your contract
- Unified Conversations for WhatsApp requires Advanced, per the source. Growth customers get WhatsApp as a channel but not the two-way service hand-off
- Pricing for the WhatsApp add-on is not stated in the source
Documented behaviour above comes from the sources listed below. Availability varies by edition, SKU and region - confirm entitlements in your own org before you rely on a feature.
Sources
Stuck on this in your own org?
Blueport is a Sydney-based Certified Salesforce Consulting Partner with 100+ implementations since 2018. If a step above does not match what you see in Marketing Cloud Next, tell us - it is either an edition difference or a change worth knowing about, and we will find out which.
Talk to our team