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 Connectors: Grounding Quality Depends on Metadata and Permissions

#MicrosoftAI #Microsoft365Copilot #CopilotConnectors #EnterpriseAI #AIArchitecture

Policies sit in SharePoint, customer records in Salesforce, knowledge articles in ServiceNow or Confluence. Copilot only reasons over them if the systems are connected properly. Copilot connectors offer two models: synced connectors index content into Microsoft Graph, federated connectors fetch it in real time via the Model Context Protocol (MCP). The gallery holds more than 100 connectors. In this article, I explain when each model fits, why grounding quality depends on metadata and permissions and who should own connector governance.

Twice as Fast, Higher Usage: What the New Copilot App Changes

#Microsoft365Copilot #MicrosoftAI #Copilot #AIAdoption #EnterpriseAI

The redesigned Copilot app loads more than twice as fast, and complex chat prompts respond 10 % faster. After the rollout of the new in-app experiences, Microsoft reports higher usage: 27 % in Word, 33 % in Excel, 43 % in PowerPoint and 30 % in Outlook. The prompt line turns into a task-aware workspace, and the output itself becomes part of the interface. In this article, I explain why experience design influences Copilot adoption as much as the model and what organizations should derive from it.

Multi-Agent Orchestration with Fabric, the Agents SDK and A2A

#MicrosoftAI #Microsoft365Copilot #CopilotStudio #AI #EnterpriseAI

Enterprise processes rarely fit into a single agent. One retrieves information, another analyzes data, a third drafts content in Microsoft 365, a fourth triggers an action. Copilot Studio now supports multi-agent orchestration with Microsoft Fabric, the Microsoft 365 Agents SDK and Agent-to-Agent (A2A) communication via open protocols. In this article, I explain why specialized agents scale better than one monolithic agent and which governance questions arise when agents delegate work to each other.

Agent Evaluation with Custom Graders in Copilot Studio

#MicrosoftAI #Microsoft365Copilot #CopilotStudio #AIGovernance #AgenticAI

"The demo worked" and "users liked it" are not enough once agents support customer interactions, approvals or system actions. Copilot Studio now offers custom graders for agent evaluations. Organizations assess agents against their own criteria: approved terminology, correct internal sources, escalation at low confidence and compliance with process boundaries. In this article, I explain why evaluation and governance belong together and how organizations can define and measure agent quality in five steps.

Ten Generic Tools: The Work IQ MCP Server and Agent Architecture

#Microsoft365Copilot #MicrosoftAI #CopilotStudio #AI #EnterpriseAI

The Work IQ API endpoints reach general availability on June 16. Work IQ combines Chat, Context, Tools and Workspaces and turns intelligence into a reusable service layer for agents. One design choice stands out: the Work IQ MCP server reduces hundreds of operations to 10 generic tools, and getSchema lets agents discover data structures dynamically. Usage is independent of Copilot licensing and billed on consumption. In this article, I explain what this architecture means for consistency, speed and governance of custom agents.