Dynamics 365 Commerce: Enable MCP tools for POS returns

Dynamics 365 Commerce: Enable MCP tools for POS returns is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

This feature provides reusable MCP tools for Store Commerce POS returns. These tools expose Commerce return capabilities as structured actions that customers, partners, and agent developers can use to build conversational or agentic return experiences. The tools enable agentic experiences to look up the original purchase using supported identifiers such as receipt, order, invoice, or confirmation number; retrieve matching transactions and returnable lines; identify items that are returnable, partially returnable, already returned, or not returnable; create a return using selected lines, quantities, and reason codes; determine eligible refund options for original-tender refund scenarios; and execute eligible original-tender refunds through existing Commerce return and payment logic. The tools can also explain return eligibility, policy restrictions, and why specific lines may or may not be returnable. They can analyze prior returns and refunds to surface duplicate-refund risk, frequent-return patterns, cross-store return history, or other return-risk indicators. Tool responses provide structured data that host experiences can use to present return details, choices, summaries, and next steps in the experience they build. Customers can use these tools from POS-embedded agents, chat-based copilots, workflow orchestrators, or other agentic surfaces. Setup is performed by an administrator, IT owner, or implementation partner. Customers configure the host surface, authorize the agent or integration to call the tools, and maintain existing Commerce return policies, reason codes, tender rules, and payment configuration.

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 · 04 Security · 05 GRC · 09 Work & Skills

• 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.

• 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.

• 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.

• MRC id: 574124
• Status: In development
• Products: Dynamics 365 Commerce
• GA / disclosure: March CY2027
• Preview: October CY2026
• Platforms: Android, Desktop, iOS, Mac, 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.