Elliot Margot
Team Lead Jumpstart at Witivio · Microsoft AI Specialist · Copilot Studio & Agents
Lausanne, Switzerland
Actions
Elliot Margot designs and ships production Microsoft Copilot Studio agents for European enterprises. His work on an AI procurement agent at BuyerCompanion was selected as an official Microsoft Customer Story. As Team Lead Jumpstart - Copilot and Agents at Witivio (Microsoft Partner), he runs envisioning-to-deployment engagements across DACH, France and Switzerland: 60+ use cases scoped across 17 industries, 15+ production AI architectures shipped. Based in Lausanne, he speaks regularly at Microsoft community events in English, French and German.
Links
Area of Expertise
Topics
Agents that died in production: 5 Copilot Studio failures and what we learned
Most Copilot Studio talks show the build, the demo, the applause. This one shows the graveyard. Five real agents from real Jumpstart engagements that shipped, struggled, and got pulled. No vendor names, no client names, just the patterns that keep killing internal AI projects. The knowledge soup: an agent grounded on an entire SharePoint site that confidently returned policy from 2019 alongside policy from 2025 - why broad RAG without hygiene is a hallucination factory and what to scope instead. The over-trusting agent: a procurement assistant that took the user's word on their approval level and called the back-end API anyway - how agents inherit privilege confusion from the prompt and the simple identity check that fixes it. The expensive intern: an agent that worked beautifully and burned through tokens and Copilot Studio messages faster than the team it was meant to assist - how to instrument cost from day one and what to do when the curve goes vertical. The forgotten agent: built in two weeks, launched on a Friday, dead by month two - why 'we'll add adoption later' never works and the three things that make agents actually used. The frankenstein: sixteen Power Automate flows, four custom connectors, three knowledge sources - one upstream API change took the whole thing down, and how to design for the failure mode you will absolutely have. You leave with an honest mental model of what breaks, a 5-point pre-deployment checklist, and the confidence to say no when an agent is not ready to ship.
Live Build: 3 IT Helpdesk Agents in 60 Minutes
The promise: walk in with a laptop, walk out with three working Copilot Studio agents shipped to your tenant. Zero theory, pure keyboard.
We skip the "what is Copilot Studio" intro (you can Google that) and ship three production-style agents in one room, live, with the screen visible and the gotchas called out as they happen.
Agent 1 - Password Reset Assistant (15 min): Adaptive Card welcome, knowledge connection to a self-service KB, Power Automate action to trigger Entra Self-Service Password Reset, fallback hand-off to L1 if validation fails.
Agent 2 - Software Request Triage (20 min): Topic with branching logic, DLP-aware data handling, connector to ITSM (ServiceNow / Jira), approval flow with manager check, audit logging.
Agent 3 - Device Enrollment Helper (15 min): Intune docs as knowledge source, decision tree for Windows / iOS / Android, Adaptive Card with QR-coded enrollment link per platform, telemetry hooks for analytics.
Final 10 minutes: ALM patterns to promote from sandbox to production, environment strategy, the gotchas the docs do not publish, Q and A.
This is not a workshop where you build along. It is a live build demo with screen, code, and decisions visible the whole time, designed so you can replicate every step in your own tenant after the session.
Cut RFP response time from days to hours with Copilot Studio
Your sales team spends 2 days on every RFP. 80% of the answers already exist in past proposals. Nobody can find them fast enough. This workshop builds the agent that changes that - no code, no IT ticket, no waiting.
We build together using Copilot Studio's no-code canvas. Starting point: a folder of past proposals in SharePoint. End state: an agent your sales team can use today to upload an RFP, extract the key requirements, and get a draft response grounded in your own content - in under 5 minutes.
What we configure together: connect the knowledge source (your SharePoint proposals folder), write the system prompt in plain English that tells the agent what to do with an RFP, test it against a real document, and publish it to Teams so anyone on the sales team can use it without a Copilot Studio license.
Just Copilot Studio, SharePoint, and a system prompt that does the heavy lifting. We also wire one Power Automate action: the agent exports the draft directly to a Word document ready for review. You leave with a working agent, the exact prompt template, and a reusable flow pattern to adapt for your own use case.
Elliot Margot
Team Lead Jumpstart at Witivio · Microsoft AI Specialist · Copilot Studio & Agents
Lausanne, Switzerland
Links
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top