Almanac
Microsoft/d365salesDynamics 365

Consultant-focused KB for Microsoft Dynamics 365 Sales: implementation notes, gotchas, and configuration decisions beyond the official docs — across pipeline management, opportunities, forecasting, sequences, sales accelerator, Copilot, integrations, administration, and licensing.

d365sales/05-sequences-and-cadences/feature-sequence-designer-and-activation.md
feature-sequence-designer-and-activation.mdv1 · history
CurrentApplies to EnterpriseUpdated 6 days agoSource Microsoft Learn ↗

What it does

A sequence is an ordered set of steps — calls, emails, waits, conditions, small automations — that you attach to a record so the seller gets a prescribed next action instead of guessing. You build it in a drag-and-drop designer under Sales Insights settings and it does nothing at all until you activate it.

Key facts

  • The designer lives at Change area > Sales Insights settings > Sales accelerator > Sequences. It is not in Advanced Settings and not in the maker portal, which catches out people who expect it to behave like a business process flow.
  • A maximum of 250 active sequences can exist in an organisation at any one time. Drafts and deactivated ones don't count against that.
  • Each sequence is bound to one entity, picked on the properties pane at creation. Lead is selected by default.
  • Available entities come from sales accelerator setup, not from the sequence designer. Leads, opportunities, accounts and contacts are enabled by default. Custom tables can be added, but the table needs Activities, Connections and Sending email turned on, and organisation-owned tables are not supported at all.
  • New sequence gives you two starting points: Use template or Use blank sequence. Templates are a starting shape, not a managed asset — once created, a template-derived sequence is just a normal sequence.
  • Assignment is a property of the sequence, set under Assign to. Record-level options are Record owner (the default) and Team member specified in a record field. Team-level options are Owner team and Access team, each of which can narrow to individuals with a condition.
  • For Owner team and Access team assignment, the record's owner must actually be that team. If the record is owned by a user, team-level assignment has nothing to bite on.
  • Activation fails if the last step is Set wait time. Delete the trailing wait, save, then activate.
  • With a Sales Enterprise licence you get 1,500 sequence-connected records per month. Past that you're into an upgrade conversation, not a support ticket.
  • Authoring needs Create, Read, Write and Delete on the Sequence table, which out of the box sits on System Administrator, Sequence manager, Sales Manager and Salesperson. The Assign command hands a user or team full rights over a sequence — view, edit and delete — with no read-only equivalent.

When to use / skip

Sequences earn their keep where outreach is genuinely repeatable and someone in the business actually owns the cadence: inbound lead follow-up, SDR prospecting, renewal chase, post-event nurture. If the sales motion is six enterprise deals a year run by three people who know exactly what they're doing, a sequence is bureaucracy with a designer attached and they will ignore it.

The other honest test is whether anyone will maintain them. Sequences rot faster than most configuration because they encode messaging, and messaging changes quarterly. If there's no named owner in the business who will revise them, build two or three and stop, rather than shipping fifteen that nobody trusts by month four.

Also worth saying plainly: sequences are not marketing automation. They generate work for a seller and, in the automated cases, send on the seller's behalf. If the client is describing multi-thousand-record nurture campaigns with consent management and unsubscribe handling, that's Customer Insights - Journeys, and you should say so early rather than discover it in UAT.

Configuration decisions

  • Which entity each sequence targets, and therefore how many near-duplicate sequences you'll end up maintaining if the same cadence is wanted on both lead and opportunity.
  • Which record types to enable in sales accelerator setup before you start authoring — the designer only offers what's already enabled, and adding a custom table has prerequisites on the table itself.
  • The assignment model: record owner is simple and right most of the time; team-based assignment only makes sense if records are genuinely team-owned, which changes your ownership design.
  • Whether to seed from templates or start blank. Templates are quicker to demo and slower to explain; blank sequences are easier to keep to the client's actual language.
  • Naming and tagging convention, decided before the first ten exist. With a 250 cap and no folders, the list view is your only navigation.
  • Who holds the Sequence manager role — that is, who is allowed to change what sellers are told to do next, and whether that's IT or the sales operations team.

Gotchas

  • The 250 active limit is organisation-wide, not per business unit or per team. Multi-country rollouts that clone one cadence per market chew through it faster than anyone expects.
  • Assigning a sequence to a user or team grants delete rights along with everything else. There's no way to hand out "can see and use but not change".
  • Custom tables must be user or team owned. If someone has already built the target table as organisation-owned, that's a rebuild, not a setting.
  • Removing a record type from the sales accelerator setup list does not disconnect records already running sequences on that type. They carry on quietly.
  • Sequences are configuration records, not solution components in the way consultants expect. Plan how they get from dev to production early; don't assume a managed solution carries them.
  • A sequence that ends in a wait will look fine in the designer and fail only when you press Activate, usually in front of the client.

Consultant notes

  • Demo the seller's "Up next" experience first, not the designer. Sales stakeholders buy the outcome; showing them the branching canvas early invites two hours of hypothetical edge cases.
  • Get a named cadence owner in the business written into the project plan. This is the single biggest predictor of whether sequences survive six months after go-live.
  • Push back on "let's build one per product per region" in workshop one. Start with two, measure, then multiply — the cap and the maintenance load are both real.
  • Before go-live, check the Enterprise 1,500 connected-records-per-month ceiling against the client's actual lead volumes. It's an easy number to blow through with automatic connection turned on.
  • Confirm the security role assignment for sales operations users explicitly. The default roles cover the common cases, but bespoke role designs almost always miss the Sequence tables.

Worth another look if the active-sequence cap or the Enterprise connected-record allowance moves, or if custom-table support changes.

Was this accurate?
Related
Sequences or marketing journeys for outreach11-decision-guidesSequence step types05-sequences-and-cadencesConnecting sequences to records05-sequences-and-cadencesCondition steps and branching05-sequences-and-cadencesExit criteria and leaving a sequence05-sequences-and-cadencesSetting up the sales accelerator06-sales-accelerator