How to Actually Get Value from Copilot at Work

Feb 25, 2026

Yves Habersaat, a Swiss AI and Microsoft technologies practitioner who builds agents and advises on Copilot adoption. He talks about starting Copilot where people already work, why Microsoft Teams yields quick wins, simple agent use cases like automated meeting minutes, choosing models with Azure Foundry, and when low-code Copilot Studio suffices versus custom SDK development.

Ask episode

AI Snips

Chapters

Transcript

Episode notes

INSIGHT

Swiss Adoption Shifted From Cloud Migration To Practical AI

AI adoption in Switzerland moved from migration to practical use this year.
Customers migrated to M365/Azure then started buying Copilot licenses and asking for training on prompts and agents.

ADVICE

Introduce Copilot Inside Teams For Fast Time To Value

Start Copilot where people already work by introducing it inside Microsoft Teams.
Yves uses Copilot in Teams to generate meeting minutes from meetings with simple pre-made prompts for fast time-to-value.

ADVICE

Keep Agents Simple Then Iterate With Feedback

Keep agents simple at the start and iterate with user feedback.
Yves built an agent that extracts Teams transcript data into a Word minutes template and plans to add automation later after feedback.

Get the Snipd Podcast app to discover more snips from this episode

Get the app

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM

This episode explores how organisations can move from AI curiosity to real value using Microsoft Copilot and agents, drawing on practical insights from Yves Habersaat. The conversation focuses on adoption that starts where people already work, keeps early use cases simple, and scales only when the need is clear. It also covers real-world agent scenarios, model choice, and why low-code tools are often enough to deliver results quickly.

👉 Full Show Notes
https://www.microsoftinnovationpodcast.com/803

🎙️ What you’ll learn

How to introduce Copilot in tools teams already use every day
Why Teams is often the fastest way to see AI value
When simple agents are enough and when custom builds make sense
How to approach agent design without overengineering
Why understanding the use case matters more than the tool choice

🔴 Highlights

“A lot of customers want to try concretely what is AI.”
“They want to use AI in the day-to-day basis.”
“Teams is a really good entry point.”
“You can have concrete results without spending a lot of time.”
“Keep it simple at the beginning.”
“After, you add more complexity and more logic.”
“Copilot Studio has evolved a lot.”
“You need to understand the use case first.”

🧰 Mentioned

Microsoft Copilot - https://copilot.microsoft.com/
Agent SDK (Microsoft 365 Agents SDK) - https://learn.microsoft.com/microsoft-365/agents-sdk/
Azure AI Foundry - https://ai.azure.com/
Azure - https://azure.microsoft.com/
ChatGPT - https://chat.openai.com/
Microsoft MVP YouTube Series - How to Become a Microsoft MVP - https://www.youtube.com/playlist?list=PLzf0yupPbVkqdRJDPVE4PtTlm6quDhiu7

✅ Keywords
microsoft copilot, ai agents, copilot studio, microsoft teams, azure ai, agent sdk, ai adoption, prompting, enterprise ai, ai workflows, low code ai, applied ai

Microsoft 365 Copilot Adoption is a Microsoft Press book for leaders and consultants. It shows how to identify high-value use cases, set guardrails, enable champions, and measure impact, so Copilot sticks. Practical frameworks, checklists, and metrics you can use this month. Get the book: https://bit.ly/CopilotAdoption

Support the show

If you want to get in touch with me, you can message me here on Linkedin.

Thanks for listening 🚀 - Mark Smith