What Microsoft says it will do
Admins would set up a vanity (custom) link in the domain authenticator. Once authenticated, that vanity domain is meant to appear in all email links, and in hosted digital assets, forms, event registration pages and the preference center. The stated goal is to show your brand name instead of the URLs that Customer Insights - Journeys generates automatically.
Microsoft's pitch is that automatically generated URLs look unprofessional and suspicious, and can lower click rates and conversions. Its example is a retail holiday campaign. Microsoft's release plan version of that example also mentions SMS, which the roadmap text submitted to us doesn't. That wording is a scenario, not measured data. Microsoft publishes no click-rate or conversion figures for the feature.
Timing: the preview date has passed
The roadmap metadata lists a preview in September 2026 and general availability in December 2026. Microsoft's release plan shows the same pair, public preview Sep 2026 and general availability Dec 2026, enabled for users by admins, makers or analysts. The roadmap metadata lists the Worldwide (Standard Multi-Tenant) cloud instance.
Today is October 23, 2026. The preview month is over, but the entry is still marked "In development". We found no announcement or documentation confirming that a preview is live. Microsoft also warns that some functionality in the release plan has not been released, and delivery timelines may change. The December date is an estimate.
Others have noticed this feature slipping before. A 2024 blog post covering the wave 1 2024 release plan was excited about "vanity domains". A commenter later asked whether branded links had been dropped, because they couldn't find any documentation. That doesn't prove anything about the current plan. It is a reason to wait for actual documentation before building campaigns around it.
Branded links are not sender authentication
The roadmap says the setup happens in the "domain authenticator", which invites confusion with email authentication. They are different things.
Microsoft's current documentation says domain authentication lets recipient servers confirm two things. The From address belongs to your organization, and you have approved Customer Insights - Journeys to send on its behalf. It also enables DKIM and SPF and aligns the From and Return-Path addresses. That's about deliverability and fraud protection, not how links look.
Today's wizard (Settings > Email marketing > Domain authentication) works like this:
- You enter the domain and choose whether it's for email sending, form hosting or both.
- You add a TXT record to prove ownership.
- You add two CNAME records for DKIM.
- You add a CNAME for Envelope-From and SPF alignment.
- You select Verify. Green checkmarks and a Confirmed status mean the domain is ready.
Microsoft hasn't said whether branded links will use these same records or this same flow. Don't assume that authenticating a sending domain today will switch on branded links later.
What links look like today
The current email designer documentation explains why this feature matters. When a marketing email goes live, each standard link is replaced with a unique redirect URL pointing at the Journeys server. That URL identifies the recipient, the message and the destination. On click, Journeys logs the click and forwards the contact to the destination you set.
So recipients see a tracking URL, not your destination page. The roadmap aims to make that visible URL carry your brand's domain. Microsoft doesn't say branded links would remove tracking, change click measurement or eliminate redirects. Don't promise stakeholders any of that.
Every commercial marketing email must also contain a preference center link before it can pass the error check. The roadmap says the branded domain would extend to preference-center links. It documents no change to that requirement.
What admins can do now
- Audit your domains. Check which domains are authenticated in your Journeys environment. By default, new installations include a pre-authenticated sending domain ending in dyn365mktg.com. Microsoft says that domain is for testing or demos only, not production sending.
- Keep sender authentication separate. Make sure your real sending domains are authenticated with DKIM and SPF. That's required regardless of this feature.
- Plan the DNS ownership question. A branded link domain will almost certainly need DNS changes. Microsoft hasn't published the specifics, so involve your DNS owners early but don't pre-create records.
- Don't promise results. Treat the trust and conversion benefits as Microsoft's expectation, not a result. Measure your own click rates before and after.
- Watch the release plan. Look for the move from "In development" to a documented preview or GA, then read the setup article before touching production domains.
Not yet known
The roadmap and release plan don't say:
- Which URL formats are supported.
- Which DNS records are required.
- What permissions apply beyond "admins, makers or analysts".
- Whether there are regional limits.
- How existing links in already-sent emails behave.
These gaps matter, because a vanity link domain also affects deliverability, certificates and security reviews. Until Microsoft publishes the documentation, anything more specific is speculation.
Bottom line
Branded content links are a sensible, overdue polish feature for Journeys. They would put your own domain on links across email, forms, event pages and the preference center. For now they are still in development, with a September preview date that has already passed and a December GA estimate. Admins can prepare by tidying their domain setup. They should wait for Microsoft's documentation before planning a rollout.