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

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

#Microsoft365Copilot #MicrosoftAI #Copilot #AIGovernance #EnterpriseAI

Up to 1,000 excluded domains is a small product detail with a much bigger strategic message. Microsoft’s Domain Exclusion capability for Copilot puts a sharper point on something many organizations are now realizing: enterprise AI value is not only about what the system can access, but also about what it should 𝑛𝑜𝑡 use. That matters because once AI starts grounding responses in the web alongside internal context, relevance and trust become governance questions as much as technical ones. Source quality, citation boundaries, and admin control all start to shape the user experience. In the article, I explore why this matters for Microsoft AI solutions: • why web grounding control is becoming part of enterprise AI architecture • how domain exclusion changes the balance between openness and trust • why admin policy decisions increasingly influence output quality • and what organizations should consider as Copilot becomes more embedded in knowledge work For me, this is a useful reminder that better AI is not just about adding more context. It is also about applying the right boundaries with intention. How important do you think source control will become in building trust in Microsoft AI solutions?

Why Agent Evaluation May Become a Defining Capability in Microsoft AI Solutions

#MicrosoftAI #Microsoft365Copilot #CopilotStudio #AIGovernance #AgenticAI

Evaluation is starting to look like one of the most important enterprise AI capabilities that people still underestimate. What caught my attention is Microsoft’s growing emphasis on agent evals in Copilot Studio, including custom graders and the data science behind how agent quality is measured and improved. For Microsoft AI solutions, that matters because the next phase of value will not come from simply deploying more agents. It will come from knowing which ones are reliable, where they fail, how they should be governed, and how quality can be improved systematically rather than anecdotally. In the article, I explore why this deserves more attention: • why agent evaluation is becoming a strategic layer, not just a technical checkpoint • how custom graders help organizations measure quality against business-specific standards • why reliability, governance, and continuous improvement are inseparable in enterprise AI • and what organizations should consider as they move from pilot agents to production-scale agent ecosystems The next phase of enterprise AI may depend not only on what agents can do, but on whether organizations can evaluate them with enough rigor to trust them in real work. How important do you think agent evaluation will become as enterprises scale Microsoft AI solutions?

Why Domain Exclusion Matters More Than It Seems in Microsoft 365 Copilot

#Microsoft365Copilot #MicrosoftAI #Copilot #AIGovernance #ResponsibleAI

Up to 1,000 domains can now be excluded from web grounding in Microsoft 365 Copilot. I think that is more important than it may first appear. For Microsoft AI solutions, this is not just a settings update. It is a signal that 𝑔𝑟𝑜𝑢𝑛𝑑𝑖𝑛𝑔 𝑐𝑜𝑛𝑡𝑟𝑜𝑙 is becoming part of enterprise AI architecture. As Copilot becomes more capable, organizations will need sharper ways to shape what external sources it can and cannot rely on. In the article, I explore why this matters: • why domain exclusion changes the governance conversation from broad trust to source-level control • how web grounding policies affect accuracy, risk, and organizational confidence • why admin tooling now matters just as much as model capability in enterprise AI adoption • and what organizations should consider as they operationalize Copilot more seriously The next phase of enterprise AI may depend not only on what AI can access, but on how deliberately organizations can define the boundaries around that access. How important do you think source-level controls like domain exclusion will become as enterprises scale AI use?

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 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?