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

Markdown and Text Files in Copilot Notebooks: Using Operational Knowledge

#Microsoft365Copilot #MicrosoftAI #AI #Copilot #EnterpriseAI

Copilot Notebooks now accepts Markdown (.md), plain-text (.txt) and rich-text (.rtf) files as references. This sounds minor. Much operational knowledge, however, sits in READMEs, wikis, logs, transcripts and handoff notes that nobody ever converts into a Word document. Copilot can now use this material together with formal documents. In this article, I explain which teams benefit most, how cross-source reasoning improves and which governance questions arise with lightweight files.

Frontier Tuning: Reinforcement Learning Inside the Compliance Boundary

#Microsoft365Copilot #MicrosoftAI #CopilotStudio #EnterpriseAI #AITransformation

Microsoft introduced Frontier Tuning at Build. It applies reinforcement learning inside the organization's compliance boundary, using its own data, conventions and workflows. The results are tuned models, skills, orchestration logic and a runtime harness that inherit existing access policies. Frontier Tuning comes to Copilot Studio and Microsoft Foundry. Pearson, EY, Bristol Myers Squibb and McKinsey are among the early users. In this article, I explain how tuning differs from prompting and retrieval and which questions organizations should answer before tuning agents.

Synced or Federated: Connecting Business Apps to Copilot

#Microsoft365 #Copilot #MicrosoftAI #AI #EnterpriseAI

A useful Copilot answer appears in seconds. Afterwards, the user often still opens another application, finds the record and carries the work forward by hand. Connected apps such as Adobe Express, Figma, Dynamics 365, Box, monday.com and Miro now appear directly inside Microsoft 365 Copilot. Copilot connectors link more than 100 external sources, either synced into Microsoft Graph or federated in real time. In this article, I explain the difference between synced and federated connectors and which four questions leaders should answer before connecting more systems.

The Copilot Interface as a Governance Surface

#Microsoft365 #MicrosoftCopilot #AI #EnterpriseAI #MicrosoftAI #DigitalTransformation

With the May update, Microsoft redesigned how Copilot appears across Microsoft 365. As Copilot takes on more actions, the interface has to show what the AI does, which context it uses and what requires human review. The interface thus becomes a governance surface as well as a productivity surface. In this article, I explain why workflow fit belongs in adoption planning and why change management should target concrete moments of work instead of features.

Source-Level Governance for Copilot Web Grounding

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