Microsoft’s 2026 Work Trend Index, published in May and drawing on a survey of 20,000 AI-using knowledge workers across 10 markets and anonymized Microsoft 365 productivity signals, shows a widening gap between what employees can now do with AI and what their organizations are structured to support. Its core finding is that AI capability is advancing at the employee level, while operating models, management practices, and business systems are lagging behind.
For ERP and business application leaders, that gap lands inside everyday execution. AI can help employees generate analysis, recommendations, drafts, and decisions faster, but value slows when the next step requires re-entering context into ERP screens, reconciling spreadsheets, chasing approvals, or moving work manually between collaboration tools and systems of record.
Microsoft is using that gap to make the case for Dynamics 365 and Copilot Cowork as the connective layer between AI-generated insight and operational action.
Employees Are Advancing Faster Than Operating Models
Per the survey, 49% of Microsoft 365 Copilot conversations support cognitive work, including analysis, problem-solving, evaluation, and creative thinking. Another 19% involve working with people, 17% involve producing work, and 15% involve finding information.
The report also found 58% of AI users say they are producing work they could not have produced a year ago, rising to 80% among Frontier Professionals, Microsoft’s most advanced group of AI users. These workers use agents for multi-step workflows, build multi-agent systems, rethink workflows, and participate in structured AI practices.
Most organizations have not matched that individual progress with operating model change. Only 19% of AI users fall into Microsoft’s “Frontier” zone, where individual capability and organizational readiness reinforce each other. Ten percent are in “blocked agency,” where individuals have strong AI skills but lack organizational support, and 50% remain in the “emergent” zone, where both individual practice and organizational conditions are still forming.
The result is a workforce learning to move faster than the systems around it.
From AI Adoption to AI Absorption
A strong commercial finding is that AI impact is driven more by organizational environment than individual behavior.
Microsoft found organizational factors such as culture, manager support, and talent practices account for 67% of reported AI impact, compared with 32% for individual mindset and behavior. The strongest single factor was organizational AI culture, followed by talent practices and manager support.
Leadership alignment remains weak. Only 26% of AI users say their leadership is clearly and consistently aligned on AI. Sixty-five percent fear falling behind if they do not adapt quickly, while 45% say it feels safer to focus on current goals than to redesign work with AI. Only 13% say they are rewarded for reinventing work with AI when results are not immediate.
The organizations pulling ahead are deploying tools, redesigning workflows, capturing what they learn, and turning those lessons into repeatable practices. The report describes these organizations as “Learning Systems,” where work continuously produces insight, and insight continuously reshapes how work gets done. Active agents in the Microsoft 365 ecosystem have grown 15x year over year, and 18x in large enterprises, increasing the need for governance, repeatable operating models, and evaluation infrastructure.
As agents become part of workflows, organizations need clear answers to who reviews agent performance, who can update agent workflows, and how local improvements are captured and scaled. Microsoft describes this institutional learning as “Owned Intelligence,” the know-how that compounds over time and becomes difficult for competitors to replicate.
For ERP teams, agentic workflows cannot sit outside the systems that manage finance, procurement, supply chain, HR, and compliance. They need operational data, governed permissions, business rules, and audit trails.
Get Our Free Weekly Newsletter
The Execution Gap Becomes the ERP Opportunity
Dynamics 365 sits in the part of the enterprise where AI output must become business action. Sales forecasts, supplier evaluations, service cases, invoices, orders, inventory decisions, and financial approvals all depend on systems that hold structured data and enforce process controls.
The Dynamics 365 ERP apps plugin for Copilot Cowork, now generally available, brings ERP business data, workflows, and operational context into Microsoft 365 Copilot. The goal is to let employees investigate issues, coordinate decisions, and execute operational workflows through natural language while keeping ERP processes and controls at the center of execution.
The next AI productivity frontier is moving from faster individual output to governed operational follow-through.
Sponsor Industry‑Grade Research
What This Means for ERP Insiders
AI value depends on operating model redesign. For CIOs, CFOs, and transformation leaders, the Work Trend Index makes clear that employee-level AI adoption will not automatically translate into enterprise performance. The next phase of ROI will come from redesigning workflows, incentives, management practices, and business systems around how humans and agents actually execute work.
ERP platforms must connect intelligence to action. For ERP product leaders, enterprise architects, and program owners, the report strengthens the case for systems that can carry context from analysis into governed execution. Platforms will be evaluated on how well they connect ERP data, approvals, permissions, collaboration, and transaction workflows without forcing users back into manual coordination.
Agent governance is part of core business architecture. For IT, risk, and security teams, agent growth creates a new control problem. Organizations will need to manage agents as operational actors with identities, permissions, review processes, lifecycle controls, and audit trails, especially when agents interact with finance, procurement, supply chain, HR, and customer workflows.
