Status: preview now, GA targeted for December
The Microsoft 365 roadmap entry (ID 577810) lists the feature as in development. It gives preview availability as October 2026 and general availability as December 2026 for the Worldwide (Standard Multi-Tenant) cloud. Roadmap dates are estimates and can change.
Microsoft's "What's new" page already lists it under the October 2026 update, in the public preview section.
The roadmap metadata says the feature is "enabled automatically" for admins, makers and marketers. The current Learn documentation says otherwise. It says live segment editing is off by default and an administrator must turn it on. Plan around the documentation, not the roadmap blurb.
What changes for marketers
Microsoft describes the old process this way: stop the journey, create a new version and restart it. That interrupted the campaign and split analytics across two journey versions.
With the feature on, you edit the segment definition while the journey keeps running. Saving updates and republishes the segment. It doesn't touch the journey, so:
- The journey isn't stopped or paused.
- No new journey version is created.
- The journey keeps its start date, analytics and history.
- People already in the journey continue without interruption.
This applies only to the audience definition. Changing a tile, a message or entry criteria still means editing the journey, and that still creates a new version.
How to turn it on and use it
- Enable the switch (admin). Go to Settings > Overview > Feature switches. Under Segmentation, set Edit live segments used in live journeys to On, then select Save. While the switch is off, the old locked behavior applies.
- Open the segment. Go to Audience > Segments and open the segment. Select the More commands ellipsis, then Edit.
- Review dependencies. The "Edit in-used segment" dialog lists the live journeys that use the segment and any segments that include it. Select Continue.
- Change the query. The segment stays live on its current definition while you work. Your edits stay local to your browser session. Other users who open the segment see the original definition.
- Select Finish editing. A dialog shows the estimated Original members against New members. It also lists journeys with changes, journeys without changes, and affected compound segments.
- Choose an outcome. Save applies the change to the live segment. Create a copy saves your changes as a new segment and leaves the original alone. Cancel returns you to editing.
If you close the tab or navigate away before saving, your changes are discarded.
When the change actually takes effect
Saving doesn't trigger an instant recalculation. A segment execution already in progress finishes with the old definition. The new one is picked up at the next execution. For a short time after you save, members from the old definition can still arrive.
| Journey type | When your change applies |
|---|---|
| One-time | Only if saved and recalculated before the audience snapshot taken at the start of the run |
| Recurring | From the next occurrence. The running occurrence keeps its original audience |
| Ongoing | At the next segment refresh, when newly qualifying people are admitted |
| Trigger-based | Once the segment has refreshed |
The segment's role in the journey matters too:
- Entry audience: follows the journey-type timing above.
- Exclusion segment: affects people admitted after the next refresh. It doesn't remove anyone who has already entered.
- Exit (suppression) segment: checked at every step, so a change reaches each person at their next step.
- Condition: evaluated when a person reaches that condition.
- Parent (compound) segment: applies after the parent re-evaluates.
Editing a child segment takes two evaluations. The child re-evaluates first, then the parent. Only then does the journey see the change. Editing the parent directly skips one stage.
Gotchas
Narrowing a segment doesn't eject anyone. People who no longer match but have already entered still finish the journey. Anyone who has already finished doesn't re-enter. To stop people mid-journey, use an exit segment. Microsoft calls it the fastest-acting option.
Static groups are read-only during live editing. You can't upload a CSV, create a manual static list, add or remove individual members, or delete a static group. Dynamic, query-based groups remain editable. For static lists, make a copy or stop the journey.
The member count is an estimate. Use it as a sanity check on the size of the change, not as an exact preview of membership.
One editor at a time. Concurrent edits can overwrite each other.
Customer Insights - Data segments are different. They're still edited in that product. The change then has to complete a refresh and sync into Journeys, so allow more time.
Preview means preview. Microsoft says preview features aren't meant for production use and may have restricted functionality. Test in a sandbox before you rely on it for a revenue-critical campaign.
Audit trail
Live editing makes it easier for a segment to change under a running campaign, so Microsoft added ways to see when it happened. On the Members and Insights tab, the segment size chart marks saved changes with vertical lines for Current edit and Previous edit. The Segment details pane shows Last query change, with the date, time and user. Neither shows what changed, and only the latest edit identifies its author. If a journey's audience shifts unexpectedly, compare the membership change against the Current edit timestamp.
Analysis
This is a practical fix. Campaigns rarely survive contact with real analytics unchanged. A stray condition or a missing exclusion used to force a stop, a new version and split reporting. Keeping analytics in one journey history is a real gain.
The flip side is governance. Anyone who can edit a segment can now quietly change a live audience. Admins should think about who gets the feature switch, and about a review step for edits to segments tied to high-volume journeys. The dependency dialogs help, but they only work if people read them. Given the timing rules above, marketers shouldn't promise stakeholders that an audience change applies instantly.
A related docs update reflects the shift. The segmentation overview now says that if a segment is used by a live journey, you can still change it without stopping the journey. The known-issues page still carries the older limitation, so expect some documentation inconsistency until GA.
Checklist before you enable it
- Confirm your environment has the feature switch available and that the preview is acceptable for your policies.
- Decide who gets edit rights on segments used in live journeys.
- Note the refresh schedule for your critical segments, so you know how long "next refresh" is.
- Use exit segments, not narrower entry segments, when you need to stop people mid-journey.
- Use Create a copy when you want to experiment without touching a live campaign.