Configure Email Delivery shows Limited Access after Winter '27? Open Authenticated Domains directly
Winter '27's setup assistant can grey out Configure Email Delivery for an admin with full rights. Open the Authenticated Domains node by URL and the step clears.
Winter '27 rebuilt the Marketing Cloud Next setup assistant. In some orgs the Required Setup step Configure Email Delivery now shows a Limited Access badge with the tooltip "You don't have permission to complete this step" and a greyed-out Go to Setup button, even for a System Administrator who holds the Marketing Cloud permission set licence, Marketing Cloud Admin and every email setup permission. Salesforce's answer: the assistant's link is what is failing, not your access. Open the Authenticated Domains setup node directly and configure the domain there; once a domain and a from address exist, the greyed-out step clears.
- Product
- Marketing Cloud Next
- Edition
- edition not stated in the source
- Topic
- Setup
- Last verified
Who this applies to
- Marketing Cloud Next orgs upgraded to Winter '27 (production from 12 October 2026, preview sandboxes from late August) where email delivery has not been configured yet
- Admins who see Limited Access on Configure Email Delivery despite holding Marketing Cloud Admin
- Edition: not stated; seen on an Advanced org, the setup node is the same for Growth
Why it matters
The badge reads like a permissions problem, so the usual reaction is a day lost comparing permission sets and raising a case. The permissions are fine. The step is a shortcut into a Setup page, and when the shortcut cannot resolve, the assistant reports it as access. Going to the page by its URL takes a minute and unblocks the whole sending-domain build, which sits on the critical path of every Marketing Cloud Next go-live.
Try it
- Confirm the user holds the Marketing Cloud permission set licence and the Marketing Cloud Admin permission set, so you are not masking a real gap.
- Open the Authenticated Domains setup node directly, replacing the placeholder with your org's My Domain name: https://YOUR-DOMAIN.my.salesforce-setup.com/lightning/setup/E360EmailAuthorizedEmailDomain/home
- Add the authenticated sending domain, publish the DNS records it gives you, and verify it. Then add at least one from address on that domain.
- Go back to Setup Assistant > Required Setup. Configure Email Delivery now shows as done and Go to Setup is active.
- If the direct URL itself returns an access error, that is a real permission or licence gap: fix the assignments from step 1 before raising a case.
Example use case
An organisation's production org was upgraded to Winter '27 on the release weekend. The architect building the sending domains, a System Administrator with Marketing Cloud Admin, saw Limited Access on Configure Email Delivery while the same user had created the same domains in two sandboxes the week before. Every effective permission was identical across the three orgs. Salesforce pointed at the direct Setup URL; the domains were created there and the assistant step cleared.
Prerequisites, limitations and risks
- Marketing Cloud Next provisioned in the org, with the Marketing Cloud permission set licence and Marketing Cloud Admin on the user
- Access to the DNS for the sending domain, or the person who has it, so the records can be published for verification
- Winter '27 in the org; the assistant behaves normally on Summer '26
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