Microsoft has addressed this friction point in Dynamics 365 Project Operations under AI at Work roadmap ID 576857, which is now marked as Launched for General Availability on the Web in Worldwide (Standard Multi-Tenant) cloud instances. Tracked with a July 2026 general availability window—and noted by M365 Admin coverage as reaching general availability on July 24, 2026 —the update gives administrators a direct toggle to enable time-zone-independent behavior on the Time Entry Grid.
Here is a look at how the setting works, what it actually changes under the hood, and how Dynamics 365 administrators can configure it without disrupting existing workflows.
Why Time Entry Grids Shifted Dates in the First Place
In Dynamics 365 Project Operations, time entries record the actual time a resource consumes across tasks, summary levels, or top-level projects. According to Microsoft Learn documentation, those entries are the foundation for calculating project cost and sales prices as tasks progress, notifying resource managers of absences on the schedule board, and feeding the submission and approval pipeline.
By default, time entry grids in Project Operations are time zone aware. When a user creates an entry, the grid evaluates the timestamp relative to the viewer's local time zone. That default works fine when an entire organization sits in a single region. However, when a delegate or approving manager in a different time zone views another user's time entry grid, the standard Date field undergoes time zone conversion, causing calendar dates to shift unexpectedly.
How Time-Zone-Independent Behavior Works
Rather than rewriting stored time-entry records or altering how the broader application handles timestamps, Microsoft’s update gives administrators a way to change which date field the grid displays:
- Default Behavior (Time Zone Aware): The time entry grid uses the standard
Datefield, which remains the out-of-the-box setting if an administrator takes no action. - Optional Behavior (Time Zone Independent): When enabled by an administrator, the time entry grid switches to using the
Date (Time Zone Independent)field instead of the standardDatefield. - Practical Result: Every viewer—whether they are the resource submitting hours, a delegate managing a sheet, or a manager reviewing entries across oceans—sees the exact same calendar date on the time entry grid, anchored to the intended business date rather than their local clock.
- Reversibility: Microsoft Learn notes that administrators can switch the grid back to time-zone-aware behavior at any time using the exact same configuration menu.
| Configuration Aspect | Default Setting | Updated Admin Option |
|---|---|---|
| Grid Behavior | Time Zone Aware | Time Zone Independent |
| Underlying Grid Field | Standard Date field | Date (Time Zone Independent) field |
| Cross-Time-Zone View | Dates may shift for delegates or managers in other time zones | Same calendar date appears for all viewers regardless of local time zone |
| Activation Method | Enabled out of the box | Configured manually by a system administrator |
Section Summary: Switching to time-zone-independent behavior instructs the Time Entry Grid to display the Date (Time Zone Independent) field, keeping calendar dates aligned for global teams without removing the option to revert to the default time-zone-aware view.
Supported Environments and Release Scope
According to Microsoft's July 2026 release notes for Project Operations Integrated with ERP, this capability shipped alongside Dataverse environment version 4.169.3495.2 and Microsoft Dynamics 365 Finance environment version 10.0.48 (with no dual-write map changes required for the July 2026 release). Microsoft Learn's configuration guide confirms that the setting applies to both major deployment models:
- Project Operations Integrated with ERP
- Project Operations Core
From a licensing and platform standpoint, roadmap ID 576857 scopes the release to the Web platform within Worldwide (Standard Multi-Tenant) cloud environments.
Step-by-Step Guide: Enabling Time-Zone-Independent Time Entry Grids
Because time-zone-aware behavior remains the default when no preference is selected, system administrators must explicitly opt in if they want their organization's grids to use time-zone-independent dates. Microsoft Learn outlines the following procedure:
- Sign in to Dynamics 365 Project Operations with a System Administrator account.
- In the left navigation pane, switch the working area to Settings.
- Under the General group, select Parameters.
- In the list of organization units that appears, double-click (or double-tap) the Organization Units row on a column area that is not a hyperlink.
- Scroll down the page to locate the Time Entry Configuration section.
- Locate the time zone behavior setting for time entry grids and change the selection from the default time-zone-aware option to Time Zone Independent.
- Save your changes. If your organization ever needs to revert to the original behavior, return to this same section and switch the preference back.
Related Controls in the Same Configuration Panel
While administrators are inside the Time Entry Configuration section, they will notice two adjacent controls documented by Microsoft Learn that govern daily entry limits and calendar integration:
- Max Daily Duration (in minutes): Administrators can cap the total time a user can log in a single day anywhere between
0and1,440minutes. While Microsoft's July 2026 release notes parenthetically referred to an out-of-the-box figure of 4 hours, Microsoft Learn's dedicated configuration documentation explicitly states that 24 hours (1,440 minutes) remains the default whenever an administrator does not set a preferred maximum. If a new or modified time entry exceeds the configured limit, Project Operations blocks the change and returns an validation error. - Use Outlook meetings as a time entry source: On environments where the preview Time Entry Calendar feature is enabled, administrators can flip this toggle from OFF (the default) to ON so team members can view Outlook meetings on the calendar interface and convert them into time entries.
Broader Context and What Admins Should Keep in Mind
This update is part of a wider effort by Microsoft to clean up cross-time-zone discrepancies across Dynamics 365 Project Operations. For instance, as tracked in Microsoft Message Center post MC1465316, Microsoft also moved to introduce time-zone-agnostic fields in resource planning (covering default start and end dates for resource requirements and bookings) on September 30, 2026.
Still, administrators should keep expectations grounded in what the Time Entry Grid toggle actually does. Based on general industry knowledge and Microsoft's documentation, this setting strictly governs how the time entry grid renders dates by swapping in the Date (Time Zone Independent) field. It is not a magic wand that rewrites custom reports, alters historical accounting ledgers, or bypasses human error during timesheet approval. Organizations with custom integrations or bespoke Power BI reports pulling directly from Dataverse tables should verify whether their queries reference the standard Date column or the Date (Time Zone Independent) column before flipping the switch in production.
Section Summary: Administrators can enable time-zone-independent grid dates in seconds via the Organization Units Parameters page, alongside daily duration limits, though teams using custom reporting should verify which Dataverse date fields their downstream tools query.