Blog

Maximilian Kenfenheuer

Manager @ BearingPoint

Maximilian Kenfenheuer

Featured

Why Human Agency May Be the Most Important Microsoft AI Story Right Now

66% of AI users surveyed by Microsoft say AI is helping them spend more time on higher-value work. That number matters because it shifts the enterprise AI conversation away from simple productivity gains and toward something more strategic: human agency. Microsoft’s recent framing around Microsoft 365 Copilot highlights a point I think many organizations are only starting to absorb. As AI takes on more execution, the differentiator is not just automation. It is whether people are equipped to direct, evaluate, and improve that work with better judgment. In the article, I explore why this matters for Microsoft AI solutions: • why agency may become a more useful leadership lens than efficiency alone • how Copilot changes the shape of knowledge work when more people can do higher-value tasks • why management systems and culture may matter more than individual prompting skill • and what organizations should do now to turn AI capability into durable business value The next phase of AI adoption may reward the companies that redesign work around human judgment, not just machine output. How are you thinking about this in your organization: is the bigger opportunity cost reduction, or expanding what your people can actually take ownership of?

Continue reading

Why Copilot Tuning Could Become a Strategic Advantage in Enterprise AI

One of the more important Microsoft AI signals this year is not another model release. It is the move toward 𝑡𝑢𝑛𝑖𝑛𝑔 AI around how a specific organization actually works. Microsoft’s announcement of Microsoft 365 Copilot Tuning and multi-agent orchestration points to a meaningful shift for enterprise AI. The question is no longer only whether AI can help with generic tasks. It is whether organizations can shape agents around their own language, processes, compliance boundaries, and domain expertise—without turning every project into a custom AI engineering effort. That matters because scalable value rarely comes from generic capability alone. It comes from making AI behave in ways that fit the business. In the article, I explore why this is strategically important for Microsoft AI solutions: • why tuning may become a practical bridge between foundation models and real enterprise workflows • how low-code customization changes the adoption equation • why multi-agent orchestration matters when work crosses functions, not just prompts • and why the next differentiator may be organizational fit, not just raw model power If enterprise AI is going to create durable value, it needs to reflect how the organization operates—not just what the model can do in general. Do you think the bigger long-term advantage will come from stronger general models, or from AI that can be tuned to the way each business actually works?

Why Microsoft 365 Copilot’s New Design Matters More Than It First Appears

Interface decisions do more strategic work than they get credit for. Microsoft’s redesign of Microsoft 365 Copilot points to something important: enterprise AI adoption is not only about model quality or new agent features. It is also about whether the experience reduces friction enough to become part of everyday work. A cleaner, faster Copilot that sits more naturally inside Microsoft 365 may sound like a product refinement. I think it is better understood as an adoption lever. In the article, I explore why UX and workflow design matter so much for Microsoft AI solutions: • why lower interaction friction can have outsized impact on usage • how in-flow AI experiences change the threshold for everyday adoption • why design consistency supports trust, governance, and scale • and why the next enterprise advantage may come from making AI easier to return to, not just more powerful If AI is going to become part of normal work, the experience has to feel native to work itself. What do you think matters more for enterprise AI adoption now: stronger capabilities, or better integration into the daily flow of work?

Posts tagged #Copilot

Why Domain Exclusion Matters More Than It First Appears in Microsoft 365 Copilot

#Microsoft365Copilot #MicrosoftAI #AIGovernance #EnterpriseAI #Copilot #ResponsibleAI

Up to 1,000 domains can now be excluded from Microsoft 365 Copilot web grounding. That may sound like a small admin setting. I think it is a meaningful signal about where enterprise AI is going. As Copilot becomes more embedded in day-to-day work, the strategic issue is not only how much context AI can access. It is how precisely organizations can shape 𝑤ℎ𝑖𝑐ℎ 𝑒𝑥𝑡𝑒𝑟𝑛𝑎𝑙 𝑐𝑜𝑛𝑡𝑒𝑥𝑡 is allowed to influence responses. What stands out here is the governance implication. Domain exclusion gives admins a way to reduce unwanted or low-trust web sources in grounded answers, which matters for reliability, compliance, and confidence at scale. It also reinforces a broader point: enterprise AI adoption depends not just on capability, but on controllability. In the article, I explore why this kind of policy control matters for Microsoft AI solutions—and why the next differentiator may be the ability to tune AI systems with more precision, not simply make them more powerful. Will enterprise trust in AI be driven more by broader access to information, or by tighter control over what the system is allowed to use?

Why Work IQ Could Become One of Microsoft’s Most Strategic AI Advantages

#Microsoft365Copilot #MicrosoftAI #Copilot #AI #EnterpriseAI #CopilotStudio

June 2 may turn out to be one of the more important dates in Microsoft’s enterprise AI roadmap. That is when Microsoft introduced Work IQ APIs—opening up the intelligence layer behind Microsoft 365 Copilot so agents and applications can reason over work context, not just retrieve isolated data. What stands out to me is the architectural implication. If Work IQ becomes the shared context layer across Microsoft 365, then the competitive advantage is no longer only the assistant interface. It is the ability to give agents secure, permission-aware understanding of how work actually happens across files, meetings, chats, mail, sites, and business systems. In the article, I explore why that matters strategically for Microsoft AI solutions: • Work IQ as infrastructure, not just a feature • why semantic context may matter more than another model upgrade • how governance and user-scoped access shape enterprise trust • why this could accelerate a new generation of Microsoft-based agents The next phase of enterprise AI may be defined less by who has a chatbot—and more by who has the best intelligence layer behind it. Do you think the bigger differentiator will be better models, or better organizational context?

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?

Why In-Chat Apps Could Be One of Microsoft 365 Copilot’s Most Practical AI Advantages

#Microsoft365Copilot #MicrosoftAI #AI #Copilot #EnterpriseAI

Every extra tab in a workflow is a small tax on execution. That is why Microsoft’s move to bring business apps directly into Microsoft 365 Copilot feels more strategic than it may first appear. When tools like Adobe Express, Figma, Miro, monday.com, Box, Optimizely, and Dynamics 365 can surface inside the Copilot conversation, AI stops being just a place to ask questions. It starts becoming a place where work actually gets completed. What stands out to me is the operating model behind this. Instead of generating insight in one window and taking action in another, Microsoft is narrowing the gap between intent and execution. That matters because a lot of enterprise friction is not caused by lack of intelligence. It is caused by context switching, fragmented interfaces, and the repeated effort of re-establishing where the work stands. In the article, I unpack why this in-chat app model could be an important next step for Microsoft’s AI strategy—and why reducing workflow fragmentation may become one of the most practical advantages in enterprise AI. If AI can bring more of your tool stack into one conversational layer, which matters more: better answers, or fewer handoffs?