To solve this, Microsoft is rolling out time-zone-agnostic date fields for project planning in Dynamics 365 Project Operations, tracked under Microsoft 365 and AI at Work Roadmap ID 576766. While the concept sounds like a minor database tweak, the architectural details published in Microsoft Learn reveal critical distinctions in how these fields behave, how they populate on legacy records, and why developers must not confuse them with the underlying scheduling engine's core fields.
The GMT Conversion Trap in Project Planning
To understand why Microsoft is adding dedicated columns to the Project and Project Task tables, it helps to look at how Dynamics 365 traditionally handles time. By default, project and project task start and end times are stored in a standard date-time format. When a project manager enters a date and time, the system converts that value to GMT (or UTC) before committing it to the database. When someone views that record in the Dynamics 365 web interface, the platform reads the user's personalization settings and converts the UTC timestamp into that individual's local time zone.
In a localized team, that behavior is invisible. Across global operations—or worse, inside automated data pipelines—it causes chaos:
- Viewer-Specific Discrepancies: Because legacy date-time fields convert UTC values into each viewer's personal time zone, two users in different regions can look at the exact same project record and see different start or finish dates.
- Integration Date Shifts: Many downstream integrations, reporting extracts, and custom plugins only care about the calendar date, not the specific hour. When an integration pulls only the date portion directly from a GMT-converted database field without translating it back from GMT, the UTC offset can shift the date backward or forward by a full calendar day.
By introducing time-zone-agnostic fields on the Project and Project Task entities, Dynamics 365 Project Operations gives administrators, report authors, and integration developers a stable date reference that does not shift based on who is viewing the screen or where an API call originates.
Section Summary: Legacy start and end fields in Project Operations convert timestamps to GMT/UTC for storage and translate them into each viewer's personal time zone, frequently causing off-by-one-day errors in date-only integrations and cross-regional reports.
Under the Hood: The Four New Schema Fields and How They Work
According to Microsoft Learn documentation for Dynamics 365 Project Operations (which applies to both Project Operations Integrated with ERP and Project Operations Core), the update introduces four specific fields across the Project and Project Task entities.
| Entity | Display Name | Schema Name | Field Behavior | Description |
|---|---|---|---|---|
| Project | Start Date Time Zone Agnostic | msdyn_tzascheduledstart | Editable | Start date of the project (Time Zone Agnostic) |
| Project | Finish Date Time Zone Agnostic | msdyn_tzafinish | Editable | Finish date of the project (Time Zone Agnostic) |
| Project Task | Start Date Time Zone Agnostic | msdyn_tzascheduledstart | Read-only | Scheduled start time of the project task (Time Zone Agnostic) |
| Project Task | Due Date Time Zone Agnostic | msdyn_tzascheduledend | Read-only | Scheduled end time of the project task (Time Zone Agnostic) |
Notice that msdyn_tzascheduledstart is used as the schema name on both the Project and Project Task entities, so developers writing queries or mappings need to keep the target entity context straight.
More importantly, the two tables do not behave the same way when it comes to data entry:
- Bidirectional Editing on the Project Entity: On the main
Projectrecord, the new time-zone-agnostic fields (msdyn_tzascheduledstartandmsdyn_tzafinish) are fully editable. If a user updates the traditional time-zone-dependent date, the system automatically calculates and updates the corresponding time-zone-agnostic date—and vice versa. - Read-Only Calculation on the Project Task Entity: On
Project Taskrecords, the new fields (msdyn_tzascheduledstartandmsdyn_tzascheduledend) are strictly read-only. Users and write-integrations cannot edit them directly; instead, you must update the existing time-zone-dependent task dates, and the system automatically computes the agnostic equivalents.
How the Project Calendar Drives the Math
How does Dynamics 365 calculate a "time-zone-agnostic" date if the underlying project is still scheduled in date-time values? According to Microsoft Learn, the system uses the project calendar's time zone as its single reference point, along with the working hours configured in that project calendar. Because the system displays these dates based on the project calendar's time zone rather than each user's personalization settings, every user across the organization sees the exact same date.
Microsoft explicitly warns administrators to verify that their project calendars have accurate working hours configured, as the automatic conversion relies on those working hours to calculate accurate results.
Section Summary: Microsoft adds two editable agnostic fields to the Project entity and two read-only agnostic fields to the Project Task entity, using the project calendar's time zone and working hours as a single shared reference point.
Two Crucial Gotchas for Admins and Developers
Before you instruct your development team to rip out every legacy date reference and replace them with msdyn_tzascheduledstart, Microsoft's documentation highlights two major operational boundaries that could easily trip up an unprepared deployment.
1. Do Not Use Agnostic Fields for the Scheduling Engine
Microsoft Learn states clearly that organizations should use time-zone-agnostic dates for reporting and display purposes only. The Project Operations scheduling engine continues to rely on the legacy, time-zone-dependent date fields for all scheduling calculations and operations.
If you have an upstream integration that feeds task schedules into Project Operations, or custom logic that manipulates task dependencies, it must still interact with the time-zone-dependent fields. Think of the new fields as a stabilized presentation and extraction layer for downstream consumers (such as ERP billing extracts, data warehouses, or executive dashboards) rather than a replacement for how the scheduling engine computes time.
2. Watch Out for "Lazy Loading" on Existing Projects
What happens to the hundreds or thousands of active projects already sitting in your Dataverse environment when this feature lands? They do not get populated overnight via an automatic background job.
According to Microsoft Learn, for existing projects, the system uses lazy loading to calculate time-zone-agnostic dates. Specifically, the fields remain empty (null) in the database until a user opens the project's main form for the first time. Opening the main form triggers the calculation and writes the values to the database.
For BI architects and integration engineers, this is a vital detail. If you switch a production report or an integration query over to msdyn_tzascheduledstart and msdyn_tzafinish on day one, any historical or in-flight project whose main form has not been manually opened since the feature's activation will return blank values. Teams planning to adopt these columns for organization-wide reporting will need to account for null values on older records or ensure active projects have their main forms opened before cutting over downstream reports.
Section Summary: The scheduling engine still requires legacy time-zone-dependent fields for all schedule calculations, and existing project records leave the new agnostic fields blank in the database until the project main form is opened for the first time.
Timeline, Availability, and Roadmap Context
This project planning update is part of a broader push by Microsoft to eliminate cross-time-zone friction across the entire Dynamics 365 Project Operations suite. For example, as tracked in Microsoft Message Center post MC1465316 and Microsoft's release plan documentation, Microsoft also introduced a companion capability—time-zone-agnostic fields in resource planning (covering resource requirements and resource bookings)—which reached general availability on September 30, 2026.
For the project planning capability specifically (Roadmap ID 576766), Microsoft's published timelines show the feature nearing the finish line:
- Preview and Rollout Target: Both the Microsoft 365 Roadmap entry (ID 576766) and the Dynamics 365 2025 release wave 1 plan list Public Preview as beginning in May 2025 (specifically May 16, 2025 on the release plan) and General Availability scheduled for December 2026 for Worldwide (Standard Multi-Tenant) web environments.
- Documentation Status: Even though the roadmap tracks General Availability for December 2026 with a status of "In development," Microsoft Learn's core product documentation for
msdyn_tzascheduledstart,msdyn_tzafinish, andmsdyn_tzascheduledendhas been live since at least March 10, 2026. - Admin Action Required: When active in an environment, the feature is enabled for end users automatically. However, because the fields areAlready documented for preview/early environments while General Availability targets December 2026, administrators should check their specific Project Operations environment schema to verify whether the columns are already present in their tenant.
Practical Checklist for Project Operations Teams
If your organization struggles with shifting dates in Dynamics 365 Project Operations, here is how to prepare for and adopt the new fields safely:
- Audit Your Project Calendars First: Because automatic calculation of time-zone-agnostic dates depends on the project calendar's time zone and working hours, verify that your templates and active project calendars have accurate working hours configured.
- Separate Reporting Consumers from Scheduling Writers: Map out your custom plugins, Power Automate flows, Dual-write or ERP integrations, and Power BI reports. Transition read-only, date-only consumers (like financial reporting and milestone dashboards) to the new
msdyn_tza*fields, while keeping schedule-modifying integrations pointed at the legacy time-zone-dependent fields. - Handle Nulls on Legacy Records: Before flipping the switch on any SQL, FetchXML, or OData query to use the new columns, remember the lazy-loading rule. Either build fallback logic (using the agnostic date if present, and falling back to a properly converted legacy date if null) or have project managers open the main form on active projects to force calculation.
By anchoring project and task display dates to the project calendar rather than the viewer's personal clock or raw GMT storage, Microsoft is finally taking one of the most annoying date-math headaches out of Dynamics 365 Project Operations—provided administrators respect the boundary between reporting display and the core scheduling engine.