Blog

Maximilian Kenfenheuer

Manager @ BearingPoint

Featured

#Microsoft365Copilot #MicrosoftAI #Copilot #AITransformation #FutureOfWork

Measuring Completed Work: Baselines, Assisted Hours and Business Outcomes

Thursday, September 10, 2026 · Maximilian Kenfenheuer

A team can generate thousands of prompts without improving a single core process. Another uses AI rarely but saves hours in contract review. Microsoft increasingly measures Copilot value by completed work and assisted hours instead of activity. Its internal guidance recommends baselines for painful processes before the rollout. In this article, I describe a three-layer measurement model of adoption signals, time and effort indicators and business outcomes, and explain why role-based deployment makes value measurable.

Power BI Grounding: Copilot Reasons Over Semantic Models

Wednesday, September 9, 2026 · Maximilian Kenfenheuer

Since the August 2026 update, Microsoft 365 Copilot reasons over Power BI reports and semantic models in Chat and Cowork. Copilot thus works with governed business definitions: how revenue is defined, how margin is calculated, which KPIs leadership uses and who may see which numbers. At the same time, a poorly defined KPI now spreads faster. In this article, I explain why semantic models become the foundation for trustworthy AI answers and how organizations can prepare their analytics layer.

From Draft to Deliverable: Agentic Copilot in the Core Apps

Saturday, September 5, 2026 · Maximilian Kenfenheuer

On April 22, Microsoft made agentic capabilities in Word, Excel and PowerPoint generally available and brought business apps into Copilot via agents. AI moves to where proposals are written, financial models built and board decks assembled. At the same time, human judgment gains weight: a polished deck is not automatically a sound strategy, and a well-structured spreadsheet is not automatically a correct model. In this article, I explain what changes when AI participates in the work and which five readiness questions organizations should answer.

Posts tagged #ResponsibleAI

Domain Exclusion in Practice: Ownership, Maintenance and Limits

Saturday, August 29, 2026 · Maximilian Kenfenheuer

#Microsoft365Copilot #MicrosoftAI #Copilot #AIGovernance #ResponsibleAI

AI governance used to ask whether employees may use AI and which model is approved. Today, organizations need finer controls, including which external sources may influence Copilot answers. Domain exclusion lets admins exclude up to 1,000 websites from web grounding in Microsoft 365 Copilot. The scope is limited to web page results, and the list is maintained via PowerShell and CSV. In this article, I explain why source controls shape answer quality and who in the organization should own the exclusion list.

Source-Level Governance for Copilot Web Grounding

Tuesday, August 18, 2026 · Maximilian Kenfenheuer

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

Web grounding sounds technical, but it is becoming a leadership question: which sources may influence Copilot answers in an enterprise? Microsoft Learn documents domain exclusion for up to 1,000 sites, managed via PowerShell by admin roles. At the same time, Microsoft has rolled the feature back for now. That makes it a signal rather than a finished feature. In this article, I explain why source-level governance becomes part of the enterprise AI operating model and which questions organizations should clarify now.

Domain Exclusion: Defining Which Web Sources Copilot Must Not Use

Friday, August 7, 2026 · Maximilian Kenfenheuer

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

Admins can now exclude up to 1,000 domains from web grounding in Microsoft 365 Copilot and Copilot Chat. Configuration runs via a PowerShell script, optionally including subpages. The feature looks like a configuration detail. It shows, however, where enterprise AI is heading: organizations want to define which sources Copilot must not use, not only extend what it can see. In this article, I explain the feature, its current limits and why administrative precision should weigh more in platform decisions.