Dynamics 365 Procurement Agent Gets Custom Supplier Email Scenarios in December 2026

According to Microsoft's AI at Work roadmap under item ID 573705, the company is developing a new capability titled Dynamics 365 Supply Chain Management: Procurement Agent - Define custom scenarios for agent-generated supplier emails. Currently marked as "In development," this Web-based feature is slated for General Availability in December 2026 for Worldwide (Standard Multi-Tenant) cloud instances. As with all Microsoft roadmap entries, the timeline and scope remain estimates subject to change before release.

For enterprise IT administrators, ERP architects, and purchasing teams, this update signals an important shift: moving the Procurement Agent from rigid, pre-packaged templates toward user-defined outbound workflows.

Moving Beyond Built-In Follow-Up Templates​

To understand why custom scenarios matter, it helps to look at how the Procurement Agent currently operates. In Microsoft Learn's documentation for the production-ready preview of Procurement Agent supplier communications, outbound follow-ups are built around two default tasks:

1. Unconfirmed purchase orders: Identifying orders assigned to the user with a delivery date within the next 60 days where the confirmed receipt date is blank, the deliver remainder is non-zero, and the document status is not "None".
2. Delayed purchase orders: Finding orders assigned to the user where the confirmed receipt date is at least one day in the past and a delivery remainder still exists.

While buyers can already tweak filter criteria—such as narrowing a task down to a specific vendor group or adjusting date ranges—the core intent of the outbound agent is locked into those two built-in scenarios.

Roadmap item 573705 plans to break out of that binary box by letting business end-users and buyers define and maintain their own outbound follow-up scenarios and deploy them wherever built-in scenarios are used today. According to Microsoft's roadmap description, the update rests on four pillars:

• Scenario maintenance: A dedicated setup page where users can create, edit, and maintain custom follow-up scenarios. Each scenario carries its own name, specific instructions that shape the email the agent drafts, and the business entity to which it applies.
• Scenario-driven configuration: Follow-up configurations are constructed around the chosen scenario so that filter criteria, email content, and agent behavior align with the user's selected scenario.
• Scenario-driven runtime: When the agent executes, it generates and sends messages based on the intent and instructions of the selected scenario.
• Self-describing configuration history: Scenario details are captured alongside each saved configuration. This ensures the audit history of an agent configuration stays readable even if the underlying scenario definition is later modified or deleted.

Section Summary: While the existing Procurement Agent limits outbound email generation to unconfirmed or delayed purchase orders, roadmap ID 573705 introduces a dedicated setup page for custom scenarios, pairing user-defined email instructions and target business entities with preserved configuration history.

Why "Self-Describing History" and Custom Instructions Matter​

If you have ever audited an automated workflow six months after a business analyst quietly changed a prompt or a rule, you know the headache of trying to figure out why an AI agent said what it said back in Q2. Microsoft's inclusion of "self-describing configuration history" directly targets this operational blind spot. By snapshotting the scenario details when a configuration is saved, administrators and procurement leads won't lose historical context when buyers refine their email instructions or retire old seasonal scenarios later on.

At the same time, it is important to be clear about what the roadmap entry does not claim. The roadmap description does not specify which business entities beyond purchase orders will be selectable, what guardrails or character limits will govern the custom prompt instructions, or whether system administrators can lock down scenario creation separately from standard task configuration. Furthermore, this feature specifically addresses outbound follow-up emails; it does not alter how the Procurement Agent reads and interprets inbound supplier emails for order quantity changes, price adjustments, or delivery date updates.

In the current production-ready preview documented on Microsoft Learn, agent tasks are designed to generate just one email per purchase order unless the purchase order itself changes. When procurement teams want to send a second follow-up to an unresponsive vendor without an underlying order change, Microsoft currently advises creating two separate tasks with non-overlapping date ranges—for example, one task covering delivery dates between seven days ago and today, and a second covering dates earlier than eight days ago. While custom scenarios will make it much easier to tailor the messaging intent for different stages of supplier outreach, Microsoft has not indicated that roadmap item 573705 changes the underlying one-email-per-order task mechanics.

Section Summary: Capturing scenario definitions inside saved configurations prevents historical ambiguity when rules change, though IT teams should note that Microsoft has not yet detailed entity limits, prompt validation rules, or any changes to the agent's single-email-per-order execution logic.

Current Architecture, Prerequisites, and Governance Boundaries​

Because custom scenarios will plug into the existing Procurement Agent supplier communications framework, ERP administrators planning for the December 2026 rollout can evaluate their readiness today using Microsoft Learn's current setup and administration requirements:

Human Review vs. Automatic Sending​

Giving end-users the ability to write custom instructions that shape AI-generated supplier emails naturally raises a governance question: Who checks the AI's homework before it hits a vendor's inbox?

In Microsoft's documented architecture, automatic email transmission is governed by a separate, optional Feature Management toggle: (Production ready preview) Procurement Agent - Supplier communications - automatically sending follow-up emails, which is turned off by default.

• Draft Mode (Default): The agent generates draft messages under Procurement and Sourcing > (Preview) Procurement Agent - Supplier communications > (Preview) Follow-up emails. A human buyer reviews, edits, and clicks Send, and the email is transmitted from that buyer's own email address.
• Automatic Sending Mode: If an administrator enables the optional auto-send feature and configures Microsoft Graph as the batch and interactive email provider (with valid Azure Application ID and secret credentials), the agent sends messages without human intervention. These emails are sent from the configured agent identity user email address, and an email footer—such as "This email was written with the help of AI"—becomes mandatory.

Microsoft explicitly recommends leaving automatic sending turned off in sandbox environments, where stale purchase order data or missing vendor contact details could trigger unwanted or misdirected messages. That advice becomes even more practical when buyers start testing custom scenario instructions later this year.

Vendor Recipient Logic​

Administrators should also verify how vendor contact records are structured under Procurement and sourcing > Vendors > All vendors. According to Microsoft Learn, the Procurement Agent selects recipient addresses using a strict hierarchy:

1. If a contact line has its Purpose set to Purchase Order Communications (the priority email address), the agent always uses that address, whether emails are sent per purchase order or grouped per vendor.
2. If no priority address exists and emails are grouped per vendor, the agent uses the Primary email address (or arbitrarily picks an email line if none is marked Primary).
3. If no priority address exists and emails are sent per purchase order, the agent checks the Email field on the purchase order header first, falling back to the vendor's contact information if the PO field is blank.

Billing Considerations​

Finally, keep an eye on capacity planning. Microsoft Learn notes that the supplier communications features consume Microsoft Copilot Studio credits, charging a fixed cost every time the outbound follow-up batch job runs and a variable cost based on the number of emails generated. While the roadmap entry does not indicate any pricing changes for custom scenarios, empowering buyers to spin up additional scenario-driven tasks could increase both the number of scheduled batch runs and the volume of generated emails.

Section Summary: Deploying Procurement Agent features requires Dynamics 365 SCM 10.0.44+, specific Copilot app versions, Dataverse mailbox sync, and Copilot Studio credit capacity. Administrators retain full control over whether custom-scenario emails are held as drafts for human review or sent automatically via Microsoft Graph.