Tracked under Microsoft's AI at Work Roadmap ID 576768 (and communicated to tenant administrators via Microsoft 365 Message Center post MC1472792 ), this update allows organizations to pre-select which resource allocation method applies automatically when staff book resources. While it will not magically invent more hours in the workday, it gives system administrators a way to align the software's default behavior with company scheduling policies—while still letting schedulers override the default in the moment when a specific project demands an exception.
Rollout Timeline and Version Nuances
For enterprise IT and Dynamics administrators keeping a close eye on deployment rings, the rollout timeline for this feature requires a quick look across three different Microsoft trackers, each reflecting a slightly different stage of the release pipeline:
- Roadmap ID 576768 & Release Wave Plans: On the AI at Work Roadmap and in the Dynamics 365 2026 release wave 1 plan on Microsoft Learn, the feature is listed for Web across Worldwide (Standard Multi-Tenant) cloud instances, with a Preview milestone of September 2026 and an estimated General Availability target of March 2027. Both the roadmap and the release plan note that delivery timelines are estimates and remain subject to change.
- Message Center Advisory (MC1472792): According to the Microsoft 365 Message Center archive (MC1472792), Microsoft announced on September 16, 2026, that the capability to set a default booking method for the Schedule Board and Schedule Assistant would reach public preview on September 30, 2026.
- September 2026 Core Release Notes: Meanwhile, Microsoft Learn's What's new September 2026 - Project Operations Core documentation lists Configure Default Booking Methods among the features included in the September 2026 release for Project Operations in a Microsoft Dataverse environment running version 4.171.3551.6.
Why does the roadmap still display an "In development" status alongside a March 2027 general availability date while the September release notes already document the feature? In the world of Dynamics 365 and Dataverse, a feature landing in a specific monthly Core build or entering public preview does not mean it is universally flipped on across every customer deployment worldwide. As Microsoft's roadmap and release plan specify, the capability is gated behind feature control and must be enabled by administrators, makers, or analysts for end users.
Section Summary: The configurable default booking method entered public preview at the end of September 2026 (associated with Dataverse version 4.171.3551.6 in Project Operations Core) and remains on track for broader General Availability in March 2027 under Roadmap ID 576768.
How to Configure Default Booking Methods in Project Operations
Once the feature is enabled through feature control in your environment, setting up the organization-wide defaults does not happen inside a user's personal browser preferences—it is configured at the Organization Unit parameter level. Note that while Microsoft's roadmap notes the feature requires enabling through feature control, Microsoft Learn's booking allocation documentation focuses directly on the parameter steps below and states that these instructions apply specifically to Project Operations.
According to Microsoft Learn's Booking allocation methods documentation, system administrators can establish the defaults by following these exact steps:
- Sign in to Dynamics 365 Project Operations using an account with system administrator privileges.
- In the left navigation pane, switch the working area to Settings.
- Under the General group, select Parameters.
- When the list of organization units loads, double-click (or double-tap) the Organization Units row on any column area that is not a hyperlink.
- Scroll down the parameter form until you reach the Scheduling section.
- Review and configure the two separate default settings:
- Schedule Assistant: Choose between Remaining Requirement and Full Requirement.
- Schedule Board: Choose between Front Load Hours, Evenly Distribute Hours, Full Capacity, Remaining Capacity, and Percentage Capacity.
- Select your preferred default method (or methods) and click Save.
- A confirmation pop-up dialog will appear warning that the configuration change can take up to five minutes to reflect on the Schedule Board. Select OK.
That five-minute propagation window is worth keeping in mind if you are testing the change in a sandbox environment; if you immediately open the Schedule Board in another tab and see the old default, give the backend cache a few minutes to catch up before troubleshooting.
Section Summary: System administrators configure separate default booking methods for the Schedule Assistant and Schedule Board inside Settings > Parameters > Organization Units > Scheduling, with changes taking up to five minutes to take effect on the board.
Why Your Default Choice Matters: The Overbooking Trap
Microsoft's business-value summary for this feature emphasizes that standardizing the default booking allocation method reduces the risk of incorrect bookings caused by inconsistent defaults, minimizes rework and cancellations, and saves time for resource managers. That is a fair assessment of workflow ergonomics—fewer clicks mean fewer accidental selections.
However, a standardized default is only as safe as the allocation math behind it. If an administrator sets an aggressive allocation method as the default, resource managers who blindly click "Book" can still double-book staff without realizing it. In fact, Microsoft Learn explicitly warns that three of the available Schedule Board allocation methods ignore existing commitments and do not notify the user when a resource becomes overbooked.
To help administrators decide which default makes the most sense for their organization, here is how all six booking allocation methods documented by Microsoft Learn actually behave under the hood, applies to both Project Operations Integrated with ERP and Project Operations Core:
| Allocation Method | Available as Schedule Board Default? | Accounts for Existing Bookings? | Can It Overbook Without Warning? | How It Distributes Hours (Microsoft Learn Examples) |
|---|---|---|---|---|
| Front Load Hours | Yes | Yes | No (may throw an error if no capacity remains) | Consumes available capacity on a "first-in-first-consumed" basis. Booking 20 hours across a 5-day (8 hr/day) week with 0 existing bookings yields 8, 8, 4, 0, 0. If 20 hours are already booked in that pattern, a second 20-hour booking automatically fills the back half: 0, 0, 4, 8, 8. |
| Remaining Capacity | Yes (only when booking directly to a project via Schedule Board) | Yes | No | Books only the unallocated capacity within the date range. If a resource has a 40-hour weekly capacity and 10 hours already booked, booking that week allocates the remaining 30 hours. |
| Full Capacity | Yes | No | Yes | Books 100% of the resource's calendar capacity across the selected dates regardless of other projects. A 5-day booking on an 8 hr/day calendar adds a flat 40 hours on top of any existing work. |
| Percentage Capacity | Yes | No | Yes | Books a set percentage of calendar capacity evenly across the date range. At 50% over a 40-hour, 5-day week, it books 20 hours (4 hours/day), added directly on top of any existing bookings. |
| Evenly Distribute Hours | Yes | No | Yes | Spreads a specified hour total equally across the chosen days without checking remaining capacity. Booking 20 hours over 5 days adds 4 hours/day, even if the resource is already at capacity. |
| None | No (only available from a project's Team tab) | N/A | No | Adds the user to the project team without creating capacity-absorbing bookings (used by default for the project manager who creates a project so the record has an owner and approver). |
Choosing the Right Default for Your Workflow
Looking at the mechanics above, the operational tradeoff becomes clear:
- For strict capacity protection: If your primary goal is preventing silent overbookings when resource managers work directly on the Schedule Board, Front Load Hours and Remaining Capacity are the only Schedule Board methods that actively check existing bookings before committing time. Front Load Hours is particularly unforgiving of over-allocation: because it checks available capacity first, Microsoft notes it cannot overbook and may return an error message if the resource has no remaining capacity to absorb the request.
- For predictable daily pacing: Many matrixed organizations prefer Evenly Distribute Hours or Percentage Capacity because staff split their days across multiple concurrent projects (for instance, four hours every morning on Project A and four hours every afternoon on Project B). Setting either of these as the Schedule Board default speeds up split-day scheduling, provided your schedulers visually verify availability on the board first—because the system will not stop them from stacking three 50% bookings on the same person.
- For the Schedule Assistant: Because the Schedule Assistant is typically invoked to fulfill defined resource requirements, its default options are scoped separately to Remaining Requirement or Full Requirement, allowing admins to decide whether partial fulfillment or total requirement fulfillment should be the starting posture.
Remember that setting a default does not lock users in. Whenever a project requires a different approach, the scheduler can still manually change the booking method at the time of booking. And if someone does use Full Capacity, Percentage Capacity, or Evenly Distribute Hours and inadvertently pushes a team member past 100% utilization, Microsoft directs administrators and managers back to the Schedule Board to manually review and correct the overbooking.
Section Summary: While configurable defaults streamline scheduling, administrators must weigh convenience against capacity risk: Full Capacity, Percentage Capacity, and Evenly Distribute Hours do not check remaining availability and will silently overbook resources, whereas Front Load Hours and Remaining Capacity respect existing commitments.
References
- Dynamics 365 Project Operations: Optimize Project Operations - Set a default booking method for the schedule board
- Use Configurable booking method for consistent and streamlined booking process | Microsoft Learn
- MC1472792 - Dynamics 365 Project Operations - Set a default booking method for the schedule board | Microsoft 365 Message Center Archive