Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | 
May 16, 2025 |
Mar 2026 |
Business value
When you create a project, the time zone comes from the time zone in the work hour template you apply. When you create a task, the start time, end time, and hours per day follow the working hours of the project. This time zone component can make it hard to enforce extensibility scenarios for contracts. The time zone component causes problems because it prevents the definition of time boundaries from crossing due to differences in time zones.
Feature details
In Dynamics 365 Project Operations, the start and end dates for projects and project tasks include extra fields that don't rely on specific time zones. You add these fields to both the project and project task entities. This setup supports integration and extensibility for scenarios where the time zone part of the start and end fields isn't important. It also helps improve accounting alignment.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.