To eliminate that tedious click-and-drag marathon, Microsoft has rolled out a bulk reassignment capability on the Dynamics 365 Field Service Schedule Board. Tracked under Microsoft's AI at Work Roadmap ID 576822 and listed in the 2026 release wave 1 plan as reaching general availability in June 2026 for Worldwide (Standard Multi-Tenant) web environments, the Move multiple bookings at once to new resource feature allows dispatchers to highlight multiple bookings simultaneously and hand them over to another resource in a single operation. While the feature is enabled automatically for end users, administrators and schedulers who rely on tight customer arrival windows need to understand how this right-click action actually handles travel time under the hood—because what the high-level roadmap summary says and what the system's routing math actually does are two slightly different stories.
What Bulk Reassignment Does on the Schedule Board
At its core, this update targets the repetitive manual updates that bog down dispatch operations during staffing disruptions. Previously, if a technician called out for the remainder of a three-day project or a dispatcher needed to rebalance workloads between teams, every affected booking had to be dragged or edited individually.
According to Microsoft's 2026 release wave 1 documentation and a July 2026 Dynamics 365 product blog post by Product Manager Michael Kelleher, the bulk Reassign to capability lets schedulers select a group of bookings on the web-based Schedule Board and redirect ownership in one step. Microsoft positions the tool for three primary operational scenarios:
- Covering unexpected absences: Quickly vacating an unavailable technician's queue without rebuilding each booking from scratch.
- Rebalancing workloads: Moving excess afternoon or late-week jobs from an overloaded specialist to a colleague with open capacity.
- Shifting work between teams: Consolidating project tasks under a different resource or crew when operational priorities pivot.
Because the feature is automatically enabled for end users on the web platform, IT administrators do not need to flip a feature switch in the Power Platform admin center or deploy a custom Schedule Board client extension to expose the right-click option.
Section Summary: Bulk reassignment in Dynamics 365 Field Service is a generally available, automatically enabled web Schedule Board enhancement that lets dispatchers transfer multiple selected bookings to a new resource in one action.
Step-by-Step: How to Reassign Multiple Bookings at Once
Microsoft Learn's current Schedule Board documentation breaks down the interaction model into a straightforward keyboard-and-mouse workflow, while distinguishing multi-booking resource reassignment from time-shifting actions.
To move multiple bookings to a new resource:
- Open the Schedule Board in your Dynamics 365 Field Service web environment.
- Multi-select the target bookings on the timeline by holding down Ctrl and clicking each booking in Windows, or holding Command and clicking in macOS.
- Right-click on any one of the highlighted bookings to open the context menu.
- Select Reassign to from the right-click menu and choose the target resource to transfer ownership of the selected bookings.
Reassign To vs. Move By vs. Move To
When dispatchers right-click on the Schedule Board, the available tools depend on whether they are acting on a single record or a multi-select batch, and whether they are changing who does the work or when it happens. Microsoft Learn's Schedule Board documentation defines these distinct pathways:
| Schedule Board Action | Selection Scope | Primary Function | Travel Time & Resource Scope Notes |
|---|---|---|---|
| Drag-and-drop | Single booking | Drag a booking across the timeline to a new time slot or resource row | Preserves duration; start time represents estimated arrival with travel time included; limited to resources visible on the current board tab. |
| Move to (right-click) | Single booking (also referenced in Microsoft's blog for batch time-shifts) | Reassign a booking or change its start date and start time | Can switch the resource filter from Resources on this tab to All resources; recalculates travel time from the new start point. |
| Move by (right-click) | Multiple bookings (Ctrl+click / Cmd+click) | Shift all selected bookings forward or backward by a consistent time offset (e.g., push three bookings back by two days) | Designed for uniform schedule delays such as weather disruptions or project pauses. |
| Reassign to (right-click) | Multiple bookings (Ctrl+click / Cmd+click) | Transfer selected bookings to a different resource while keeping their existing scheduled times | Recalculates travel time from the new resource's starting location, which shifts the booking slot forward. |
Move bookings (... menu) | Bookings matching a specific status | Move bookings of a selected status to a different day via Show more schedule board actions (...) | Preserves existing times and booking parameters across the day change. |
Note on UI terminology: While Microsoft's July 2026 blog post informally refers to multi-booking time-offset shifting as "Move To", Microsoft Learn's authoritative operating documentation updated in September 2026 explicitly labels the multi-booking right-click offset option Move by, reserving Move to for the single-booking dialog. Dispatchers training their teams should point users to Move by for time offsets and Reassign to for changing technicians.
Section Summary: Schedulers can Ctrl-click (Windows) or Command-click (macOS) multiple bookings on the Schedule Board and right-click to choose either Reassign to (for changing the assigned technician) or Move by (for shifting bookings forward or backward by a fixed time offset).
The Catch: Why "Unchanged Timing" Still Shifts Your Schedule
Here is where veteran Dynamics administrators earn their keep. If you only read the high-level AI at Work Roadmap description or the archived 2026 release wave 1 plan page, you will see a comforting promise: "Booking timing and duration remain unchanged, ensuring continuity while ownership updates seamlessly".
Hold the phone. If Technician A lives five minutes from the first job site and Technician B is driving in from forty-five minutes across town, how can the booking timing possibly remain unchanged?
According to Microsoft Learn's official Schedule Board documentation, there is a critical operational caveat that every dispatch team needs to understand: when you use Move to or Reassign to to reassign a booking, Dynamics 365 Field Service automatically recalculates travel time from the new resource's starting point, and shifts the booking slot forward compared to the original booking.
Microsoft explicitly flags this in its documentation as expected behavior and contrasts it with standard drag-and-drop scheduling:
- When you drag and drop a booking onto a timeline slot, the slot's start time represents the estimated arrival time, with travel time already baked in prior to that mark.
- When you use Reassign to (or Move to), the system preserves the underlying time reference but recalculates travel routing from the new start point, pushing the resulting booking block forward on the board to account for the new technician's drive.
Practical Guidance for Dispatchers
What does this mean on a busy Monday morning? If you bulk-reassign five tightly sequenced service calls to a backup technician whose home base or prior job is farther away, those recalculated travel segments can cascade into shifted arrival slots.
After executing a bulk Reassign to action, dispatchers should always visually inspect the target resource's timeline row on the Schedule Board to verify that:
- Recalculated travel times have not pushed an appointment past a promised customer SLA arrival window.
- Back-to-back transferred bookings have not overlapped with each other or with jobs that were already sitting on the receiving technician's calendar.
Section Summary: Although roadmap summaries state that bulk reassignment leaves booking timing and duration unchanged, Microsoft Learn's technical documentation confirms that Reassign to recalculates travel time from the new starting point and shifts the booking slot forward. Dispatchers must review the resulting schedule for SLA or overlap impacts.
Bulk Reassignment vs. Automated Optimization
It is also worth drawing a sharp line between manual bulk actions and automated schedule optimization. Even though Microsoft's roadmap entry carries the title "Optimize resource scheduling - Move multiple bookings at once to new resource," this right-click tool is an interface productivity shortcut, not an algorithmic optimization engine.
While the roadmap description states that bookings can be redirected to another "qualified resource", Microsoft's documentation for the bulk Reassign to workflow does not claim that the right-click action automatically audits skill certifications, territory rules, resource capacities, or optimal drive routes across your fleet. Furthermore, while the single-booking Move to dialog explicitly documents a filter toggle to switch between Resources on this tab and All resources, the multi-booking guidance focuses strictly on streamlined selection and reassignment.
Organizations that want Dynamics 365 Field Service to automatically evaluate skills, territories, travel minimization, and working hours across dozens of jobs have two separate Microsoft capabilities designed for that job:
- Resource Scheduling Optimization (RSO) Add-on: A paid, rules-based engine that automatically schedules multiple jobs at once to the best-equipped resources while minimizing travel time and maximizing utilization.
- Scheduling Operations Agent: A Copilot-powered capability in Field Service aimed at proposing automated schedule adjustments and handling exceptions for smaller groups of resources.
Bulk Reassign to, by contrast, is built for the human in the loop—giving an experienced dispatcher who already knows which technician should take over a batch of work the ability to execute that transfer in three clicks instead of thirty.
A Note on Microsoft's Evolving Roadmap Records
For IT pros tracking Dynamics 365 deployments this autumn, you may notice a quirk when pulling up the original 2026 release wave 1 plan page on Microsoft Learn. As of October 2026, Microsoft has marked the standalone release-plan page as archived and no longer maintained, directing administrators instead to the unified AI at Work Roadmap (where this feature lives under ID 576822) for status tracking and to Microsoft Learn product documentation for active operational guidance.
Along with bulk reassignment and bulk time-shifting (Move by), Microsoft's recent wave of everyday Schedule Board quality-of-life updates also introduced a dedicated primary Map view, optional calendar week numbers controlled via Dynamics personalization settings, and Partial Cancellation for trimming specific days out of multi-day bookings without tearing down the entire appointment. Together, these updates show that while AI agents get top billing on stage, Microsoft hasn't forgotten the keyboard shortcuts and right-click menus that keep field service dispatchers sane during the morning rush.