Targeted for General Availability in November 2026 for Worldwide (Standard Multi-Tenant) cloud instances on the Web platform, the upcoming capability will allow organizations to configure an allowable duration increment for time entries. Once enabled by administrators, makers, or marketers for end users, Dynamics 365 Project Operations will only allow users to create or modify time entries whose duration is a clean multiple of that configured value—such as 15 minutes or 1 hour. Because the feature is currently listed as "In development," Microsoft notes on its AI at Work Roadmap that all release timelines and descriptions remain estimates and are subject to change before rollout.
Why Time Entry Granularity Matters in Project Operations
In Dynamics 365 Project Operations, a time entry is far more than a digital punch card. As documented on Microsoft Learn, time entries record the actual time a resource consumes across project, summary, or task levels, and they directly feed the calculations for project cost and sales prices as work progresses. When project contracts define discrete components of work—whether billed on a time-and-materials basis or tracked against fixed-price milestones—dirty input data at the time-entry layer cascades into project tracking, client invoicing, and resource scheduling.
Historically, organizations had limited out-of-the-box options for governing the shape of a time entry duration without resorting to custom validation plugins or client-side scripts. As noted by Power Platform & Dynamics CRM Tip Of The Day, when a user creates a new time entry in Project Operations, the system's standard default duration value is set to 1 hour. While modifying a default value helps guide initial input, it does not stop a user from manually typing an odd duration—say, 22 minutes—when creating or editing a record.
With Roadmap ID 576858, Microsoft is moving from passive defaults to active increment validation. By requiring every newly created or modified time entry to be a multiple of a chosen interval, enterprises can enforce internal time-tracking policies and client billing rules right at the point of entry.
Key Summary: Roadmap ID 576858 at a Glance
| Attribute | Official Roadmap Detail |
|---|---|
| Feature Title | Dynamics 365 Project Operations: Optimize Project Operations - Configure minimum interval of time entry duration |
| Roadmap ID | 576858 |
| Product & Platform | Dynamics 365 Project Operations (Web) |
| Current Status | In development |
| Target Release Ring & Date | General Availability — November 2026 (Estimated) |
| Cloud Instance | Worldwide (Standard Multi-Tenant) |
| Enablement Model | Enabled by admins, makers, or marketers for end users |
| Core Behavior | Restricts creation and modification of time entries to durations that are multiples of the configured interval (for example, 15 minutes or 1 hour) |
How the New Interval Rule Fits Alongside Existing Controls
To understand why this update is a welcome addition for Dynamics 365 administrators, it helps to look at the validation tools Microsoft already provides. According to Microsoft Learn’s documentation on Time Entry Configurations (which applies to both Project Operations Integrated with ERP and Project Operations Core), system administrators currently have access to a Max Daily Duration (in minutes) setting.
That existing control addresses a different half of the timekeeping problem:
- Daily Cap vs. Entry Increment: By default, Project Operations caps the total time entries for a single day at 24 hours (1,440 minutes), and administrators can adjust that ceiling anywhere between 0 and 1,440 minutes to prevent users from logging unrealistic daily totals. Whenever a user creates a time entry or modifies an existing entry's duration, Project Operations checks the daily total and returns an error if it exceeds the configured maximum.
- Time Zone Consistency: In the same configuration area, administrators can switch time entry grids from their default time-zone-aware behavior to Time Zone Independent, ensuring delegates and managers in other regions see consistent dates without unexpected shifts.
- Calendar Sourcing: Environments with the Time Entry Calendar feature enabled can also toggle on Outlook meetings as a time entry source.
Where the existing Max Daily Duration control prevents someone from accidentally logging 30 hours on a Tuesday, the forthcoming minimum interval setting under Roadmap ID 576858 governs the granularity of entries as they are created or modified. Used together, an organization could both cap total daily hours at a sensible ceiling and ensure that every time entry adheres to a standard 15-minute, 30-minute, or 60-minute block.
Where Current Time Entry Settings Live
For administrators who want to review their current validation posture ahead of the November 2026 target window, Microsoft Learn outlines the following navigation path for existing time entry parameters:
- Sign in to Dynamics 365 Project Operations as a system administrator.
- In the left navigation pane, switch the area to Settings.
- Under the General section, select Parameters.
- In the list of organization units, double-click (or double-tap) the Organization Units row on a column that is not a hyperlink.
- Scroll down to the Time Entry Configuration section.
Important caveat: While Microsoft Learn documents this exact path for maximum daily duration and grid time-zone behavior, Microsoft has not yet published the exact screen location, field label, or step-by-step setup documentation for the upcoming minimum interval setting. Administrators should treat the existing Time Entry Configuration section as helpful background context rather than confirmed setup instructions for Roadmap ID 576858.
What the Rule Does—and What Remains Unspecified
When evaluating a roadmap item for enterprise deployment, knowing what the documentation doesn't say is just as important as knowing what it does. Based on the verified roadmap record and current Microsoft Learn documentation, administrators and solution architects should keep several boundaries in mind:
- Multiples, Not Just Minimums: Despite the phrase "minimum interval" in the title, the roadmap description specifies that durations must be a multiple of the configured value. For example, if an organization configures a 15-minute interval, valid entries must align with 15-minute steps (15, 30, 45, 60 minutes, and so on) whenever a user creates or modifies a time entry.
- Approval and Billing Logic: The roadmap item describes input validation during the creation and modification of time entries. It does not state that the feature automatically rounds irregular inputs, alters approval workflows, or retroactively modifies historical entries already stored in the system.
- Scope and Surface Area: The roadmap lists Web as the target platform and states that the feature is enabled by admins, makers, or marketers for end users. However, the brief does not yet specify whether the increment is configured globally across the environment, per organization unit, or per project, nor does it detail how validation behaves when time entries are generated via API integrations, data imports, or Outlook calendar imports.
Practical Next Steps for Dynamics 365 Administrators
If your organization currently relies on custom JavaScript web resources, Power Automate checks, or Dataverse plug-ins just to stop users from entering fractional oddities on their timesheets, Roadmap ID 576858 is worth putting on your radar for late 2026. Between now and the targeted November 2026 General Availability window, IT and PMO leads can prepare by auditing their current time-tracking policies:
- Standardize Your Policy Increment: Confirm with finance, HR, and legal teams whether your organization's standard billing and payroll rules require 15-minute, 30-minute, or 1-hour increments across all business units, or if requirements vary by contract type.
- Inventory Custom Validations: Check whether your Dynamics 365 environment currently runs custom scripts or plug-ins on the Time Entry table to enforce duration increments, so you can test and retire redundant custom code once Microsoft’s native validation becomes generally available.
- Watch for Official Learn Documentation: Monitor the Dynamics 365 Project Operations release notes and Microsoft Learn documentation as November 2026 approaches for the exact parameter name, supported interval range, and error-handling behavior.
By bringing native duration-increment validation into Dynamics 365 Project Operations, Microsoft is tackling one of the oldest paper cuts in enterprise timekeeping—helping project managers spend less time policing stray minutes and more time delivering actual projects.