Connecting sequences to records

What it does

Connecting is the act of putting a record onto a sequence so its steps start appearing in a seller's Up next list. Nothing happens from authoring a sequence alone — a record has to be attached to it, either by a person clicking a button or by something automated doing it for them.

Key facts

Four routes in: from the sequence itself via the Connected records tab, from a record type grid using the Connect sequence command, from an individual record form, or programmatically from Power Automate.
The sequence must be Active. Draft and deactivated sequences don't appear in the picker at all, which is the usual reason for "the sequence isn't showing".
Grid connection is multi-select, so a seller or manager can put a filtered view of leads onto a cadence in one action. This is the workhorse in practice.
The automated route is the msdyn_ConnectSequence unbound action. It takes RegardingEntityId, RegardingEntityName and SequenceId as required parameters, with SegmentId, WaitTime and Source optional; WaitTime lets you stagger a batch rather than firing everyone's first step at once.
A record can be connected to more than one sequence at the same time. That's deliberate, to let different people work the same account in parallel.
Connecting from within a sequence only offers records not already connected to that sequence.
Once connected, the sequence's activities show in the record's Summary section and in the Up next widget under My work, in the order the sequence defines.
Connecting and disconnecting needs more than the Sequence table: Create and Append To on Sequence, plus Create, Read, Write, Append, Append To and Assign on Sequence Target, and Create, Read, Write, Append and Assign on Sequence Target Step. All of it sits on the Custom Entities tab of the security role editor.
Who the work lands on is decided by the sequence's own Assign to setting, not by who pressed Connect.
A known issue: if a segment connects the same sequence to the same record more than once for the same seller, the Up next widget shows duplicate activities.

When to use / skip

The real decision here isn't whether to connect records, it's whether connection should be manual or automatic. Manual connection keeps sellers in control and keeps volumes honest — they put a lead on a cadence because they've decided to work it. Automatic connection via a flow or a segment scales, and it's the only sane approach when a marketing system is dropping hundreds of leads a week, but it also means the system starts generating work without anyone agreeing to it.

Most implementations should start manual, with grid multi-select as the primary route, and add automation once the cadence has proven itself. The exception is high-volume inbound, where manual connection just won't happen and you'll end up with a well-designed sequence nobody uses.

Be careful with multiple sequences on one record. It's genuinely useful for account-centric selling where a relationship manager and a specialist both have a plan. It's actively harmful when it happens by accident, because the seller sees two overlapping to-do lists and trusts neither.

Configuration decisions

Manual, automatic, or both — and if automatic, whether that's a Power Automate flow calling msdyn_ConnectSequence or segment-driven connection.
The entry criteria for automatic connection, expressed as something you can actually query. "Qualified leads from the web form" needs a field behind it.
Whether to use the WaitTime parameter to stagger batch connections, and what the stagger should be.
Whether multiple concurrent sequences per record are allowed as a matter of policy, and if so which combinations are sensible.
Which security roles get the Sequence Target and Sequence Target Step privileges — this is what separates users who can connect from users who can only see.
What happens on re-entry: whether a record that has finished a sequence can be put back on the same one, and who decides.

Gotchas

The privilege set for connecting is broader than anyone guesses. Bespoke security roles built by copying Salesperson often miss Sequence Target Step, and the failure looks like a permissions error at the moment of connection rather than at login.
A flow that connects records with no filter and no wait will bury a sales team overnight. Test automatic connection against production-shaped volumes, not five test leads.
Sequences that aren't activated simply don't appear in the picker. There's no message explaining why.
Connection assigns work using the sequence's assignment rule. If that's set to Record owner and ownership is about to change, the work follows the old owner until something reassigns it.
Duplicate connections through segments produce duplicate Up next entries, which sellers read as a system fault and report as one.
Disconnecting is available from the record and from the sequence's connected records view, but it isn't obvious to sellers. Without training they abandon the activities instead, which leaves stale open tasks behind.

Consultant notes

Build the security role change for Sequence, Sequence Target and Sequence Target Step as a deliverable in its own right, and test it as a real seller rather than as an admin.
Demo grid multi-select connection to sales managers. It's the feature that makes the whole thing feel practical to them, and it takes thirty seconds to show.
If the client wants automatic connection, agree the entry criteria in writing and put a volume cap or a staged rollout behind it for the first month.
Check connection volumes against the Sales Enterprise allowance of 1,500 sequence-connected records per month before switching automation on.
Train sellers explicitly on disconnecting. It's the difference between clean data and a timeline full of tasks nobody will ever do.

Worth another look if segment-driven connection or the msdyn_ConnectSequence parameters change, or if a per-record sequence limit is introduced.