Blog

Maximilian Kenfenheuer

Manager @ BearingPoint

Maximilian Kenfenheuer

Featured

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

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?

Continue reading

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

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?

From AI Adoption to Work Transformation: Why Microsoft 365 Copilot’s Next Signal Matters

30 million paid seats is an adoption milestone. But the more interesting signal is what Microsoft says comes next: measuring AI by 𝑤𝑜𝑟𝑘 𝑡𝑟𝑎𝑛𝑠𝑓𝑜𝑟𝑚𝑒𝑑, not just licenses deployed. What stood out to me is how clearly the conversation is moving beyond simple productivity math. Microsoft is describing a shift from AI as a tool people occasionally use to AI as an active participant in workflows—handling multi-step work, supporting role-specific execution, and helping small expert teams move faster than traditional operating models allowed. A few details are especially notable: • Microsoft says Microsoft 365 Copilot has surpassed 30 million paid seats, with net seat adds more than doubling quarter over quarter • average weekly engagement is now on par with Outlook and Teams • the number of customers with more than 50,000 seats has increased more than 7x year over year To me, that reframes the strategic question. The issue is no longer only whether AI can save minutes on drafting or summarizing. It is whether organizations can redesign work so humans set direction, agents execute within boundaries, and value is measured at workflow and operating-model level. In the article, I unpack why this matters for Microsoft’s AI position—and why the next competitive advantage may come from transforming how work gets done, not merely accelerating the old way of doing it. What do you think will matter more over the next 12 months: AI adoption at scale, or evidence that work itself is being fundamentally redesigned?

Latest posts

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?