D365 Journeys Now Brief Your Sellers

Dynamics 365 journeys can now brief your sellers directly, and for marketing and sales teams on the Microsoft stack that is a very welcome change. Since the September 2026 release, the Create a record tile in Dynamics 365 Customer Insights – Journeys has been generally available. A journey can create a phone call, a task, a lead or an opportunity at the moment a buyer acts, with the owner set and the context filled in.

Three more updates from the August and October release notes fit around it. Records created by a journey can carry the name of that journey. Segments can change while a campaign runs, in public preview. And marketers can check consent and build journeys in plain language through Copilot Cowork.

Together they let a team design the handoff from marketing to sales once, on the journey canvas, and then measure it.

What shipped in Customer Insights – Journeys this autumn?

Four updates matter most to B2B teams. The Create a record tile reached general availability in September and can create any Dataverse record that has a relationship to a contact or lead, custom tables included. An August enhancement lets a journey stamp live journey metadata on the records and custom triggers it produces, so a lead keeps the name of the campaign that created it. In October, marketing skills became generally available in Copilot Cowork, where staff can check consent, draft and review emails, and create journeys in natural language. The same release opened a public preview of live segment editing, which changes a journey’s audience without stopping the journey.

The Cowork skills were part of the 30 that Microsoft announced on 8 October, which this blog covered from the seller’s side. This piece stays with the marketer and the handoff.

How do you align sales and marketing in Dynamics 365?

Sales and marketing alignment means both teams agree what a qualified buyer looks like, who follows up, how quickly, and how the result gets counted. In Dynamics 365 those agreements can now live inside a journey. Microsoft’s documented example starts with a lead submitting a pricing request form. A trigger-based journey fires, an optional attribute branch picks the right team, and a Create a record tile adds a phone call for that team, with the Regarding field set so the seller can see why the call exists. The rule both teams agreed in a meeting becomes the thing that runs.

Speed is the obvious gain. In a 2011 Harvard Business Review article, James Oldroyd, Kristina McElheran and David Elkington reported that firms contacting a lead within an hour were nearly seven times as likely to qualify it as firms that took longer. A call task created the moment the form arrives gives a seller that hour.

Ownership is well thought through too. The tile can assign a record to the contact or lead owner, the parent account owner, a named user or team, or a dynamic value. For leads and opportunities, Dynamics 365 Sales assignment rules take precedence, so territory routing keeps working and marketing never has to maintain a second copy of it. Teams that used to build this with Power Automate can now configure it on the canvas, where marketers can read it.

How do you measure what marketing hands to sales?

CRM return on investment is measured by connecting what happens in the system to revenue. Pick a small set of figures both teams accept: time to first contact, the share of handed-over leads that become opportunities, and won revenue by originating campaign. Take a baseline before a change, then compare after a full sales cycle. Adoption numbers such as log-ins help explain the result, and the revenue figures are the result. The method is simple. The part that has historically taken effort is keeping an unbroken link between a campaign and the deal it produced.

That link is what the August update provides. Microsoft’s release note describes the old position candidly: teams relied on manual workarounds, Power Automate flows or static references that broke every time a journey was republished. Now the journey itself is a data source, and its metadata is stamped on the record as it is created.

Journey analytics also list the records each journey created and let you open them directly. Failures show their details in the same place. A marketing lead can therefore start the quarterly review with a named journey, the leads it produced and the opportunities that followed.

Why is CRM data quality important to a journey?

CRM data quality decides how useful every automated step can be. A journey fills each field on a new record from static values or from dynamic content in Dataverse, so a complete contact produces a call task with the job title, the account and the product of interest already in place. A contact with no phone number produces a task with an empty phone field, which the seller then has to chase. Good data turns each record into a short briefing, and that is why the tidy-up pays back twice: once in the journey and again in routing and reporting, which improve anyway.

Microsoft has made the setup easier to keep consistent. Under Create record settings, an administrator can define default field mappings per table and audience, and the Lead table ships with two defaults, one each for contact and lead audiences. Agree the mapping once and every journey author inherits it.

Before a new tile goes live, run it against a small sample audience and read the execution results. Microsoft recommends this because custom plug-ins and business rules only show themselves at runtime. Ten test records is an easy habit, and it gives sellers confidence from their very first task.

Your campaign audience can now change while it runs

Until October, a live journey locked its segment. To fix a missed exclusion you had to stop the journey, create a new version and start again, and the analytics ended up split across two versions. Live segment editing removes that step. An administrator turns it on under Feature switches, and the journey keeps its start date, its analytics and its history while the audience changes at the next segment refresh.

The design is careful in the right places. Before you edit, a dialog lists every journey and compound segment that depends on the segment. Before you save, a second dialog estimates the new member count and shows which journeys will shift, with a Create a copy option if you would rather leave the live campaign alone. People already inside a journey finish it undisturbed, and anyone who must leave goes into an exit segment, which is checked at every step.

It is still a preview, and Microsoft says previews are not meant for production use. So this is the moment to try it in a sandbox and decide who may edit a segment that feeds live journeys. When it reaches general availability, that decision is already made.

How do you improve CRM adoption rates in marketing and sales?

CRM adoption improves when the system saves people time in the tools they already use. Remove a step before you add one, give each role a reason to open the record, and show people that what they enter comes back to help them. A seller who receives a call task with the reason attached has a reason to trust the CRM. A marketer who can ask a question in chat and get an answer from live data will use that data more often. Adoption grows from small, repeated moments like these.

Copilot Cowork adds several of those moments. The Customer Insights plugin has three skills: customer brief and value metrics, customer outreach, and email content advisor. A marketer can type “Check whether I can email the Enterprise Renewals segment about the Q3 product update, then show me who is blocked and why.” The consent check applies the same rules as the Journeys runtime, so the answer in chat matches what the platform would do at send time. For European teams working under GDPR, that is the most useful line in the documentation.

The controls are reassuring as well. The plugin uses each person’s existing Dataverse permissions and asks for confirmation before it creates or changes a record, the same pattern as the approval gates Microsoft added for agents in September. To switch it on you need the Dataverse MCP server enabled for the environment, a Microsoft 365 Copilot licence and a Customer Insights licence.

The Sirocco perspective

We would start with one journey. Choose the buyer action your sellers value most, usually a pricing or demo request, and sit marketing and sales in the same room for an hour to agree who gets the task, what it must say and how fast it should be picked up. Build that as a Create a record tile, test it on a small audience, and turn on journey metadata from day one so the first quarter’s results have a clean source. It is a small first project, and the second journey reuses the same mappings.

We work across Salesforce, HubSpot and Dynamics 365, and the handoff conversation is the same on all three. The rules you write down for Dynamics 365 this quarter describe your own sales process, so they stay useful whatever your platform roadmap brings. That is much of the case for an independent CRM partner: the advice starts from how your revenue team works, and the tooling follows.

Microsoft now ships these updates monthly, so a handoff designed today keeps getting better without another project. Teams that connect their journeys to their sellers this quarter will walk into 2027 budget talks with a straight line from a campaign to a closed deal. If you would like to map yours, schedule a consultation with our team.

Get in Touch

Planning your first journey-to-seller handoff in Dynamics 365 Customer Insights? Tell us which buyer action matters most in your pipeline and we can help you design the journey around it.

So where do you start?

As your long-term partner for sustainable success, Sirocco is here to help you achieve your business goals. Contact us today to discuss your specific needs and book a free consultation or workshop to get started!