Dynamics 365 Procurement Agent to Add Joined-Table Supplier Follow-Up Filters in December 2026

Microsoft says roadmap dates are estimates and subject to change. December 2026 is therefore a forecast. It doesn't mean the feature has shipped.

What the roadmap item says​

The listing describes buyers extending follow-up criteria with data from related standard, extended and custom tables. They could add table joins and use fields from those tables as filter conditions. Which purchase order lines qualify for follow-up would then depend on the organization's own processes and data.

The listing doesn't name any tables, field types, join types, join limits, operators or permissions. It also gives no preview date, minimum version or licensing detail. Any of those would be speculation until Microsoft publishes documentation.

Why it matters: how follow-up criteria work today​

Microsoft Learn documents the current supplier follow-up workflow, which is labeled a production-ready preview. The Procurement Agent can generate emails that remind vendors to confirm a purchase order or ask why a delivery is late. It can send those emails right away, or save them as drafts for human review before sending. Automatic sending is optional and off by default.

The agent ships with two default tasks, per Microsoft Learn:

• Unconfirmed purchase orders. This task finds orders assigned to you with a delivery date in the next 60 days and a blank confirmed delivery date. Its criteria include a nonzero deliver remainder, a blank confirmed receipt date, a requested receipt date before today, the current user as orderer, and a header document status other than None.
• Delayed purchase orders. This task finds orders assigned to you whose confirmed receipt date is before the current date. It also requires a nonzero deliver remainder and the current user as orderer.

Users can edit or delete these defaults and build their own tasks. The documented examples are fairly simple. They include orders created in the last three days, orders for a particular vendor group, and date-range splits for repeat follow-ups.

Those examples show where the gap is. Real procurement rules often depend on something not on the purchase order or standard vendor fields. A custom supplier attribute or a related organizational record are illustrative cases. The roadmap description suggests the joins feature is meant to close this gap. Today, a buyer with such a rule can only approximate it with broader filters.

The two-task pattern still applies​

Agent tasks generate just one email per purchase order unless the purchase order changes. To keep following up when a vendor doesn't reply, Microsoft recommends two tasks with the same core criteria but non-overlapping date ranges. The documented example is a "recent overdue" task covering seven days ago to today. A second "extended overdue" task covers anything earlier than eight days ago.

Nothing in the roadmap item says this behavior changes. Richer criteria could make careful range design matter more. Overlapping ranges can cause the same order to be evaluated by multiple tasks at once, and adding joined conditions would make accidental overlap easier to miss. That is my own inference. It is not something Microsoft has stated.

What the roadmap item does not cover​

This is a change to qualification criteria only. The evidence doesn't say it changes any of the following:

• how the agent writes email content
• how vendor recipients are chosen
• how vendor replies are processed
• whether purchase orders are modified
• whether emails are sent automatically

Learn describes those areas separately. Recipient selection, for example, follows a priority purchase-order communications address on the vendor. If none is set, it uses the primary email or the purchase order's email field, depending on the task grouping.

What administrators can do now​

1. Audit current rules. List the follow-up rules your buyers apply by hand that the current criteria can't express. Those are the candidates for joined-table filters.
2. Check your data. Joined criteria will only help if the custom or extended fields exist and are kept up to date. Clean vendor and purchase order data now.
3. Stay in review mode. Keep automatic sending off and review drafts until you've seen how new criteria behave. Microsoft documents that the email footer is mandatory if automatic sending is enabled.
4. Wait for documentation. Plan around the December 2026 estimate, but wait for the release notes and Learn pages before committing configuration work.

Bottom line​

This is a modest but practical improvement for organizations with business-specific follow-up logic. It is also unshipped and thinly described. The listing confirms joins and filter conditions on related standard, extended and custom tables. It leaves the limits and mechanics undefined. Treat it as a roadmap signal until Microsoft documents the feature.