What Microsoft says is coming
The roadmap listing says the feature extends delivery address handling in integrated Project Operations deployments. The planned scope is:
- Delivery address support on three record types: Project, Project Task, and Material Estimate.
- Customer addresses as the source: users can pick a delivery address from the customer's existing addresses.
- Defaults through the project hierarchy: an address set higher up can flow down to the records beneath it.
- Synchronization between Dataverse and Finance and Operations: the address is meant to stay consistent across both sides of an integrated deployment.
- Item Requirements always get an address: the address should be resolved and populated however the requirement is created. The listing names three origins: Item Forecasts, Project Purchase Orders, or directly from Projects.
Microsoft's stated goal is a consistent, controlled address experience across project planning, procurement, and fulfillment.
Timeline and status
| Item | Roadmap value |
|---|---|
| Roadmap ID | 577400 |
| Status | In development |
| Products | Dynamics 365 Finance, Dynamics 365 Project Operations, Finance and Operations cross-app |
| Platform | Web |
| Cloud | Worldwide (Standard Multi-Tenant) |
| Preview | January 2027 |
| General availability | January 2028 |
These dates are estimates. The Microsoft roadmap page says all information is subject to change, and features can be postponed or cancelled. The listing was published on 13 November 2026, and no modification date is recorded.
I could not confirm the live roadmap card's current details independently. Treat the description above as what the submitted listing says, not as a released or documented feature.
Why the delivery address matters in this workflow
Microsoft Learn describes item requirements as the materials or products a project needs. They can be procured, reserved, or issued from stock. Item requirements are linked to a project, and their transactions are tracked for project costing and revenue recognition.
Two documented flows already produce item requirements, and both are named in the roadmap item.
Purchase-order flow. Per Microsoft Learn, when a purchase order is created using the Item requirements feature, Finance generates the project item requirements, and each purchase order line is directly related to its requirement. A purchase order can also start from an item requirement, in the other direction.
Forecast flow. In integrated Project Operations deployments, item forecasts come from project material estimates in Dataverse. Item forecasts are generated by using the project material estimates in Dynamics 365 Project operations Dataverse. Users then create item requirements from those forecasts in Finance.
The roadmap item touches Material Estimates, Item Forecasts, Project Purchase Orders, and Item Requirements. In other words, it covers the whole chain from estimate to purchase order to delivery.
The problem it appears to address
Today, delivery addresses in project procurement can take manual effort. A Dynamics 365 Community blog post on item-requirement limitations describes a workaround. The user manually updates the purchase order, choosing the customer's address from the global address book and propagating it to the lines. That post is old, so it may not reflect current behavior. Still, it shows the kind of friction a defaulting and sync feature could remove.
Microsoft has not said this is the motivation. Reading the roadmap description against community experience, though, the intent looks like fewer manual address edits and fewer mismatches between systems.
What we don't know yet
The roadmap text leaves several practical questions open:
- Precedence rules: if a Project, a Task, and a Material Estimate each carry a different address, which one wins?
- Field names and mappings: nothing specifies how the address maps between Dataverse and Finance and Operations.
- Dual-write or integration changes: it is unclear whether existing integrations need updating.
- Prerequisites and minimum versions: none are listed for this feature.
- Effect on existing records: the listing doesn't say whether addresses will be back-filled on existing projects and requirements.
Don't assume any of these. In particular, the roadmap does not say the change alters costing, accounting, tax, or shipping behavior.
Existing prerequisites, for context only
The currently documented stocked-product forecast workflow has its own requirements. Learn lists these minimums for it:
- Project Operations Dataverse: version 4.161.0.x or later.
- Dynamics 365 Finance: version 10.0.46 or later.
- Dual-write map: "Project material usage creates (msdyn_materialusagelogs)", version 1.0.0.0.
These are prerequisites for that existing workflow, not confirmed requirements for roadmap item 577400. They do show that the project-to-Finance handoff already depends on specific versions and maps. A new address feature will likely sit on that same integration layer. That is analyst inference, not a Microsoft statement.
Practical advice for admins and project teams
- Audit your current process. Note where delivery addresses are entered today: project, purchase order, or both. Record how often they differ from the customer's address book.
- Check customer address data quality. The feature is described as selecting from customer addresses, so incomplete or duplicated customer address records will limit its value.
- Review integration customizations. If you extended Dataverse-to-Finance mappings or item-requirement creation, flag them for retesting when preview arrives.
- Plan for preview in a sandbox. January 2027 is the estimated preview, so line up a non-production environment now.
- Track the roadmap entry. Microsoft says features can be found by ID, and cards can be followed through the roadmap site or RSS. Watch for changes to dates or descriptions.
Bottom line
This is a modest but useful plumbing improvement for project-based businesses that buy materials for customer sites. It targets address defaulting and consistency across Dataverse and Finance, and it could mean fewer manual address fixes on project purchase orders. But preview is about two months away at best, general availability is estimated at January 2028, and Microsoft hasn't yet published setup details, precedence rules, or prerequisites. Until it does, plan for it, but don't build processes around it.