A preliminary RAM 2025™ multi-model assessment, framed as inquiry rather than as settled diagnosis. Microsoft’s own published material already acknowledges that “when data is fragmented across systems, agents can’t act with autonomy.” The framework’s question for Sameer Verma is what Microsoft is thinking about the multi-wave compounding dimension of that fragmentation, and where pre-commitment substrate diagnostic work fits alongside the data-and-process standardization Microsoft’s own material identifies as prerequisite.
On May 4, 2026, Sameer Verma published a Microsoft Dynamics 365 blog post titled “From intelligence to impact: How agentic AI is reshaping today’s supply chain.” Sameer is Vice President and Chief Product Officer of Microsoft Dynamics 365 AI ERP and drives Microsoft’s vision for Agentic ERP across Finance, Supply Chain, Commerce, HR, and Project Operations. The post describes how the Dynamics 365 ERP Model Context Protocol (MCP) Server, Microsoft 365 Copilot, Agent 365, and Work IQ work together to enable agents to reason over data, take action across workflows, and operate within defined business policies. The capabilities described represent the most ambitious agentic ERP architecture in the market.
When a colleague forwarded the piece earlier this week and asked what it would take to implement and execute on what Microsoft says it can do, the question triggered a memory of work the Procurement Insights archive has been documenting since 2007: the recurring strategic ambition to fuse the productivity layer where workers actually work with the operational data layer where the enterprise actually runs. In June 2004, that ambition was the Mendocino Project — a Microsoft and SAP partnership that became Duet, which attempted to bring SAP business processes into Outlook and Excel. The 2007 archive analysis framed Mendocino as a brilliant strategic move to sidestep antitrust scrutiny while creating an operational integration that would make the SAP-plus-Microsoft combination the de facto enterprise operating environment.
The framework has revisited that genealogy twice since. In April 2023, responding to David Loseby’s LinkedIn observation about the myth of the single source solution, the framework asked what procurement’s digital transformation might have looked like had Mendocino succeeded. In October 2025, responding to IBM’s acquisition of Cognitus, the framework asked whether the acquisition was a replay of Duet/Mendocino with better AI branding. The October 2025 piece used the ARA RAM 2025™ multi-model assessment to surface a preliminary structural read: integration ambition without substrate validation tends to reproduce the same outcome regardless of the technology generation that frames it.
This piece extends that documented analytical thread to the 2026 Microsoft Dynamics 365 agentic ERP positioning, with one structurally important calibration. Microsoft’s broader public material on Dynamics 365 agentic AI revealed that Microsoft has already publicly acknowledged the substrate question that the framework’s preliminary read assumed Microsoft was missing. That discovery changes the structural function of this piece. It is no longer a diagnosis of what Microsoft is missing. It is a substantive inquiry into what Microsoft has figured out that the public positioning has not yet fully surfaced.
What Microsoft has actually acknowledged publicly
The Sameer Verma piece, read in isolation, foregrounds capability rather than precondition. Agents reason over data. Agents take action across workflows. The MCP Server provides governed access. Work IQ gives agents real-time context. Agent 365 lets IT teams observe, govern, and secure agents. The piece is calibrated for executive supply chain leaders attending the Gartner Supply Chain Symposium, and the marketing function of that calibration is to surface what is now possible rather than to surface what is required first.
Microsoft’s broader public material engages the precondition question more substantively. From the Microsoft Dynamics 365 Convergence 2025 blog post published December 9, 2025:
“When this data is fragmented across systems, agents can’t act with autonomy, and AI can only answer questions instead of accelerating outcomes.”
That sentence, published by Microsoft, names exactly what the Compounding Technology Shadow Wave™ framework names. Data fragmentation prevents agents from operating autonomously. The substrate condition determines whether the agentic ERP architecture produces sustained outcomes. Microsoft has not used the framework’s vocabulary. Microsoft has identified the same structural reality through different language.
The independent analyst coverage of the 2026 Release Wave 1 announcement extends the acknowledgment further. From the March 2026 industry analysis summarizing what enterprise software teams should know about agentic AI in Dynamics 365:
“Many organizations running Dynamics 365 still contend with fragmented data across multiple instances, legacy integrations held together with custom code, and business processes that vary by region or division. Before an AI agent can autonomously manage order-to-cash or procure-to-pay, the underlying data and process standardization must be in place… Agentic AI amplifies whatever it finds: clean, well-governed data produces intelligent automation; messy data produces automated chaos.”
The formulation “Agentic AI amplifies whatever it finds” is structurally identical to the framework’s March 2026 formulation — “AI doesn’t break broken processes. It perfects them.” Different vocabulary. Same diagnosis. The framework’s archive has been documenting this dynamic since 2007. Microsoft and the analyst community engaging Microsoft’s positioning are documenting it now. The convergence is real.
The Top Dynamics Partners evaluation framework, updated in April 2026 in response to Release Wave 1, now explicitly includes “Copilot deployment experience, agent design capabilities, Work IQ integration readiness, and AI governance practices” as partner selection criteria. The framework agrees with this calibration. Organizational readiness is the variable. Partner capability calibrated to that readiness is one of the determining factors in whether deployment produces sustained outcomes.
So the preliminary diagnosis the framework would have produced from the Sameer Verma piece in isolation — that Microsoft is repeating the Mendocino ambition without surfacing the substrate question — turns out to be only partially correct. Microsoft has surfaced the substrate question publicly. The Sameer Verma supply chain marketing piece does not foreground it because that specific piece is calibrated to a different audience function. The framework’s preliminary read needs to be recalibrated to what Microsoft has actually published, not to what one marketing piece alone surfaces.
The Mendocino genealogy as historical context for the contemporary ambition
The structural parallel between the 2007 Mendocino Project and the 2026 Microsoft Dynamics 365 agentic ERP architecture is genuine and worth being explicit about, with the calibration that historical parallels surface structural patterns rather than predict specific outcomes.
The 2007 ambition was to embed SAP business processes into Microsoft Office so that workers could execute ERP transactions from Outlook and Excel without learning the SAP user interface. The structural move was integration at the productivity layer, with the productivity layer functioning as the abstraction that made the underlying ERP usable. The 2007 archive analysis framed this as a brilliant strategic move that would also, if successful, lock the procurement-tech ecosystem into the SAP-plus-Microsoft operational frame.
The 2026 ambition is structurally similar but operates at materially different scale. Where Mendocino brought ERP transactions to workers through productivity tools, Dynamics 365 agentic ERP brings autonomous execution to the worker’s operating context. Agents reason across Outlook, Teams, Word, and Dynamics 365 simultaneously, taking action on orders, supply plans, and transfers based on current conditions. The MCP Server provides the governed pathway for agentic access to ERP data. Work IQ gives agents real-time context drawn from the productivity tools where decisions are made. Agent 365 provides the observability and governance layer.
The structural pattern is the same — the productivity layer is the fusion point with the operational data layer. The technology generation is different — workflow integration in 2007, agentic execution in 2026. The scale is materially different — Microsoft alone in 2026 owns the productivity layer, the operational data layer, and the agentic execution layer through wholly-owned vertical integration that the 2007 Microsoft-SAP partnership could only attempt across organizational boundaries.
The 2025 IBM and Cognitus acquisition operated in adjacent territory, focused on SAP S/4HANA transformation services rather than on the productivity-plus-operational-data fusion specifically. The framework’s October 2025 analysis surfaced a preliminary read that integration ambition without substrate validation tends to reproduce the same structural outcome regardless of the technology generation. The contemporary Microsoft positioning is the most ambitious version of the productivity-plus-operational-data fusion that the framework’s archive has documented across nineteen years of continuous engagement with the procurement and ERP technology discourse.
The genealogy provides context, not prediction. Microsoft in 2026 is not 2007 SAP-plus-Microsoft. Microsoft in 2026 is not 2025 IBM-plus-Cognitus. The contemporary architecture has substantially more sophisticated technical capability, broader strategic surface area, and demonstrably more substantive public engagement with the substrate question than either prior iteration of the productivity-plus-operational-data ambition. The genealogy surfaces the recurring strategic pattern. The contemporary positioning warrants its own structural analysis.
The framework’s preliminary RAM 2025™ multi-model read
Following the methodology the October 2025 IBM/Cognitus assessment used, the framework applied a multi-model ARA RAM 2025™ preliminary assessment to the Sameer Verma piece, the Mendocino archive thread, and the broader Microsoft public positioning on Dynamics 365 agentic ERP. Four models produced independent reads. The reads converged on several structural observations and diverged on others. The converged observations form the preliminary read; the divergences indicate where the framework’s analytical confidence is calibrated to actively held uncertainty rather than to settled conclusion.
Converged observation one. The contemporary Microsoft positioning operates in the same structural territory as the 2007 Mendocino ambition. The productivity layer is the abstraction that makes the operational data layer usable. The fusion point is where transformation happens. This convergence is grounded in the explicit architectural decisions Microsoft has documented — MCP Server as the agent-to-ERP pathway, Work IQ as the productivity-to-operational-data signal layer, Copilot as the unified surface that operates across both.
Converged observation two. Microsoft’s broader public material engages the substrate question that the Sameer Verma piece in isolation does not foreground. The Convergence 2025 acknowledgment that “when data is fragmented across systems, agents can’t act with autonomy” is structurally identical to the framework’s substrate inheritance diagnosis. The contemporary Microsoft positioning is not unaware of the precondition. The marketing materials calibrated to different audiences surface the precondition with different levels of emphasis.
Converged observation three. The framework’s nineteen-year archive on the productivity-plus-operational-data ambition produces analytical context that the contemporary procurement-tech discourse has not consistently surfaced. The Mendocino genealogy, the 2007 Dangerous Supply Chain Myths Part 7 finding that “process and not technology is the driving force behind a successful e-procurement initiative,” the 1998 Department of National Defence agent-based Metaprise R&D engagement that produced the framework’s foundational proof case — this body of work has been documenting the substrate-versus-technology question for nineteen years. The contemporary engagement with Microsoft’s positioning operates from analytical context the broader discourse does not yet have.
Diverged observation. The four models diverged on whether the contemporary Microsoft positioning has substantively engaged the multi-wave compounding dimension of the substrate condition the framework names. Microsoft has publicly acknowledged that data fragmentation prevents agentic autonomy. Microsoft has not (in the public material the framework has surfaced) explicitly engaged the recognition that the data fragmentation is itself the residue of four technology generations of unresolved operating decisions — Wave 1 spreadsheets accumulating since approximately 1990, Wave 2 BYOD fragmentation accumulating since approximately 2007, Wave 3 SaaS sprawl accumulating since approximately 2012, and now Wave 4 AI deployment landing on top of the unresolved substrate from the prior three waves.
The diverged observation is where the framework’s preliminary read becomes a substantive inquiry rather than a settled diagnosis. The framework does not know what Microsoft is thinking about the multi-wave dimension. The framework has surfaced the broader public material it could find. That material acknowledges the substrate question at the data-and-process-standardization level. The material does not (so far as the framework has been able to surface) engage the multi-wave compounding dimension explicitly.
What the framework is asking Sameer Verma
The framework’s substantive question, grounded in the preliminary RAM 2025™ multi-model read and presented as inquiry rather than as assertion, is the following.
Microsoft has publicly acknowledged that data fragmentation across systems prevents agents from acting with autonomy. The framework’s archive documents that the data fragmentation typically encountered in 2026 enterprise environments is not the residue of any single technology generation — it is the cumulative residue of four technology generations of unresolved operating decisions, each of which calibrated the underlying operating model to a pre-AI condition. Spreadsheets accumulated local overrides and shadow logic since approximately 1990. BYOD-era systems fragmented identity management and access control since approximately 2007. SaaS sprawl produced disconnected approval paths and decentralized data ownership since approximately 2012. The Wave 4 AI deployment is now landing on top of the cumulative substrate residue from those three prior waves.
How is the Dynamics 365 team thinking about the multi-wave compounding dimension of the substrate fragmentation that Microsoft has already acknowledged? The framework’s diagnostic instrument, Phase 0™, is calibrated to surface the cumulative substrate condition across all four waves before deployment commitment, producing a documented readiness profile that informs whether the technology layer’s capability will produce sustained outcomes or amplify the prior-wave inheritance at machine speed. Where does pre-commitment multi-wave substrate diagnostic work fit alongside the data-and-process standardization Microsoft’s broader public material identifies as prerequisite for agentic autonomy?
The question is not whether Dynamics 365 agentic ERP will produce sustained outcomes. The question is what the pre-commitment work needs to look like for organizations evaluating the architecture to actually realize the outcomes the architecture is capable of producing. The framework’s preliminary read is that the multi-wave compounding dimension is materially significant and that Phase 0™-style substrate diagnostic work operates upstream of the data-and-process standardization Microsoft’s own material identifies. The framework is asking Sameer how Microsoft is thinking about that upstream layer, because Microsoft’s senior leadership in the Dynamics 365 product organization has substantially more visibility into actual deployment patterns across customer organizations than the framework’s archive can produce from external observation alone.
Why this inquiry is structurally significant for the broader procurement-tech discourse
The framework’s body of work has been engaging the substrate question continuously for nineteen years. The recent runway — the Compounding Technology Shadow Wave™ trilogy, the financial impact piece, the Eric Kimberling engagement piece on agile in ERP, the forthcoming Tealbook/Supplier.io merger demonstration piece — operates at multiple analytical layers simultaneously. Structural diagnosis. Financial measurement. Methodology convergence. Operational case demonstration.
The Microsoft Dynamics 365 positioning operates at the highest analytical layer of the contemporary agentic ERP discourse. Microsoft is the largest enterprise software vendor in the world. Dynamics 365 with Copilot, Agent 365, and the MCP Server is the most sophisticated agentic ERP architecture in the market. Sameer Verma’s leadership position in the Dynamics 365 product organization gives him visibility into deployment patterns at a substantially larger scale than is normally recognized and utilized to its full potential. The substantive question the framework is asking him is not rhetorical. It is the kind of question that, if engaged substantively, produces analytical work neither the framework nor Microsoft alone could produce.
The October 2025 IBM/Cognitus piece used the same preliminary RAM 2025™ inquiry construction. The piece engaged the IBM acquisition as a structural question rather than as a settled diagnosis, allowed for the possibility that the acquisition might break the historical pattern, and surfaced the framework’s analytical context as background for the inquiry rather than as oppositional foreground. The contemporary Microsoft engagement follows the same structural template. The framework asks. The engaged party (in this case Microsoft, through Sameer Verma directly if he chooses to engage) responds substantively. The dialogue produces analytical work that survives multi-model scrutiny and the engaged party’s substantive response.
That construction is structurally rare in the contemporary procurement-tech discourse. Most vendor engagement operates either as marketing-aligned positive coverage or as adversarial commentary that the engaged party has no productive reason to engage. The preliminary RAM 2025™ inquiry construction sits between those poles. It engages substantively while inviting refinement. It surfaces preliminary analytical reads while explicitly holding them as preliminary. It positions the framework as engaging from genuine inquiry rather than from asserted analytical priority.
The framework’s analytical posture and what it invites
The framework’s nineteen-year archive on substrate inheritance and operating-model coherence is substantial. The contemporary Compounding Technology Shadow Wave™ vocabulary formalizes analytical positions that have been continuously documented since 2007. The framework’s commercial proposition, Phase 0™ as a pre-commitment substrate diagnostic, is calibrated to exactly the decision point organizations face when evaluating sophisticated technology like Dynamics 365 agentic ERP.
None of that means the framework knows what Microsoft has figured out about agentic ERP deployment that Microsoft has not yet surfaced publicly. The framework has one Sameer Verma marketing piece, the Microsoft broader public material discovered through search, the Mendocino archive thread, and the multi-model preliminary assessment. That is real evidence. It is also bounded evidence. Microsoft’s product organization has visibility into actual customer deployments, observed failure modes, architectural decisions made and not made, and deployment patterns the public material does not surface. The framework genuinely wants to know what Microsoft has figured out that the public positioning has not yet fully surfaced.
If Microsoft has substantively engaged the multi-wave compounding dimension through architectural decisions that the public material does not yet describe, the framework’s preliminary read needs to be refined and the analytical contribution recalibrated. If Microsoft has not yet engaged that dimension, the framework’s preliminary read identifies an opportunity where Phase 0™-style substrate diagnostic work complements the data-and-process standardization Microsoft’s own material identifies as prerequisite. Either outcome produces value. Either outcome advances the substantive analytical work. Either outcome is preferable to publishing a settled diagnosis from incomplete evidence.
The framework’s question to Sameer Verma stands. The framework’s analytical posture is honest about its preliminary status. The framework’s commercial proposition, Phase 0™ as a pre-commitment substrate diagnostic, is positioned as complementary to what Microsoft has publicly identified as the precondition for agentic autonomy rather than as oppositional to Microsoft’s architectural ambition. The framework invites Sameer’s response and the broader Dynamics 365 product organization’s engagement. The dialogue is the work.
The framework’s preliminary RAM 2025™ multi-model assessment of the Microsoft Dynamics 365 agentic ERP positioning is published here as inquiry rather than as settled diagnosis. The framework genuinely does not know what Microsoft has figured out about agentic ERP deployment that the public positioning has not yet surfaced. The substantive question — how the Dynamics 365 team is thinking about the multi-wave compounding dimension of the substrate fragmentation Microsoft has already acknowledged — is asked because the answer matters. Sameer Verma and the broader Microsoft Dynamics 365 product organization are explicitly invited to respond. If the response refines or refutes the framework’s preliminary read, the framework will publish the refinement. The dialogue is structurally more valuable than the unilateral assessment.
From Peesker’s 2018 declaration that companies will either ‘transform or be transformed’ to Sameer’s expanded Microsoft Dynamics 365 offering, where is the company truly heading?
Author note: Jon W. Hansen interviewed Kevin Peesker, then President of Microsoft Canada, on April 4, 2018 at the Activate Digital 2018 event hosted by Long View Systems. That interview is part of the Procurement Insights archive. The archive’s engagement with Microsoft’s product and leadership positioning has been continuous across multiple technology generations. The October 2025 IBM/Cognitus preliminary RAM 2025™ assessment used the same structural template applied here to the contemporary Microsoft Dynamics 365 agentic ERP positioning.
Compounding Technology Shadow Wave™ · Hansen Deflator Formula™ · Hansen Optionality Loss Estimate™ · Phase 0™ · Hansen Fit Score™ (HFS™) · RAM 2025™ · Real-World Condition Substrate™ · Strand Commonality™ · ARA™ · Implementation Physics™
Hansen Models™ · Founder: Jon W. Hansen · hansenprocurement.com
-30-
Procurement Insights
Is Microsoft’s 2026 Agentic ERP Architecture A Scaled Version Of The 2007 Mendocino Project — And What Has The Dynamics 365 Team Figured Out That The Public Positioning Has Not Yet Surfaced?
Posted on May 12, 2026
0
A preliminary RAM 2025™ multi-model assessment, framed as inquiry rather than as settled diagnosis. Microsoft’s own published material already acknowledges that “when data is fragmented across systems, agents can’t act with autonomy.” The framework’s question for Sameer Verma is what Microsoft is thinking about the multi-wave compounding dimension of that fragmentation, and where pre-commitment substrate diagnostic work fits alongside the data-and-process standardization Microsoft’s own material identifies as prerequisite.
On May 4, 2026, Sameer Verma published a Microsoft Dynamics 365 blog post titled “From intelligence to impact: How agentic AI is reshaping today’s supply chain.” Sameer is Vice President and Chief Product Officer of Microsoft Dynamics 365 AI ERP and drives Microsoft’s vision for Agentic ERP across Finance, Supply Chain, Commerce, HR, and Project Operations. The post describes how the Dynamics 365 ERP Model Context Protocol (MCP) Server, Microsoft 365 Copilot, Agent 365, and Work IQ work together to enable agents to reason over data, take action across workflows, and operate within defined business policies. The capabilities described represent the most ambitious agentic ERP architecture in the market.
When a colleague forwarded the piece earlier this week and asked what it would take to implement and execute on what Microsoft says it can do, the question triggered a memory of work the Procurement Insights archive has been documenting since 2007: the recurring strategic ambition to fuse the productivity layer where workers actually work with the operational data layer where the enterprise actually runs. In June 2004, that ambition was the Mendocino Project — a Microsoft and SAP partnership that became Duet, which attempted to bring SAP business processes into Outlook and Excel. The 2007 archive analysis framed Mendocino as a brilliant strategic move to sidestep antitrust scrutiny while creating an operational integration that would make the SAP-plus-Microsoft combination the de facto enterprise operating environment.
The framework has revisited that genealogy twice since. In April 2023, responding to David Loseby’s LinkedIn observation about the myth of the single source solution, the framework asked what procurement’s digital transformation might have looked like had Mendocino succeeded. In October 2025, responding to IBM’s acquisition of Cognitus, the framework asked whether the acquisition was a replay of Duet/Mendocino with better AI branding. The October 2025 piece used the ARA RAM 2025™ multi-model assessment to surface a preliminary structural read: integration ambition without substrate validation tends to reproduce the same outcome regardless of the technology generation that frames it.
This piece extends that documented analytical thread to the 2026 Microsoft Dynamics 365 agentic ERP positioning, with one structurally important calibration. Microsoft’s broader public material on Dynamics 365 agentic AI revealed that Microsoft has already publicly acknowledged the substrate question that the framework’s preliminary read assumed Microsoft was missing. That discovery changes the structural function of this piece. It is no longer a diagnosis of what Microsoft is missing. It is a substantive inquiry into what Microsoft has figured out that the public positioning has not yet fully surfaced.
What Microsoft has actually acknowledged publicly
The Sameer Verma piece, read in isolation, foregrounds capability rather than precondition. Agents reason over data. Agents take action across workflows. The MCP Server provides governed access. Work IQ gives agents real-time context. Agent 365 lets IT teams observe, govern, and secure agents. The piece is calibrated for executive supply chain leaders attending the Gartner Supply Chain Symposium, and the marketing function of that calibration is to surface what is now possible rather than to surface what is required first.
Microsoft’s broader public material engages the precondition question more substantively. From the Microsoft Dynamics 365 Convergence 2025 blog post published December 9, 2025:
That sentence, published by Microsoft, names exactly what the Compounding Technology Shadow Wave™ framework names. Data fragmentation prevents agents from operating autonomously. The substrate condition determines whether the agentic ERP architecture produces sustained outcomes. Microsoft has not used the framework’s vocabulary. Microsoft has identified the same structural reality through different language.
The independent analyst coverage of the 2026 Release Wave 1 announcement extends the acknowledgment further. From the March 2026 industry analysis summarizing what enterprise software teams should know about agentic AI in Dynamics 365:
The formulation “Agentic AI amplifies whatever it finds” is structurally identical to the framework’s March 2026 formulation — “AI doesn’t break broken processes. It perfects them.” Different vocabulary. Same diagnosis. The framework’s archive has been documenting this dynamic since 2007. Microsoft and the analyst community engaging Microsoft’s positioning are documenting it now. The convergence is real.
The Top Dynamics Partners evaluation framework, updated in April 2026 in response to Release Wave 1, now explicitly includes “Copilot deployment experience, agent design capabilities, Work IQ integration readiness, and AI governance practices” as partner selection criteria. The framework agrees with this calibration. Organizational readiness is the variable. Partner capability calibrated to that readiness is one of the determining factors in whether deployment produces sustained outcomes.
So the preliminary diagnosis the framework would have produced from the Sameer Verma piece in isolation — that Microsoft is repeating the Mendocino ambition without surfacing the substrate question — turns out to be only partially correct. Microsoft has surfaced the substrate question publicly. The Sameer Verma supply chain marketing piece does not foreground it because that specific piece is calibrated to a different audience function. The framework’s preliminary read needs to be recalibrated to what Microsoft has actually published, not to what one marketing piece alone surfaces.
The Mendocino genealogy as historical context for the contemporary ambition
The structural parallel between the 2007 Mendocino Project and the 2026 Microsoft Dynamics 365 agentic ERP architecture is genuine and worth being explicit about, with the calibration that historical parallels surface structural patterns rather than predict specific outcomes.
The 2007 ambition was to embed SAP business processes into Microsoft Office so that workers could execute ERP transactions from Outlook and Excel without learning the SAP user interface. The structural move was integration at the productivity layer, with the productivity layer functioning as the abstraction that made the underlying ERP usable. The 2007 archive analysis framed this as a brilliant strategic move that would also, if successful, lock the procurement-tech ecosystem into the SAP-plus-Microsoft operational frame.
The 2026 ambition is structurally similar but operates at materially different scale. Where Mendocino brought ERP transactions to workers through productivity tools, Dynamics 365 agentic ERP brings autonomous execution to the worker’s operating context. Agents reason across Outlook, Teams, Word, and Dynamics 365 simultaneously, taking action on orders, supply plans, and transfers based on current conditions. The MCP Server provides the governed pathway for agentic access to ERP data. Work IQ gives agents real-time context drawn from the productivity tools where decisions are made. Agent 365 provides the observability and governance layer.
The structural pattern is the same — the productivity layer is the fusion point with the operational data layer. The technology generation is different — workflow integration in 2007, agentic execution in 2026. The scale is materially different — Microsoft alone in 2026 owns the productivity layer, the operational data layer, and the agentic execution layer through wholly-owned vertical integration that the 2007 Microsoft-SAP partnership could only attempt across organizational boundaries.
The 2025 IBM and Cognitus acquisition operated in adjacent territory, focused on SAP S/4HANA transformation services rather than on the productivity-plus-operational-data fusion specifically. The framework’s October 2025 analysis surfaced a preliminary read that integration ambition without substrate validation tends to reproduce the same structural outcome regardless of the technology generation. The contemporary Microsoft positioning is the most ambitious version of the productivity-plus-operational-data fusion that the framework’s archive has documented across nineteen years of continuous engagement with the procurement and ERP technology discourse.
The genealogy provides context, not prediction. Microsoft in 2026 is not 2007 SAP-plus-Microsoft. Microsoft in 2026 is not 2025 IBM-plus-Cognitus. The contemporary architecture has substantially more sophisticated technical capability, broader strategic surface area, and demonstrably more substantive public engagement with the substrate question than either prior iteration of the productivity-plus-operational-data ambition. The genealogy surfaces the recurring strategic pattern. The contemporary positioning warrants its own structural analysis.
The framework’s preliminary RAM 2025™ multi-model read
Following the methodology the October 2025 IBM/Cognitus assessment used, the framework applied a multi-model ARA RAM 2025™ preliminary assessment to the Sameer Verma piece, the Mendocino archive thread, and the broader Microsoft public positioning on Dynamics 365 agentic ERP. Four models produced independent reads. The reads converged on several structural observations and diverged on others. The converged observations form the preliminary read; the divergences indicate where the framework’s analytical confidence is calibrated to actively held uncertainty rather than to settled conclusion.
Converged observation one. The contemporary Microsoft positioning operates in the same structural territory as the 2007 Mendocino ambition. The productivity layer is the abstraction that makes the operational data layer usable. The fusion point is where transformation happens. This convergence is grounded in the explicit architectural decisions Microsoft has documented — MCP Server as the agent-to-ERP pathway, Work IQ as the productivity-to-operational-data signal layer, Copilot as the unified surface that operates across both.
Converged observation two. Microsoft’s broader public material engages the substrate question that the Sameer Verma piece in isolation does not foreground. The Convergence 2025 acknowledgment that “when data is fragmented across systems, agents can’t act with autonomy” is structurally identical to the framework’s substrate inheritance diagnosis. The contemporary Microsoft positioning is not unaware of the precondition. The marketing materials calibrated to different audiences surface the precondition with different levels of emphasis.
Converged observation three. The framework’s nineteen-year archive on the productivity-plus-operational-data ambition produces analytical context that the contemporary procurement-tech discourse has not consistently surfaced. The Mendocino genealogy, the 2007 Dangerous Supply Chain Myths Part 7 finding that “process and not technology is the driving force behind a successful e-procurement initiative,” the 1998 Department of National Defence agent-based Metaprise R&D engagement that produced the framework’s foundational proof case — this body of work has been documenting the substrate-versus-technology question for nineteen years. The contemporary engagement with Microsoft’s positioning operates from analytical context the broader discourse does not yet have.
Diverged observation. The four models diverged on whether the contemporary Microsoft positioning has substantively engaged the multi-wave compounding dimension of the substrate condition the framework names. Microsoft has publicly acknowledged that data fragmentation prevents agentic autonomy. Microsoft has not (in the public material the framework has surfaced) explicitly engaged the recognition that the data fragmentation is itself the residue of four technology generations of unresolved operating decisions — Wave 1 spreadsheets accumulating since approximately 1990, Wave 2 BYOD fragmentation accumulating since approximately 2007, Wave 3 SaaS sprawl accumulating since approximately 2012, and now Wave 4 AI deployment landing on top of the unresolved substrate from the prior three waves.
The diverged observation is where the framework’s preliminary read becomes a substantive inquiry rather than a settled diagnosis. The framework does not know what Microsoft is thinking about the multi-wave dimension. The framework has surfaced the broader public material it could find. That material acknowledges the substrate question at the data-and-process-standardization level. The material does not (so far as the framework has been able to surface) engage the multi-wave compounding dimension explicitly.
What the framework is asking Sameer Verma
The framework’s substantive question, grounded in the preliminary RAM 2025™ multi-model read and presented as inquiry rather than as assertion, is the following.
Microsoft has publicly acknowledged that data fragmentation across systems prevents agents from acting with autonomy. The framework’s archive documents that the data fragmentation typically encountered in 2026 enterprise environments is not the residue of any single technology generation — it is the cumulative residue of four technology generations of unresolved operating decisions, each of which calibrated the underlying operating model to a pre-AI condition. Spreadsheets accumulated local overrides and shadow logic since approximately 1990. BYOD-era systems fragmented identity management and access control since approximately 2007. SaaS sprawl produced disconnected approval paths and decentralized data ownership since approximately 2012. The Wave 4 AI deployment is now landing on top of the cumulative substrate residue from those three prior waves.
How is the Dynamics 365 team thinking about the multi-wave compounding dimension of the substrate fragmentation that Microsoft has already acknowledged? The framework’s diagnostic instrument, Phase 0™, is calibrated to surface the cumulative substrate condition across all four waves before deployment commitment, producing a documented readiness profile that informs whether the technology layer’s capability will produce sustained outcomes or amplify the prior-wave inheritance at machine speed. Where does pre-commitment multi-wave substrate diagnostic work fit alongside the data-and-process standardization Microsoft’s broader public material identifies as prerequisite for agentic autonomy?
The question is not whether Dynamics 365 agentic ERP will produce sustained outcomes. The question is what the pre-commitment work needs to look like for organizations evaluating the architecture to actually realize the outcomes the architecture is capable of producing. The framework’s preliminary read is that the multi-wave compounding dimension is materially significant and that Phase 0™-style substrate diagnostic work operates upstream of the data-and-process standardization Microsoft’s own material identifies. The framework is asking Sameer how Microsoft is thinking about that upstream layer, because Microsoft’s senior leadership in the Dynamics 365 product organization has substantially more visibility into actual deployment patterns across customer organizations than the framework’s archive can produce from external observation alone.
Why this inquiry is structurally significant for the broader procurement-tech discourse
The framework’s body of work has been engaging the substrate question continuously for nineteen years. The recent runway — the Compounding Technology Shadow Wave™ trilogy, the financial impact piece, the Eric Kimberling engagement piece on agile in ERP, the forthcoming Tealbook/Supplier.io merger demonstration piece — operates at multiple analytical layers simultaneously. Structural diagnosis. Financial measurement. Methodology convergence. Operational case demonstration.
The Microsoft Dynamics 365 positioning operates at the highest analytical layer of the contemporary agentic ERP discourse. Microsoft is the largest enterprise software vendor in the world. Dynamics 365 with Copilot, Agent 365, and the MCP Server is the most sophisticated agentic ERP architecture in the market. Sameer Verma’s leadership position in the Dynamics 365 product organization gives him visibility into deployment patterns at a substantially larger scale than is normally recognized and utilized to its full potential. The substantive question the framework is asking him is not rhetorical. It is the kind of question that, if engaged substantively, produces analytical work neither the framework nor Microsoft alone could produce.
The October 2025 IBM/Cognitus piece used the same preliminary RAM 2025™ inquiry construction. The piece engaged the IBM acquisition as a structural question rather than as a settled diagnosis, allowed for the possibility that the acquisition might break the historical pattern, and surfaced the framework’s analytical context as background for the inquiry rather than as oppositional foreground. The contemporary Microsoft engagement follows the same structural template. The framework asks. The engaged party (in this case Microsoft, through Sameer Verma directly if he chooses to engage) responds substantively. The dialogue produces analytical work that survives multi-model scrutiny and the engaged party’s substantive response.
That construction is structurally rare in the contemporary procurement-tech discourse. Most vendor engagement operates either as marketing-aligned positive coverage or as adversarial commentary that the engaged party has no productive reason to engage. The preliminary RAM 2025™ inquiry construction sits between those poles. It engages substantively while inviting refinement. It surfaces preliminary analytical reads while explicitly holding them as preliminary. It positions the framework as engaging from genuine inquiry rather than from asserted analytical priority.
The framework’s analytical posture and what it invites
The framework’s nineteen-year archive on substrate inheritance and operating-model coherence is substantial. The contemporary Compounding Technology Shadow Wave™ vocabulary formalizes analytical positions that have been continuously documented since 2007. The framework’s commercial proposition, Phase 0™ as a pre-commitment substrate diagnostic, is calibrated to exactly the decision point organizations face when evaluating sophisticated technology like Dynamics 365 agentic ERP.
None of that means the framework knows what Microsoft has figured out about agentic ERP deployment that Microsoft has not yet surfaced publicly. The framework has one Sameer Verma marketing piece, the Microsoft broader public material discovered through search, the Mendocino archive thread, and the multi-model preliminary assessment. That is real evidence. It is also bounded evidence. Microsoft’s product organization has visibility into actual customer deployments, observed failure modes, architectural decisions made and not made, and deployment patterns the public material does not surface. The framework genuinely wants to know what Microsoft has figured out that the public positioning has not yet fully surfaced.
If Microsoft has substantively engaged the multi-wave compounding dimension through architectural decisions that the public material does not yet describe, the framework’s preliminary read needs to be refined and the analytical contribution recalibrated. If Microsoft has not yet engaged that dimension, the framework’s preliminary read identifies an opportunity where Phase 0™-style substrate diagnostic work complements the data-and-process standardization Microsoft’s own material identifies as prerequisite. Either outcome produces value. Either outcome advances the substantive analytical work. Either outcome is preferable to publishing a settled diagnosis from incomplete evidence.
The framework’s question to Sameer Verma stands. The framework’s analytical posture is honest about its preliminary status. The framework’s commercial proposition, Phase 0™ as a pre-commitment substrate diagnostic, is positioned as complementary to what Microsoft has publicly identified as the precondition for agentic autonomy rather than as oppositional to Microsoft’s architectural ambition. The framework invites Sameer’s response and the broader Dynamics 365 product organization’s engagement. The dialogue is the work.
The framework’s preliminary RAM 2025™ multi-model assessment of the Microsoft Dynamics 365 agentic ERP positioning is published here as inquiry rather than as settled diagnosis. The framework genuinely does not know what Microsoft has figured out about agentic ERP deployment that the public positioning has not yet surfaced. The substantive question — how the Dynamics 365 team is thinking about the multi-wave compounding dimension of the substrate fragmentation Microsoft has already acknowledged — is asked because the answer matters. Sameer Verma and the broader Microsoft Dynamics 365 product organization are explicitly invited to respond. If the response refines or refutes the framework’s preliminary read, the framework will publish the refinement. The dialogue is structurally more valuable than the unilateral assessment.
From Peesker’s 2018 declaration that companies will either ‘transform or be transformed’ to Sameer’s expanded Microsoft Dynamics 365 offering, where is the company truly heading?
Author note: Jon W. Hansen interviewed Kevin Peesker, then President of Microsoft Canada, on April 4, 2018 at the Activate Digital 2018 event hosted by Long View Systems. That interview is part of the Procurement Insights archive. The archive’s engagement with Microsoft’s product and leadership positioning has been continuous across multiple technology generations. The October 2025 IBM/Cognitus preliminary RAM 2025™ assessment used the same structural template applied here to the contemporary Microsoft Dynamics 365 agentic ERP positioning.
Compounding Technology Shadow Wave™ · Hansen Deflator Formula™ · Hansen Optionality Loss Estimate™ · Phase 0™ · Hansen Fit Score™ (HFS™) · RAM 2025™ · Real-World Condition Substrate™ · Strand Commonality™ · ARA™ · Implementation Physics™
Hansen Models™ · Founder: Jon W. Hansen · hansenprocurement.com
-30-
Share this:
Related