Innovate Your Business
with Our Insights!

General availability adds two capabilities beyond the original scope. Policy checks now extend past the email body to text-based attachments, including PDFs, Word documents, and text files, and administrators can set Low, Medium, High, or Very High strictness levels so each policy enforces at the sensitivity and business risk appropriate to its scenario. Simulation and reporting tools let teams validate policies before turning them on broadly, and enforcement can be set to flag or block outbound messages that fail a check. 

Governance is one of two skills inside the Quality Management agent, working alongside Quality Evaluation, which assesses interactions against quality standards, so the pairing gives service organizations one framework covering both compliance and quality as AI takes on a larger share of customer communication. 

For customer service teams scaling AI-generated responses, this is the kind of control worth building into a compliance plan alongside the guidance in our Dynamics 365 security and compliance guide.

The addition lets implementation teams open and navigate standard business process diagrams, explore process hierarchies, and mark processes as in or out of scope, all inside the same project profiling experience they already use, which is also the primary channel for the required Go Live Readiness workshop on finance and operations projects. Microsoft's stated goal is a shared starting point for scoping conversations, so business and technical stakeholders are working from the same standard process reference from day one rather than reconciling different assumptions later in the project. 

Microsoft points to Kiwa, a global testing, inspection, and certification organization, as an early user of the underlying catalog to harmonize service operations across more than 200 legal entities in over 40 countries, comparing current-state and future-state processes to align stakeholders around one operating model during a global rollout. 

For organizations scoping a new implementation or a multi-entity rollout, grounding early discovery in a standard process reference is exactly the discipline we outline in our Dynamics 365 implementation best practices guide.

The release ships five capabilities: cross-legal-entity fulfillment groups that span warehouses and stores across companies, inventory visibility that lets the optimization engine draw from a larger pool, fulfillment profiles that apply logic consistently while preserving entity-specific settings, automated intercompany transaction orchestration, and execution that keeps the original sales order and the intercompany purchase and sales orders synchronized throughout. In Microsoft's example, a retailer with separate entities in Germany, France, and Spain can take an order in Germany, automatically source it from available French stock, and route fulfillment there without manual intercompany coordination. 

This is currently scoped to retail sales orders across POS, e-commerce, call center, and headless channels, with support for standard Supply Chain Management sales orders on the roadmap but not yet committed. It builds directly on Cross-Legal-Entity Inventory Lookup, released earlier this year, which gave store associates visibility into stock at other entities. Microsoft also used the same release to note that Distributed Order Management now supports advanced warehouse-enabled items, closing a gap where those items were previously excluded from sourcing and fulfillment optimization. 

For multi-entity operations weighing what this means for warehouse and fulfillment strategy, it is a natural extension of the fundamentals we walk through in our guide to Dynamics 365 warehouse management.

The module is built on Microsoft Power Platform rather than as a standalone add-on. Dataverse holds the supplier engagement data model, while model-driven Power Apps and Power Pages deliver the procurement team and supplier-facing experiences, with Dynamics 365 Supply Chain Management remaining the system of record for operational transactions. A global vendor management layer lets organizations maintain one shared supplier profile, covering contacts, addresses, certifications, and capabilities, and release it into one or more legal entities once qualification and approval are complete, which addresses the duplicate and inconsistent supplier records that multi-entity organizations often accumulate. 

Underneath, event-driven synchronization and configurable mappings keep Dataverse and Supply Chain Management aligned, and Microsoft is explicit that this mechanism is separate from standard dual-write and should not be configured alongside it for the same entities, since running both can create duplicate records. Microsoft frames the deeper motivation as preparing supplier data for agentic procurement: agents need not just access to supplier data but the surrounding business context, permissions, and approvals, and a fragmented supplier environment makes that context harder to establish. 

For procurement and IT teams evaluating this, the module is worth watching alongside the broader supply chain features Dynamics 365 already brings to the table, which we cover in our roundup of Dynamics 365 Supply Chain Management features. 

The change is a response to how organizations actually run Microsoft's stack. Few customers operate Dynamics 365 in isolation. It increasingly works alongside Power Platform, Microsoft 365, Copilot, and custom agents built in Copilot Studio to power the same business processes, so Microsoft wants one destination where teams can filter to the products they use, export views to CSV, subscribe by RSS, and search by feature ID rather than reconstructing plans from separate wave announcements twice a year. 

The transition runs on a set timeline. Roadmap content with a public preview or general availability date of June 1, 2026 or later will move over between September and November 2026, and Release Planner retires by November 15, 2026 once the move completes. Products keep their existing release schedules, Message Center stays the source for tenant specific change notices, and Microsoft Learn remains the documentation home, so the shift changes how Microsoft communicates upcoming work rather than how it ships product. 

For IT and operations leaders, the practical effect is that roadmap planning becomes a rolling exercise rather than a twice a year event, which rewards teams that already treat Dynamics 365 and Power Platform as one connected estate. We have been tracking that convergence in our look at where Business Central's AI agents are headed, and our Dynamics 365 AI Solutions practice helps clients set a monthly or quarterly review rhythm that keeps pace with always-on disclosure instead of waiting for the next wave.