A global team coordinates a shared March 20 project milestone across time zones, with linked billing documents.
Microsoft has added a roadmap entry, ID 580479, for a Dynamics 365 Project Operations feature that keeps billing milestone dates the same for every user, whatever their local time zone. The record is marked In development, covers the Web platform and Worldwide (Standard Multi-Tenant) cloud, and targets General Availability in February 2027. Microsoft's roadmap page warns that all dates and descriptions are estimates and subject to change. Treat February 2027 as a forecast, not a promise.

A global team coordinates a shared March 20 project milestone across time zones, with linked billing documents. What the roadmap item says​

The description is short. The feature keeps project billing milestone dates consistent no matter where the signed-in user is. The date applies to quote and contract records. The stated goals are to let globally distributed teams work from the same billing date and to cut date discrepancies when milestone information is exchanged with finance systems.

The roadmap page itself didn't show the item's metadata in the text captured for this story. The status, ring, cloud scope and target date above come from the submitted roadmap record, not from the visible page text.

Why a date can drift​

Dates are awkward in business software. Storing "March 1" as a moment in time means a user in Sydney and a user in Los Angeles can each see a different calendar day.

Microsoft's documentation describes this exact problem in Project Operations. The milestone date field in the project contract line milestone entity uses user local time, but the same field in the invoice entity is time zone independent. That mismatch creates a discrepancy when you view the milestone date from the invoice schedule in the project contract line in the UI. The fix makes the milestone date consistent in both entities, so invoicing milestones are more accurate.

Microsoft says the benefit is mainly for fixed-price contract lines. Keeping the milestone date consistent between the contract line and the invoice entity reduces corrections downstream. Microsoft also says it lowers the administrative burden and leads to faster cash flow. Those are expected business benefits as Microsoft frames them. The documentation gives no measured results.

This capability is already documented​

The roadmap entry reads like a new feature, but Microsoft already documents a "Time Zone Independent Milestone Date" capability. Some background on how the two relate:

  • Microsoft's 2025 release wave 1 plan lists "Enable milestone date to be time zone independent" with general availability on May 2, 2025.
  • The Learn page on time zone independent date fields says it applies to Project Operations Core and Project Operations Integrated with ERP.
  • Neither the roadmap record nor the documentation explains how item 580479 relates to the 2025 entry. It could be a rollout phase, an extension or a re-listing. Don't assume the February 2027 date means a first-time release.
  • Microsoft's archived release-plan page says that as of October 2026 the content is archived and no longer maintained, and it sends readers to the roadmap for current plans. That fits the new entry appearing on the AI at Work roadmap.

How the documented feature works​

If you run Project Operations today, Microsoft's Learn page gives these steps and behaviors.

  1. Go to Settings > Parameters > Feature control > Enable TZ Independent Milestone Date.
  2. Update your Dual-write map version to 1.0.0.7 to use the milestone date (TZ independent) field in your finance and operations apps environment.

After you enable it:

  • All out-of-the-box forms and views that use the Milestone date are updated to use the TZ Independent Milestone date. The quote line and contract line entities are updated too.
  • Microsoft says both msdyn_invoicedate and msdyn_milestonedate are set regardless of the feature flag state.
  • The new Dual-write map version can sync the TZ independent milestone date to finance and operations apps.
  • On upgrade, the TZ independent value on existing milestones in quote line and contract line entities updates when a user triggers an action on a related form or view.

That last point matters. Existing milestones aren't necessarily converted in one batch. They update as users touch the related forms or views.

Practical advice for admins and finance teams​

This is my analysis, not Microsoft guidance.

  • Check your Dual-write map version if you integrate with Finance and Operations apps. Version 1.0.0.7 is the documented requirement for the TZ-independent milestone field.
  • Test in a sandbox with users in at least two distant time zones. Compare the milestone date on the quote line, the contract line, the invoice schedule and the finance-side record.
  • Audit customizations. Microsoft says out-of-the-box forms and views are updated. It doesn't say custom forms, reports, flows or third-party integrations will adopt the new field automatically. Check anything that reads msdyn_milestonedate directly.
  • Don't expect changes to money. Nothing in Microsoft's description suggests invoice amounts, contract terms or billing policy change. This is about date consistency.
  • Plan for slippage. Microsoft's roadmap disclaimer applies. Don't schedule a finance-system change around February 2027 alone.

Part of a wider time-zone cleanup​

Microsoft has been fixing the same class of problem across Project Operations. Other time-zone-agnostic work includes:

  • Project and project task dates. Project and Project Task entities now support time zone agnostic dates. The system calculates them using the project calendar's time zone as the reference.
  • Accounting date in invoicing. A Message Center post says Dataverse includes a new time-zone agnostic accounting date field to use when posting transactions in finance and operations.
  • Time entry grid. Message Center item MC1425995 says admins can enable behavior so time entries appear against the same calendar date regardless of a user's time zone.

Together these suggest Microsoft is treating "calendar dates" and "moments in time" as separate concepts across the product. That's good news for global billing teams. It's less good for anyone with custom code that assumed everything was a UTC timestamp.

Bottom line​

Roadmap item 580479 is a forward-looking, In-development entry targeting February 2027. It continues a documented line of Project Operations work to stop billing milestone dates shifting by user time zone. The fixes to check today are the feature control setting and Dual-write map 1.0.0.7. Microsoft hasn't said how the roadmap item differs from the capability already documented, so treat the date as a forecast and test your own environment before relying on it.

 

References

  1. Dynamics 365 Project Operations: Optimize Project Operations: TZ Independent Milestone Date Microsoft 365 Roadmap 2026-11-17T18:36:41.967573Z
  2. Enable milestone date to be time zone independent learn.microsoft.com
  3. Use time zone independent date fields learn.microsoft.com