Now, system administrators can tighten that guardrail without writing custom plugins or Dataverse workflows. Under Microsoft 365 Roadmap ID 576859 (and tracked in Microsoft 365 Message Center notice MC1425968), Microsoft has rolled out a native configuration allowing administrators to set a custom maximum daily time entry duration in Dynamics 365 Project Operations.
What Changed: From 24 Hours to Policy-Aligned Caps
Out of the box, Dynamics 365 Project Operations enforces a ceiling of 24 hours—or 1,440 minutes—of combined time entries for a single day. According to Microsoft’s release plan and product documentation, that daily aggregate includes vacation hours alongside regular logged time. If an administrator leaves the new setting untouched, that 24-hour (1,440-minute) default remains in effect.
With the new Max Daily Duration (in minutes) parameter, administrators can configure any value between 0 and 1,440 minutes. If an organization wants a hard ceiling of 9 hours per day, the administrator enters 540.
Whenever a user creates a new time entry or modifies the duration of an existing entry, Project Operations evaluates the day's total logged duration against this parameter. If the new or edited entry pushes the day's total past the configured limit, the system blocks the change and returns an validation error.
| Configuration Attribute | Verified Detail |
|---|---|
| Product Scope | Dynamics 365 Project Operations (Integrated with ERP and Project Operations Core) |
| Roadmap & Notice IDs | Roadmap ID 576859 / Message Center MC1425968 |
| Availability | General Availability (July 24, 2026 in release plan and MC1425968; August 2026 on Roadmap) |
| Cloud Instance & Platform | Worldwide (Standard Multi-Tenant), Web |
| Default Daily Maximum | 24 hours (1,440 minutes) |
| Configurable Range | 0 to 1,440 minutes |
| Included Time | Total daily time entries, explicitly including vacation hours |
| Validation Trigger | Creation of a new time entry or modification of an existing entry's duration |
A Quick Note on Documentation Discrepancies
If you happen to read Microsoft Learn's What's new July 2026 - Project Operations Integrated with ERP summary table (covering Dataverse version 4.169.3495.2 and Finance version 10.0.48), you might spot a line claiming that the daily maximum is "currently set to 4 hours out of the box." Treat that as a documentation typo. Both the dedicated Time entry configurations in Project Operations guide on Microsoft Learn and the official 2026 release wave 1 plan explicitly confirm that 24 hours (1,440 minutes) is the out-of-the-box default and stays the default unless an administrator changes it.
How to Configure the Maximum Daily Time Entry Duration
Microsoft Learn’s configuration documentation outlines a straightforward setup path that applies to both Project Operations Integrated with ERP and Project Operations Core:
- Sign in to Dynamics 365 Project Operations using an account with System Administrator privileges.
- In the left navigation pane, switch the area selector to Settings.
- Under the General group, select Parameters.
- In the list of organization units, double-click (or double-tap) the Organization Units row—make sure to click a column area that is not a hyperlink so you open the parameter record rather than navigating away.
- Scroll down to the Time Entry Configuration section.
- Locate Max Daily Duration (in minutes) and enter your preferred value between 0 and 1,440 (for example,
540for a 9-hour daily cap, or600for a 10-hour cap). - Save the record.
While you are in the Time Entry Configuration section of the Parameters page, you may also notice two neighboring settings documented by Microsoft Learn: a toggle to switch time entry grids from their default time-zone-aware behavior to Time Zone Independent (which prevents dates from shifting when managers or delegates in other time zones review a grid), and a toggle to Use Outlook meetings as a time entry source on environments where the Time Entry Calendar is enabled. Those sit in the same administrative panel, though they operate independently of the daily duration limit.
Practical Considerations Before You Flip the Switch
Before an administrator clamps the daily limit down to 8 or 9 hours, it pays to think through how real employees log their time—and what this parameter does and does not do:
- It is an environment-level parameter, not a per-user rule: Microsoft’s documentation places this setting inside the global Parameters record. It does not provide granular overrides by individual user, security role, project, or billing type. If you set the ceiling to 540 minutes (9 hours), it applies across the board.
- Watch out for legitimate overtime and split days: Because the rule checks the total duration logged for a single day—including vacation hours—setting the cap too tightly to a standard 8-hour (480-minute) workday will block anyone who legitimately works an extra hour of billable overtime, or someone who logs 4 hours of vacation and 5 hours of project work on the same day. Picking a slightly wider buffer (such as 10 or 12 hours) catches accidental "80-hour Tuesday" typos without generating helpdesk tickets every time a deployment runs late.
- Validation happens on create and edit: Project Operations checks the limit when a user creates a new entry or modifies an existing entry's duration. Lowering the cap will immediately govern new entries and duration edits going forward.
For organizations running Dynamics 365 Project Operations, this update removes the need to maintain custom validation rules just to stop impossible daily timesheet totals. A quick stop in the Parameters menu is now all it takes to keep daily time reporting within sensible boundaries.