Blog

Maximilian Kenfenheuer

Manager · Microsoft 365 & AI Transformation @ BearingPoint

Maximilian Kenfenheuer

Featured

Measuring Completed Work: Baselines, Assisted Hours and Business Outcomes

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.

Continue reading

Latest posts

Copilot Tuning and Multi-Agent Orchestration: Adapting AI to the Organization

#Microsoft365Copilot #MicrosoftAI #CopilotStudio #EnterpriseAI #AITransformation

A law firm has its own drafting style, a consulting company its own industry playbooks. General-purpose models do not know either. With Microsoft 365 Copilot Tuning, organizations tune models with their own data, workflows and processes in Copilot Studio, low-code and without a data science team. Multi-agent orchestration lets HR, IT and marketing agents share work, for example during onboarding. In this article, I explain why organizational fit may become a stronger advantage than access to the most powerful general model.

Copilot Design and Adoption: Habits Instead of Occasional Visits

#Microsoft365Copilot #MicrosoftAI #AIAdoption #FutureOfWork #EnterpriseAI

Many organizations no longer ask whether Microsoft 365 Copilot can do useful things. They ask whether employees use it often and easily enough for it to become part of normal work. Microsoft's redesign of May 28 addresses this question. Fewer clicks and less context switching turn Copilot from a separate destination into a capability close at hand. In this article, I explain why experience design now belongs to enterprise AI readiness and which questions leaders should ask.

Model Choice in Copilot Cowork: From AI Access to a Model Portfolio

#Microsoft365Copilot #MicrosoftAI #AI #CopilotStudio #EnterpriseAI

Copilot Cowork now offers several models, depending on what the organization allows: Auto, Claude Sonnet 5, Claude Opus 4.8, GPT 5.5 (Frontier) and a paired Sonnet + Opus Advisor mode. A quick meeting summary needs different capabilities than a high-stakes research synthesis. Microsoft makes this choice available inside enterprise controls, with visible retention notices and admin settings per model family. In this article, I explain why enterprises move from AI access to managing a model portfolio and what IT leaders should watch.

Domain Exclusion: Defining Which Web Sources Copilot Must Not Use

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

Data, Memory, Inference: The Three Layers of Work IQ

#Microsoft365Copilot #MicrosoftAI #Copilot #AI #EnterpriseAI #CopilotStudio

An excellent model with thin enterprise context still produces generic output. The advantage lies with the platform that provides context. Work IQ builds this context in three layers: data from Microsoft 365 and business systems, memory about how teams work, and inference for reasoning and action. Microsoft offers it via REST, agent-to-agent and a remote MCP server, on a consumption basis and independent of Copilot licensing. In this article, I explain why this context infrastructure may become more durable than any assistant interface.