Blog

Maximilian Kenfenheuer

Manager @ BearingPoint

Maximilian Kenfenheuer

Featured

Why Copilot Cowork Signals a More Operational Future for Microsoft AI Solutions

30 million paid seats is a notable number. But I do not think it is the most interesting Microsoft 365 Copilot signal right now. What stands out more is Microsoft’s push around 𝐂𝐨𝐩𝐢𝐥𝐨𝐭 𝐂𝐨𝐰𝐨𝐫𝐤 and the idea of AI as an execution layer for longer-running, multi-step work. That matters for Microsoft AI solutions because enterprise value rarely comes from a single good answer. It comes from whether AI can help coordinate tasks, respond to events, work across tools, and keep people in control while work actually moves. In the article, I explore why this shift deserves attention: • why Cowork changes the conversation from chat assistance to managed execution • how event-driven tasks, skills, plugins, and browser use point to a more operational AI model • why governance, billing, and admin controls become more important as AI takes on longer-running work • and what organizations should consider as they move from experimenting with copilots to scaling agentic work responsibly The next phase of enterprise AI may depend less on how well AI answers, and more on how reliably it can carry work forward across time, systems, and approvals. Do you think execution layers like Copilot Cowork will become the real measure of enterprise AI maturity?

Continue reading

Why Legal Work Is Becoming an Important Proving Ground for Microsoft 365 Copilot

Legal work is a good test of whether enterprise AI is becoming genuinely useful. Not because it is flashy. Because it is high-stakes, document-heavy, time-sensitive, and full of context that has to be handled carefully. What caught my attention is Microsoft’s growing emphasis on legal workflows in Microsoft 365 Copilot, including partner agent experiences that help bring legal tasks into the flow of everyday work rather than forcing people to jump between disconnected systems. For Microsoft AI solutions, that matters. When AI can help legal teams review contracts faster, surface relevant information, support audit preparation, and reduce repetitive manual work inside the tools people already use, the value is not just productivity. It is operational fit. In the article, I explore why this is strategically important: • why legal work is an important proving ground for enterprise AI • how embedded legal agents point to a more workflow-centric Copilot model • why permissions, accuracy, and human oversight matter even more in this domain • and what organizations should consider as they bring AI into regulated, high-consequence work The next phase of enterprise AI may be shaped less by broad generic capability, and more by whether AI can support specialized work responsibly inside real business processes. Do you think legal and compliance functions will become one of the clearest indicators of whether enterprise AI is truly enterprise-ready?

Why Copilot Notebooks’ support for Markdown and text files matters more than it seems

Markdown may sound like a small file-format update. I do not think it is. Microsoft’s move to let Copilot Notebooks work with 𝐌𝐚𝐫𝐤𝐝𝐨𝐰𝐧, 𝐩𝐥𝐚𝐢𝐧-𝐭𝐞𝐱𝐭, 𝐚𝐧𝐝 𝐫𝐢𝐜𝐡-𝐭𝐞𝐱𝐭 𝐟𝐢𝐥𝐞𝐬 points to something more important for Microsoft AI solutions: enterprise AI is becoming more useful when it can reason over the 𝑎𝑐𝑡𝑢𝑎𝑙 𝑤𝑜𝑟𝑘𝑖𝑛𝑔 𝑚𝑎𝑡𝑒𝑟𝑖𝑎𝑙𝑠 teams rely on every day. That includes READMEs, wikis, logs, transcripts, notes, and operational text that often sits outside polished documents and slide decks. In the article, I explore why that matters: • why unstructured working content is often where real context lives • how broader file support can make Copilot Notebooks more relevant for technical, operational, and cross-functional teams • why this improves continuity between knowledge capture and AI-assisted reasoning • and what organizations should think about as they expand the range of content they want AI to work with responsibly The next phase of enterprise AI may depend not only on better models, but on whether those models can work effectively with the formats people already use to run the business. Which overlooked content types do you think will create the most value once AI can use them more naturally?

Posts tagged #Copilot

Why Copilot Cowork Signals a More Operational Future for Microsoft AI Solutions

#Microsoft365Copilot #MicrosoftAI #Copilot #AI #EnterpriseAI

30 million paid seats is a notable number. But I do not think it is the most interesting Microsoft 365 Copilot signal right now. What stands out more is Microsoft’s push around 𝐂𝐨𝐩𝐢𝐥𝐨𝐭 𝐂𝐨𝐰𝐨𝐫𝐤 and the idea of AI as an execution layer for longer-running, multi-step work. That matters for Microsoft AI solutions because enterprise value rarely comes from a single good answer. It comes from whether AI can help coordinate tasks, respond to events, work across tools, and keep people in control while work actually moves. In the article, I explore why this shift deserves attention: • why Cowork changes the conversation from chat assistance to managed execution • how event-driven tasks, skills, plugins, and browser use point to a more operational AI model • why governance, billing, and admin controls become more important as AI takes on longer-running work • and what organizations should consider as they move from experimenting with copilots to scaling agentic work responsibly The next phase of enterprise AI may depend less on how well AI answers, and more on how reliably it can carry work forward across time, systems, and approvals. Do you think execution layers like Copilot Cowork will become the real measure of enterprise AI maturity?

Why Copilot Notebooks’ support for Markdown and text files matters more than it seems

#Microsoft365Copilot #MicrosoftAI #AI #Copilot #EnterpriseAI

Markdown may sound like a small file-format update. I do not think it is. Microsoft’s move to let Copilot Notebooks work with 𝐌𝐚𝐫𝐤𝐝𝐨𝐰𝐧, 𝐩𝐥𝐚𝐢𝐧-𝐭𝐞𝐱𝐭, 𝐚𝐧𝐝 𝐫𝐢𝐜𝐡-𝐭𝐞𝐱𝐭 𝐟𝐢𝐥𝐞𝐬 points to something more important for Microsoft AI solutions: enterprise AI is becoming more useful when it can reason over the 𝑎𝑐𝑡𝑢𝑎𝑙 𝑤𝑜𝑟𝑘𝑖𝑛𝑔 𝑚𝑎𝑡𝑒𝑟𝑖𝑎𝑙𝑠 teams rely on every day. That includes READMEs, wikis, logs, transcripts, notes, and operational text that often sits outside polished documents and slide decks. In the article, I explore why that matters: • why unstructured working content is often where real context lives • how broader file support can make Copilot Notebooks more relevant for technical, operational, and cross-functional teams • why this improves continuity between knowledge capture and AI-assisted reasoning • and what organizations should think about as they expand the range of content they want AI to work with responsibly The next phase of enterprise AI may depend not only on better models, but on whether those models can work effectively with the formats people already use to run the business. Which overlooked content types do you think will create the most value once AI can use them more naturally?

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 Source Control Will Matter More in Microsoft 365 Copilot Than Many Teams Realize

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

Trust in enterprise AI is not only about what the model can do. It is also about what the organization can control. That is why Microsoft’s work on domain exclusion for Microsoft 365 Copilot caught my attention. Even with the recent rollback of the feature as originally announced, the direction is strategically important: giving admins more control over which external web domains can influence Copilot responses. For Microsoft AI solutions, that matters because grounded AI is only useful at scale if it is also governable at scale. In the article, I look at why this issue deserves more attention: • why web grounding controls are becoming part of the enterprise trust model • how domain-level policy can shape quality, compliance, and risk • why this is bigger than one feature release or rollback • and what it says about the next phase of governed AI adoption in Microsoft 365 The future of enterprise AI will not be defined by capability alone. It will also be defined by how precisely organizations can shape the information boundaries around that capability. How important do you think source-level control will become as companies scale AI across 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?