Blog

Maximilian Kenfenheuer

Manager @ BearingPoint

Maximilian Kenfenheuer

Featured

Why Microsoft’s New Focus on Measuring Completed Work Matters for Enterprise AI

Most AI dashboards still tell you what happened in the tool, not what happened in the work. That is why Microsoft’s latest shift around Copilot Cowork measurement stands out to me. The conversation is moving beyond prompts, clicks, and activity counts toward something more useful: whether AI is actually helping people complete meaningful work and return time to the business. For organizations investing in Microsoft AI solutions, that matters. If value is measured only by interaction volume, it is easy to confuse usage with impact. But when Microsoft starts framing measurement around assisted hours, completed work, and business process outcomes, it signals a more mature model for enterprise AI adoption. In the article, I explore: • why this change in measurement is strategically important for Microsoft AI solutions • what it says about the shift from AI engagement metrics to work outcome metrics • why baseline process measurement and role-based use cases matter more than generic adoption reporting • and how organizations can think more clearly about ROI as Copilot and agents become part of operational work For me, this is one of the more important signs that Microsoft AI solutions are being positioned not just as tools people use, but as capabilities businesses need to evaluate against real work transformation. How do you think organizations should measure AI success: by usage, by time returned, or by completed business outcomes?

Continue reading

Why Power BI Grounding Could Be a Bigger Microsoft AI Shift Than It First Appears

Power BI is becoming a more important part of the Microsoft AI story. One of the more interesting recent updates is that Microsoft 365 Copilot can now reason over Power BI reports and semantic models in Chat and Cowork. For me, that matters because it moves Microsoft AI solutions closer to a question many leaders actually care about: can AI work with governed business metrics, not just documents and conversations? That is a meaningful step. When AI can answer in natural language against enterprise data models people already trust, the conversation shifts from generic productivity to decision support grounded in the business’s own definitions, permissions, and reporting structure. In the article, I explore: • why Power BI grounding changes the strategic value of Microsoft AI solutions • how semantic models help create more reliable AI answers than disconnected data access • why governed metrics may become a key layer in enterprise AI adoption • and what organizations should consider as Copilot moves closer to analytics and operational decision-making For me, this is another sign that Microsoft is building AI not only around content creation, but around enterprise understanding. How important do you think governed analytics context will become in making Microsoft AI solutions truly useful at scale?

Why Work IQ Could Become a Foundational Layer in Microsoft AI Solutions (1)

June 16 is a notable date in Microsoft AI solutions, not because of another chat feature, but because Work IQ APIs are becoming generally available beyond Microsoft 365 Copilot licensing. For me, that signals something bigger: Microsoft is starting to define enterprise AI around a shared intelligence layer for agents, apps, and workflows, not only around one assistant experience. That matters because once AI can reason over chat, files, meetings, people, and actions through a governed, permission-aware layer, the conversation changes. It becomes less about isolated copilots and more about how organizations build reliable AI systems on top of their actual work graph. In the article, I explore: • why Work IQ represents a deeper architectural move in Microsoft AI solutions • how APIs, A2A support, and a compact tool model point toward more scalable agent design • why governance and cost controls are becoming part of the platform story, not an afterthought • and what organizations should consider as Microsoft expands AI from product feature to enterprise intelligence layer I think this is one of the clearest signs yet that Microsoft AI solutions are evolving into infrastructure for how work gets understood and executed. How important do you think a shared intelligence layer like Work IQ will become in enterprise AI strategy?

Posts tagged #Microsoft365Copilot

Why Human Agency May Become Microsoft’s Most Important Enterprise AI Advantage

#Microsoft365Copilot #MicrosoftAI #EnterpriseAI #AITransformation #FutureOfWork

20,000 workers across 10 countries. Trillions of anonymized Microsoft 365 productivity signals. And one message stands out: the enterprise AI conversation is shifting from productivity gains alone to ℎ𝑢𝑚𝑎𝑛 𝑎𝑔𝑒𝑛𝑐𝑦. What I find most interesting in Microsoft’s latest framing is that Copilot is no longer positioned simply as a tool for faster output. It is being positioned as infrastructure for redesigning how work is assigned, executed, and governed across people and agents. That changes the strategic question. The issue is not only whether AI helps an individual draft, summarize, or analyze faster. It is whether organizations can build an operating model where employees direct more work at a higher level, while agents handle more execution inside clear boundaries. Microsoft’s own data points make that tension visible: • 49% of Copilot conversations support cognitive work • 58% of AI users say they are producing work they could not have a year ago • organizational factors account for more than 2x the reported AI impact of individual factors To me, that last point is the most important. It suggests the next advantage in enterprise AI may not come from giving employees access to better models alone. It may come from leadership, governance, culture, and workflow design that let people use those systems with confidence and clarity. In the article, I unpack why Microsoft’s emphasis on human agency matters strategically for Microsoft 365 Copilot—and why the harder challenge ahead may be organizational redesign, not model performance. If AI increases human agency, what does your organization need to change first: tools, governance, or the way work itself is structured?

