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 #Microsoft365

Why Connected Apps Inside Microsoft 365 Copilot Matter More Than Another AI Feature

#Microsoft365 #Copilot #MicrosoftAI #AI #EnterpriseAI

One of the biggest AI adoption problems is still surprisingly simple: the answer shows up in one place, but the work still has to happen somewhere else. That is why Microsoft’s move to bring business apps directly into Microsoft 365 Copilot deserves more attention. When agents can surface experiences from tools like Dynamics 365, Adobe Express, Figma, Box, or monday.com inside the Copilot flow, the value is not just convenience. It is a shift in operating model. AI becomes more useful when it can stay connected to the systems where teams actually create, update, approve, and execute work. In the article, I explore why this matters for Microsoft AI solutions: • why reducing context switching is becoming a strategic design goal • how in-chat app experiences can narrow the gap between insight and execution • why connectors, agents, and governance now matter together • and what organizations should think about as Copilot becomes a more connected work surface The next phase of enterprise AI may depend less on generating another good answer, and more on whether that answer can move work forward across the tools the business already depends on. How important do you think connected app experiences will be in turning AI from assistance into real execution?

Why Microsoft’s Copilot Redesign Matters More Than It Seems

#Microsoft365 #MicrosoftCopilot #AI #EnterpriseAI #MicrosoftAI #DigitalTransformation

The interface layer of enterprise AI is becoming a strategy decision. Microsoft’s redesign of the Microsoft 365 Copilot app may look, at first glance, like a product UX update. I think it is more significant than that. When Copilot becomes cleaner, faster, and more embedded across Microsoft 365, the real shift is not visual. It is operational. AI moves closer to the flow of work, which changes adoption, trust, and ultimately business value. In the article, I explore why this matters for Microsoft AI solutions: • why user experience is becoming part of enterprise AI architecture • how a more unified Copilot surface can reduce friction between insight and action • why design consistency matters when agents, apps, and workflows start to converge • and what organizations should think about as AI becomes a more persistent layer of daily work The next stage of AI adoption may depend not only on model capability, but on how naturally that capability fits into the way people already work. Do you think enterprise AI adoption will be shaped more by what the model can do, or by how well the experience fits into everyday work?

Why Agentic Copilot Inside Word, Excel, and PowerPoint Is a Bigger Enterprise Shift Than It First Appears

#Microsoft365 #Copilot #MicrosoftAI #AI #EnterpriseAI

Three apps tell you a lot about where enterprise AI is heading: Word, Excel, and PowerPoint. Microsoft making agentic capabilities generally available across these core tools matters because it changes the role of AI from optional assistance around documents to active collaboration inside the document itself. That is a meaningful shift for Microsoft AI solutions. When AI can help restructure a deck, work through spreadsheet logic, or refine a draft directly in the place where the work lives, the value is not just speed. It is reducing the gap between intention and execution while keeping the user in control. In the article, I explore why this matters: • why in-document action is strategically different from chat-based support alone • how app-specific agent behavior can improve usefulness and trust • why Word, Excel, and PowerPoint are important proving grounds for enterprise AI adoption • and what organizations should think about as they scale these capabilities responsibly The next phase of AI at work may depend less on adding another interface, and more on embedding capable action into the tools people already use every day. Do you think the bigger adoption breakthrough will come from better AI conversations, or from AI that can act more effectively inside the applications where work actually gets done?

Why Microsoft’s App-Native AI in Word, Excel, and PowerPoint Matters

#Microsoft365 #Copilot #MicrosoftAI #AI #EnterpriseAI

Word, Excel, and PowerPoint are no longer just places where AI helps you draft faster. They are becoming places where AI can 𝑤𝑜𝑟𝑘 𝑤𝑖𝑡ℎ 𝑦𝑜𝑢 𝑖𝑛𝑠𝑖𝑑𝑒 𝑡ℎ𝑒 𝑑𝑜𝑐𝑢𝑚𝑒𝑛𝑡 𝑖𝑡𝑠𝑒𝑙𝑓. That shift matters more than it may first appear. What stands out in Microsoft’s rollout of agentic capabilities across its core productivity apps is the move from generic assistance toward application-native execution: restructuring content in Word, analyzing and reasoning over data in Excel, and building presentations in PowerPoint with deeper in-app context. To me, this is one of the clearest signals yet of where Microsoft’s AI strategy is heading. The value is not only in having Copilot available across Microsoft 365. It is in embedding specialized AI behavior directly into the environments where work is already being done. In the article, I explore why that matters strategically—and why the next enterprise advantage may come from AI that understands the grammar of each application, not just the user’s prompt. Which will create more value in practice: one general assistant everywhere, or app-specific AI that can operate natively inside the tools people already trust?

Why Microsoft Scout Could Shift Enterprise AI From Prompted Help to Persistent Support

#Microsoft365 #Copilot #AI #EnterpriseAI #Microsoft

An always-on agent is a different proposition from an on-demand assistant. What caught my attention in Microsoft’s latest Copilot direction is the move toward a personal agent that stays connected to the user’s flow of work across Microsoft 365, rather than waiting for the next prompt. That is strategically important because the value of AI often disappears in the gaps between moments of interaction. In the article, I explore why Microsoft Scout points to a new design pattern in enterprise AI: less episodic chat, more persistent support; less isolated output, more continuity across tasks, context, and decisions. If this model matures, the advantage may not come only from better responses. It may come from reducing the amount of work people have to remember, re-open, and manually restart. Do you think the bigger opportunity is smarter assistants, or AI that can stay productively present between interactions?