For Power Platform and Dynamics 365 teams

Every change in its lane.Every step on the record.

Can this work item ship on its own? Lanestep tells you before every step. Pick what each work item changed, down to a single component, and Lanestep moves it through your environments to Prod, with a record of what got there and why.

Workspace map

Feature and hotfix tracks feeding one Stage and one Prod

Map of a workspace with a feature track and a hotfix trackThe feature track builds in Dev 02 and tests in Test 02. The hotfix track builds in Dev 01, which mirrors Prod, and tests in Test 01. A guard sits on every step inside a track. Both tracks feed one release line: Stage, then Prod, with a guard on the step between them. Dashed arrows show each release that reaches Prod being synced into the build and test environments of the tracks. Shown: Stage is booked by REL-1004. The hotfix CHG-1003 has taken Stage and sits in front, ready for Prod; the feature CHG-1002 waits behind it, marked Needs retest.Feature trackHotfix trackRelease lineSync from ProdSync from ProdDev 02BuildTest 02TestDev 01Build, mirrors ProdTest 01TestStageRelease candidateProdShips by releaseBooked by REL-1004Kept the workSyncedCHG-1002Needs retestOlder copyRebuiltIn ProdCHG-1003Took StageIn ProdMap of a workspace with a feature track and a hotfix trackThe feature track builds in Dev 02 and tests in Test 02. The hotfix track builds in Dev 01, which mirrors Prod, and tests in Test 01. A guard sits on every step inside a track. Both tracks feed one release line: Stage, then Prod, with a guard on the step between them. Dashed arrows show each release that reaches Prod being synced into the build and test environments of the tracks. Shown: Stage is booked by REL-1004. The hotfix CHG-1003 has taken Stage and sits in front, ready for Prod; the feature CHG-1002 waits behind it, marked Needs retest.Feature trackHotfix trackRelease lineDev 02BuildTest 02TestDev 01Build, mirrors ProdTest 01TestStageRelease candidateProdShips by releaseBooked by REL-1004Kept the workSyncedCHG-1002Needs retestOlder copyRebuiltIn ProdCHG-1003Took StageIn Prod
  • Deploy
  • Sync from Prod
  • Guard
  • Feature change
  • Hotfix change
Feature track
Dev 02 to Test 02. Changes are built in Dev 02 and tested in Test 02. Within the track, each change moves on without waiting for other work.
Hotfix track
Dev 01 to Test 01. Changes are built in Dev 01, which mirrors Prod, and tested in Test 01. A hotfix can take Stage even when a release has booked it.
Release line
Stage to Prod. Stage, then Prod, shared by every track. Changes from all tracks meet at Stage. Prod receives them only in a release, after the guards run.
Sync from Prod
Prod to every other track. When a release reaches Prod, Lanestep syncs it into every track it did not come from. Each clash it finds needs a decision first.
  1. Step 1: CHG-1002 is built in Dev 02 and tested in Test 02.
  2. Step 2: Its release, REL-1004, books Stage, which keeps changes from other releases out.
  3. Step 3: Hotfix CHG-1003 is built in Dev 01 and tested in Test 01. It overtakes CHG-1002 and takes the booked Stage. CHG-1002 is marked Needs retest. (the moment the map shows)
  4. Step 4: CHG-1003 ships to Prod in a release of its own.
  5. Step 5: The release syncs from Prod into the feature track. In Dev 02 the sync finds a clash on common.js, and the team keeps its work.
  6. Step 6: The older copy guard holds CHG-1002. Shipping it as it is would undo CHG-1003 in Prod.
  7. Step 7: CHG-1002 is rebuilt and reaches Stage again.
  8. Step 8: CHG-1002 ships to Prod, the booking ends, and the release syncs into the hotfix track.

The problem

Shared environments turn every release into a negotiation

Power Platform teams often grow faster than their release process. More makers, more solutions and a hotfix track all meet in one Stage and one Prod.

  • Everyone builds in the same place

    Many makers and solutions share Dev, Stage and Prod. It is hard to tell whose change is in which environment.

  • Hotfixes and features collide

    A hotfix built from an older copy can quietly undo a feature in Prod. In Dataverse, the last managed layer wins.

  • Whole solutions or nothing

    The usual release tools move one whole solution at a time. Finished work waits for unfinished work in the same solution.

  • A spreadsheet of what is where

    Someone tracks which change is in which environment in a spreadsheet, and updates it by hand after each deployment.

  • Proof by screenshot

    Approvals live in email and chat. The change board gets screenshots and a meeting instead of a record.

How it works

One record behind every step

A change is everything one work item changed. Lanestep keeps one record for each change: its components, the environments they reached, their versions and the track they came from. Every check and every report reads from that record.

  1. Set up your tracks

    Add your environments and group them into tracks, such as a feature track and a hotfix track. Every track feeds the same Stage and Prod.

  2. Pick what each work item changed

    Pick whole solutions or single components in the build environment. Lanestep exports the change once, and that same export goes to every environment.

  3. Move each change on its own

    A change goes to its test environment without waiting for other work. At Stage, you choose which changes go to Prod. A release can hold a single change.

  4. Sync and keep the record

    When a release reaches Prod, Lanestep syncs it into every other track. You decide each clash it finds. The audit trail and the evidence pack build up as you go.

Follow a change from Dev to Prod

Guards

Checked before every step

A guard is an automatic check. Before a release goes to Prod, Lanestep runs every guard. Each finding says what the guard caught and how to clear it.

  • A finding holds the release. For example, an older copy of a component would undo a change already in Prod.
  • Where your policy allows, a person can pass a finding with a written reason. The reason stays on the release.
  • Lanestep flags two changes that touch the same component when they are exported, well before release day.

REL-1004

Draft

Before Prod: what each guard found

  • Blocks

    Older copy

    Shipping CHG-1002 would undo CHG-1003 in Prod.

    To clear it: Rebuild CHG-1002

  • Needs retest

    Retest

    CHG-1003 replaced common.js in Stage after CHG-1002 was tested.

    To clear it: Mark CHG-1002 retested

  • 1 of 2

    Approvals

    Needs 2 approvals from people who built none of its changes.

  • Clear

    Freeze

    No freeze holds Prod.

The product

Everything between Dev and Prod

Ship, govern and measure from one record, so the release, the evidence and the reports agree.

  • Ship

    Ship by work item, down to one column of one table. Every track feeds one Stage and one Prod, and a compensating release undoes a release where Dataverse allows.

  • Govern

    Sign-in with Microsoft Entra ID, roles, Stage booking, approvals with separation of duties, freezes and an audit trail where entries can only be added. Each release gets an evidence pack.

  • Insights

    Delivery and risk, read from the record rather than from what people reported, down to the components behind the most rebuilds and failures.

  • AI suggestions

    AI suggests a plain summary of each release’s risk, draft release notes and an order for changes that overlap. Each is marked as a suggestion, and a person decides.

  • Keep your board

    Lanestep links each change to its work item in Azure Boards or Jira, shows the item’s title and state, and comments as the work reaches each environment. It never edits the item.

  • Works with your tools

    Deploy through Azure Pipelines or GitHub Actions, let Azure DevOps checks and Power Platform Pipelines ask Lanestep before Prod, and keep Teams, Slack and ServiceNow up to date.

See your own tracks in Lanestep

Book a demo to walk through your environments, tracks and change board with the team building Lanestep.