Dynamics 365 Supply Chain Management: Procurement Agent - Define custom scenarios for agent-generated supplier emails
Business end-users and buyers can define and maintain their own outbound follow-up scenarios and use them wherever built-in scenarios are used today: Scenario maintenance — a dedicated setup page where users create, edit, and maintain custom follow-up scenarios. Each scenario car
DIGITAL SKILL WORKS LTD / 12 PANES
What it is
Dynamics 365 Supply Chain Management: Procurement Agent - Define custom scenarios for agent-generated supplier emails is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.
What it does
Business end-users and buyers can define and maintain their own outbound follow-up scenarios and use them wherever built-in scenarios are used today: Scenario maintenance — a dedicated setup page where users create, edit, and maintain custom follow-up scenarios. Each scenario carries its own name, the instructions that shape the email the agent writes, and the business entity it applies to. Scenario-driven configuration — follow-up configurations are built around the chosen scenario, so criteria, email content, and agent behavior all follow the scenario the user selected. Scenario-driven runtime — when the agent runs, it generates and sends messages according to the selected scenario's intent and instructions. Self-describing configuration history — scenario details are captured with each saved configuration, so the audit history of an agent configuration remains readable even if the underlying scenario definition is later changed or removed.
Why you should care
Board
Agents change operating risk. Ask for registry coverage and owner accountability first.
CISO
Treat agents as privileged actors: least privilege, owner, lifecycle, and audit before scale.
CFO
Map licence or consumption impact to the frozen value case; avoid seat spray.
Adoption
Pilot with a named cohort and measure changed work, not vanity clicks.
Suggested action
Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Put this on the agent register with a named owner. Do not enable broadly until permissions, DLP, and reclaim rules exist.
12 Panes: 03 Horizon · 05 GRC · 08 Adoption · 04 Security · 09 Work & Skills
Communication needed
- Security: Assess exposure, Conditional Access, and agent/tool permissions.
- GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
- FinOps: Forecast seat or credit impact; align to frozen value case.
- Adoption: Plan cohort messaging, clinics, and success measures.
- Comms: One story for board and staff — what changes, what does not, who owns risk.
Benefits
- May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
- Roadmap visibility helps Horizon planning without guessing dates.
- Agents can automate multi-step work inside existing Microsoft 365 permissions.
Risks
- Status and dates change; treat MRC as directional, not a contract.
- Enabling without Steady controls can amplify overshare or cost leakage.
- Agents act; over-privilege and ownerless agents create lasting exposure.
- Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.
Source
- MRC id: 573705
- Status: In development
- Products: Dynamics 365 Supply Chain Management
- GA / disclosure: December CY2026
- Preview: —
- Platforms: Web
- Cloud instances: Worldwide (Standard Multi-Tenant)
- moreInfoUrls: —
- Open on Microsoft 365 Roadmap
Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.