Blog

Maximilian Kenfenheuer

Manager @ BearingPoint

Maximilian Kenfenheuer

Featured

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?

Continue reading

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?

Why Model Choice in Microsoft 365 Copilot Could Become a Strategic Enterprise Advantage

Model choice inside Microsoft 365 Copilot may become a bigger enterprise differentiator than many people expect. What caught my attention is not just that Microsoft is expanding available models in Copilot environments. It is the operating implication: organizations are moving toward an AI layer where different models can be matched to different kinds of work, with admin controls, visibility, and clear data-handling boundaries. That matters because enterprise AI is no longer one simple question of “do we have a model?” It is increasingly a question of 𝑤ℎ𝑖𝑐ℎ 𝑚𝑜𝑑𝑒𝑙 𝑠ℎ𝑜𝑢𝑙𝑑 ℎ𝑎𝑛𝑑𝑙𝑒 𝑤ℎ𝑖𝑐ℎ 𝑡𝑎𝑠𝑘, 𝑢𝑛𝑑𝑒𝑟 𝑤ℎ𝑖𝑐ℎ 𝑔𝑜𝑣𝑒𝑟𝑛𝑎𝑛𝑐𝑒 𝑐𝑜𝑛𝑑𝑖𝑡𝑖𝑜𝑛𝑠, 𝑎𝑛𝑑 𝑤𝑖𝑡ℎ 𝑤ℎ𝑎𝑡 𝑡𝑟𝑎𝑑𝑒-𝑜𝑓𝑓 𝑏𝑒𝑡𝑤𝑒𝑒𝑛 𝑠𝑝𝑒𝑒𝑑, 𝑑𝑒𝑝𝑡ℎ, 𝑎𝑛𝑑 𝑟𝑒𝑡𝑒𝑛𝑡𝑖𝑜𝑛 𝑝𝑜𝑠𝑡𝑢𝑟𝑒? In the article, I explore why this shift matters for Microsoft AI solutions: • why model choice is becoming an architectural decision, not just a product feature • how Copilot environments are starting to separate fast everyday work from deeper reasoning work • why admin controls and data-retention signals matter just as much as model quality • and how this could shape the next phase of trusted enterprise AI adoption The next advantage may not come from one model winning outright. It may come from giving organizations a governed way to use the right model for the right job. Do you think enterprise AI will be shaped more by having the best single model, or by orchestrating multiple models well?

Latest posts

Why Copilot Tuning Could Become a Strategic Advantage in Enterprise AI

#Microsoft365Copilot #MicrosoftAI #CopilotStudio #EnterpriseAI #AITransformation

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?