Why Microsoft’s Copilot Redesign Matters More Than It First Appears

#Microsoft365Copilot #MicrosoftAI #EnterpriseAI #Copilot #DigitalWorkplace

Microsoft’s latest Copilot move is not just about aesthetics. The redesigned Microsoft 365 Copilot experience points to something more strategic: enterprise AI is being shaped not only by model capability, but by interface discipline. Faster load times, more structured responses, and progressive disclosure may sound like product design details. In practice, they determine whether AI fits naturally into real work or adds another layer of friction. In the article, I look at why this matters: how UI choices influence trust, adoption, and execution inside Microsoft 365—and why the next competitive advantage in AI may come from making powerful systems feel simpler, clearer, and more controllable. Could interface design become one of the most underrated differentiators in enterprise AI?

Why Microsoft’s Work IQ APIs Could Become a Foundational Layer for Enterprise Agents

#Microsoft365Copilot #MicrosoftAI #AI #EnterpriseAI #CopilotStudio

Microsoft is making a deeper platform move than “better Copilot answers.” With the new Work IQ APIs, it is exposing the intelligence layer behind Microsoft 365 so agents can work with business context, use tools, and operate inside governed digital workspaces. That changes the enterprise AI conversation. The question is no longer just whether a model can generate a strong response. It is whether developers and organizations can give agents a secure, scalable way to understand how work actually happens across email, meetings, files, chats, people, and business systems. What stands out to me is the architecture: • Chat and Context APIs for grounded understanding • Tool APIs for action across Microsoft 365 • Workspaces for memory, intermediate state, and longer-running execution • consumption-based pricing via Copilot Credits This looks like Microsoft productizing an operating layer for agentic work. If that layer matures, the strategic advantage may not be the assistant UI alone. It may be the infrastructure that lets many different agents act with context, speed, governance, and cost controls inside the enterprise boundary. I unpack what this means for builders, IT leaders, and the next phase of AI deployment in the article. Do you think the bigger enterprise opportunity is building smarter agents, or building the runtime they can safely work inside?

Why Work IQ Could Become One of Microsoft’s Most Important AI Layers

#Microsoft365Copilot #MicrosoftAI #CopilotStudio #EnterpriseAI #AITransformation

Microsoft is starting to expose something enterprise AI has been missing: a system-level understanding of how work actually moves. The Work IQ APIs are interesting not because they add another model or another chat surface, but because they turn Microsoft 365 activity into an intelligence layer developers and partners can build on. Add the new consumption model through Copilot Credits, plus Copilot Studio extensibility, and this starts to look like infrastructure for a new class of work-aware agents. That changes the conversation. Instead of asking whether an AI can answer well, enterprises can start asking whether it understands: • who is involved • what artifacts matter • where decisions stall • which actions and tools should be invoked next In the article, I unpack why this matters strategically for Microsoft’s AI position: from grounded retrieval to workflow intelligence, from standalone assistants to agents that can reason over the operating patterns of the organization itself. If this layer matures, the real moat may not just be models, apps, or agents. It may be owning the intelligence fabric that tells those systems how work gets done. What do you think becomes more valuable in enterprise AI: better model output, or better understanding of organizational work patterns?

Why Copilot Notebooks May Become One of Microsoft’s Most Important Enterprise AI Moves

#Microsoft365Copilot #CopilotNotebooks #AI #EnterpriseAI #MicrosoftAI

Most enterprise AI still has a context problem. The useful information is scattered across decks, meeting notes, spreadsheets, chats, whiteboards, and half-finished drafts. So even when the model is strong, the work often starts with rebuilding the project context from scratch. That is why Microsoft’s push around Copilot Notebooks is more strategically important than it may first appear. Notebooks create a bounded workspace where Copilot reasons over selected project materials rather than the entire enterprise by default. Microsoft says users can bring together files, Pages, links, and other references, keep them current as the project evolves, and get responses grounded only in that curated set. It is also expanding access: Copilot Notebooks is now available to Copilot Chat licensed users, not just the full Microsoft 365 Copilot audience. The interesting part is not just better summarization. It is the operating model behind it: scoped context, persistent project memory, and tighter grounding around the actual artifacts of work. Add newer capabilities like audio overviews and Capture for in-person conversations and whiteboard sessions, and Microsoft starts turning messy project context into something AI can actually work with. In the article, I unpack why this matters for enterprise AI adoption, governance, and execution—and why the next competitive layer may be not just models or agents, but the systems that package context into usable workspaces. Do you think enterprise AI will create more value from better reasoning, or from better context architecture?