
RPA Teacher. Follow along👆 35,000+ YouTube Subscribers. Microsoft MVP. 2 x UiPath MVP.
Anders Jensen [MVP] published a clear, step-by-step YouTube tutorial showing how to add Claude Cowork to Microsoft 365 Copilot. The video walks viewers through discovering the agent in the Agent Store, installing it, selecting models, and running automated workflows inside familiar Microsoft apps. Consequently, the tutorial targets both individual users who want quick wins and IT teams that must consider governance. Overall, Jensen frames the setup as practical and immediately useful for daily productivity.
First, the video demonstrates how to locate Claude Cowork in the Copilot Agent Store and install it into a Microsoft 365 tenant. Jensen shows each click and setting with commentary, so viewers can replicate the steps without guesswork. Then, he explains model selection options and how those choices affect reasoning and execution inside Copilot. As a result, the tutorial serves as a hands-on guide for both beginners and experienced users.
Next, Jensen runs live examples that illustrate cross-app automation across Outlook, Teams, Excel, and PowerPoint. He asks Copilot to plan and perform multi-step tasks such as compiling meeting briefings, pulling Excel financials, drafting emails, and preparing slides. During these segments, the video emphasizes the checkpoint workflow where users review and approve each step before execution. Thus, viewers see both the power of automation and the safeguards Microsoft builds into the process.
Jensen outlines the practical setup details, including permissions and tenant-scoped deployment, so administrators understand the control points. He also compares model choices, noting that Copilot can route tasks to different engines, including Claude variants and other models, to balance planning and execution strengths. This multi-model strategy aims to match tasks to the best tool, which can improve results but adds configuration considerations. Therefore, Jensen advises testing with representative tasks to find the most reliable mix.
In addition, the tutorial highlights the importance of the review checkpoints that appear before Copilot executes actions across apps. Jensen shows how to accept, edit, or pause plans, and how Copilot asks for clarification when instructions are ambiguous. These checkpoints reduce risk, especially for sensitive operations like deleting files or sending mass emails. Consequently, administrators and end users can maintain control while still benefiting from automation.
According to the video, teams can speed up routine work such as meeting prep, budget summaries, and status updates by using Claude Cowork inside Copilot. Jensen demonstrates time savings when Copilot pulls context from calendars, emails, and documents to assemble briefings and slides. Moreover, outputs are saved natively in Microsoft 365 apps so teams can refine results collaboratively. As a result, this approach fits typical enterprise workflows without requiring external tools.
Jensen also shows how automation can improve consistency in reporting and reduce manual file hunting across SharePoint and OneDrive. By grounding actions in M365 signals—emails, chats, and documents—Copilot produces more relevant outputs than a generic prompt might. Still, Jensen cautions that users should review generated content for accuracy and tone before distribution. Thus, the combination of automation and human review becomes central to practical adoption.
Jensen does not shy away from discussing tradeoffs, such as balancing convenience against governance and auditability. While cloud-based Cowork in Microsoft 365 offers enterprise controls and logging, it also raises questions about which model handles which task and who approves sensitive actions. Consequently, organizations must design policies that define model use, approval thresholds, and data handling practices. Without those policies, automated workflows can introduce compliance and operational risks.
Furthermore, Jensen explores technical challenges like cross-app state handling and the potential for model errors or misinterpretations. He notes that Copilot seeks clarification when uncertain, but complex multi-step tasks can still fail or produce incomplete outputs. Therefore, teams should pilot workflows in non-critical environments and maintain human oversight. In short, the move to agent-driven automation requires careful testing, training, and clear escalation paths.
Finally, Jensen recommends that organizations start small with clearly defined tasks and expand automation as confidence grows. He suggests beginning with low-risk processes such as meeting summaries or data pulls, and progressively adding more sensitive actions once controls and review workflows prove reliable. Additionally, he urges IT and business leaders to monitor audit logs and user feedback closely to adjust policies and model routing over time. In this way, teams can capture productivity gains while managing risk.
In conclusion, the YouTube tutorial by Anders Jensen [MVP] provides a practical roadmap for integrating Claude Cowork into Microsoft 365 Copilot, balancing hands-on setup with governance advice. By showing live examples and noting tradeoffs, the video helps viewers weigh benefits against operational challenges. As organizations evaluate agent-driven automation, Jensen’s stepwise approach offers a useful starting point for secure, accountable adoption.
Claude in Copilot setup, Add Claude to Copilot, Claude Copilot integration, Full setup tutorial Claude Copilot, How to use Claude in Copilot, Anthropic Claude Copilot guide, Copilot Claude walkthrough, Enable Claude in Microsoft Copilot