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, automatically | 
May 16, 2025 |
Mar 2026 |
Business value
With this feature, you can use a field that stores start and end dates on projects and project tasks in a time zone-agnostic way. Currently, the system converts times to GMT before saving them. This conversion can cause issues when it moves a time to a different day. Using time zone-agnostic fields that the system doesn't convert to GMT when storing solves these issues.
Feature details
Project and project task start and end times are saved in a date-time format. The system converts these times to GMT before saving them. When the product displays these times, it converts them back to the user's time zone. However, some integrations and customizations pull only the date from this field. This approach causes problems when the conversion to GMT changes the date. The problem happens when an integration pulls only that date from the field without converting it back to GMT.
To prevent this problem, create new fields on the entity to store the start and end date and time values without converting them to GMT. With these fields, you can confidently pull only the date without worrying about time-zone conversion causing the date to change.
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.