Dynamics 365 Project Operations - Use time zone-agnostic fields in resource planning
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Rollout
- Ends
- 31 Oct 2026
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
- Microsoft's start date
- 1 Sep 2026
- Last changed by Microsoft
- 1 Sep 2026
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedWe are announcing the ability to use time zone-agnostic fields in resource planning in Dynamics 365 Project Operations. This feature will reach general availability on September 30, 2026. How does this affect me? Users will be able to set default start and end dates for resource requirements, resource bookings, and related tables without dates being converted based on time zone differences. This feature will also give environments flexibility to use time zone-independent date fields, helping maintain consistent dates for users working across multiple geographies. What action do I need to take? This message is for awareness, and no action is required. If you would like more information on this feature, please visit Use time zone-agnostic fields in resource planning.
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.