The Microsoft Copilot workshop
that actually gets used
on Monday morning.
A Microsoft Copilot workshop for organizations is a single, focused session where participants open Word, Outlook, Excel, and Teams and work through real exercises on real documents. Not slides. Not a demo. Hands on the tool.
I've run Copilot workshops for more than 120 organizations as of mid-2026 (across just about every category: insurance, banking, healthcare, startups, retail, professional services, and more), with organizations ranging from mid-sized to enormous. Dozens of those sessions have been delivered in English, over Zoom, to distributed and international teams. The format that works: short preparation conversation before, tailored content on the day, small enough group to give everyone real attention. Max 25 participants per hands-on session. That limit isn't arbitrary. It's the number above which I can't circulate and help people who get stuck, and at that point it isn't really a workshop anymore.
If you're looking for a multi-session course rather than a single workshop, the Microsoft Copilot training for companies page covers that. If you need ongoing strategy and consulting rather than a training event, see the Copilot consulting page. This page is about the workshop format specifically.
What happens in a Microsoft Copilot workshop
A Microsoft Copilot workshop runs 3 to 4 hours. Participants come in with Copilot open on their computers (or join via Zoom with their Microsoft 365 accounts active). From the first few minutes, we're working inside the actual apps, not watching a slideshow about them.
The content is built around the specific team. Before the session, I have a conversation with someone who knows the group: what they do all day, what a good use of 3 hours looks like for them, what would make this feel like a waste of time. That shapes everything. A finance team and a communications team both use Word and Outlook, but the examples that land for one won't land for the other.
I ask teams to share real documents in advance (with sensitive content removed, of course). We work with those. When a participant sees Copilot processing something they recognize from their own work, it clicks differently than any generic demonstration would.
01Copilot in Word and Outlook
Drafting, rewriting, summarizing long email threads, composing replies from bullet points. These two applications cover the majority of where knowledge workers spend their time. The practice exercises use real documents collected from the team before the session. This is usually where people have their first "I didn't know it could do that" moment.
02Copilot in Teams meetings
Meeting summaries, action item capture, catching up on a meeting you missed. For most participants, this is the feature they start using immediately after the workshop because it requires almost no behavior change: the meeting happens, Copilot is on, the summary appears. We cover setup, how to read and use the output, and how to prompt it when the auto-summary misses something important.
03Copilot in Excel and PowerPoint
Data analysis, formula explanation, chart suggestions, slides generated from existing content. These get more depth in dedicated sessions (or in the multi-session course format). In a generalist workshop, we cover the basics and participants go deeper on whichever application matters most for their role. (Finance teams tend to disappear entirely into the Excel portion. Every time.)
04Prompting: the skill that transfers everywhere
Knowing that Copilot exists isn't the gap. Knowing how to ask it for something and get back something useful is. A significant part of every workshop covers prompting: what makes a request work, how to iterate when the first result isn't right, how to build prompts for tasks that repeat week after week. This transfers across every Copilot surface and keeps working long after the session ends.
Copilot workshop formats: in-person and remote
A Copilot workshop for teams runs either in-person or over Zoom. Both formats deliver hands-on practice. The choice depends more on your team's setup than on which is technically better.
Remote over Zoom is the default for most of the teams I work with. Participants are already at their computers, which is exactly where they'll use Copilot. Logistics are simpler, coordination is easier, and the hands-on practice works very well when everyone has their own screen. In-person works for organizations that specifically want a physical group event, or for teams that don't have individual laptop setups in a room.
01Remote workshop over Zoom (recommended starting point)
Three to four hours over Zoom. Participants join from their own computers with Copilot active. Real exercises happen in the actual apps during the session. I can see where people are, answer questions in the chat or verbally, and bring the whole group back together for shared practice at key moments. Works for teams spread across locations, time zones, or who simply prefer not to coordinate a physical event. This is the format that covers the most ground with the least scheduling friction.
02In-person workshop (onsite at your location)
Same content, same exercises, same hands-on format. I come to your location. Works well when you want the energy of a physical gathering, or when your team's setup doesn't easily support a Zoom-based hands-on session. For larger organizations, in-person sessions are sometimes preferred for senior leadership groups. The 25-participant cap applies here as well.
Why the cap is 25 and not higher
When I run a hands-on workshop, I circulate, check in on people who are stuck, and adjust the pace based on where the room is. That works up to around 25 participants. Above that number, I can't physically give people the individual attention that makes the hands-on format work. For larger teams, the right approach is either multiple workshop waves (running the session twice or three times with different groups) or a lecture format for the full team combined with workshops for specific departments. I'm honest about this on every intro call: if you have 80 people, one workshop session isn't the answer.
Who the Copilot workshop for organizations is built for
Most of the participants I train are not technical. They're lawyers, account managers, project coordinators, HR professionals, analysts, finance team members. People who spend most of their working day in Word, Outlook, Excel, and Teams. Copilot was genuinely built for them (not as an afterthought, and not primarily for developers), and a workshop designed for them works.
That said, the workshop adapts. I've run sessions specifically for IT teams who want to understand what Copilot can and can't do before rolling it out. For senior leadership groups who want to understand the tool before endorsing it internally. For L&D teams building an internal enablement plan. The audience changes what we emphasize. The core remains the same: start with what this specific group actually does, build the practice around that, and leave them with things they can use before the week is out.
Organizations that get the most from this format
Teams that have Microsoft 365 Copilot licenses and want people to start using them. Organizations that ran a rollout announcement and found adoption stalling. IT and L&D leaders who want a structured, hands-on event rather than a generic product orientation. Senior teams who want to understand Copilot before mandating it. And any team that's heard "Copilot is great" but hasn't yet had a session where someone shows them specifically what to do with it in their own work. For everything that goes beyond a single workshop, see the full Microsoft Copilot training page or read the complete Microsoft Copilot guide.
What a good Copilot workshop actually looks like
I've been working with AI tools since late 2022 and training organizations full-time since early 2023. That means I've been inside Copilot since before most organizations had heard of it. I've seen what people get stuck on when they open it for the first time. I've also seen what happens three months after a generic training event when there's been no follow-up (the adoption rate goes back to where it started).
I deliver dozens of Microsoft Copilot workshop sessions in English, over Zoom, to distributed and international teams. The organizations span just about every category you could name: insurance, banking, healthcare, startups, retail, professional services, enterprise tech, and more. They range from mid-sized to enormous. Remote delivery over Zoom has become the default for most of them, and it works extremely well for this format.
I run a weekly AI newsletter (since February 2023), which means I'm testing new Copilot features the week they ship. What I teach reflects how the product actually works right now. When Microsoft updates something (which happens regularly), the material gets updated. You notice this in small ways during the workshop: I won't demo a feature and then explain it changed last month. That kind of thing goes unnoticed in a generic session. It doesn't go unnoticed here…
Real documents, not toy examples
Before the session, I ask teams to share examples of the kinds of documents they work with: emails they write, reports they produce, meeting notes they take. I work with those during the workshop. Seeing Copilot handle something that looks like your actual work lands differently than watching it summarize a fictional scenario built for a demo.
Tailored, every time
Every workshop looks and behaves differently. That's not a marketing line. It's how the prep conversation works: I ask what the team does, what a good outcome looks like for them, what would make this feel like a wasted half-day. The answers change the session. A legal team's workshop and a marketing team's workshop cover some of the same Copilot features but feel completely different in how they're framed and what gets practiced. (This is what distinguishes a tailored session from a generic vendor orientation.)
What happens after
I stay available for questions after sessions. For organizations doing a full Copilot rollout (planning, multiple waves of training, tracking adoption), there's a consulting and advisory structure that goes beyond a single workshop. See the Microsoft Copilot consultant page for what that looks like.
How to book a Copilot workshop for your team
The process is short. A conversation before anything is confirmed, a tailored plan, then the session itself.
01Intro call (30-45 minutes)
We talk about your team: how many people, what they do, how far along the Copilot rollout is, and what you want participants to be able to do after the workshop. No proposal until that conversation has happened. I've had calls where the honest answer was "a single workshop isn't the right starting point for where you are" and I'll say that. (I'd rather that conversation happen before you book than after.)
02Tailored plan
Based on the call, I put together a clear picture of what I'd recommend: format (Zoom or in-person), session structure, application focus, and logistics. You know exactly what you're getting before anything is finalized.
03Pre-session preparation
Before the workshop, I collect real examples from your team (document types, common tasks, the kinds of things they'd actually want Copilot to help with). That shapes the exercises. I also confirm that participants have Copilot active and accessible before the session starts, so we don't spend the first 30 minutes troubleshooting licenses.
04The workshop
In-person or over Zoom. Hands on the tool from the start. Real exercises, real documents, time for questions. Most participants find that the hardest part is not having more time at the end. That's usually a good sign.
Questions people ask before booking
What does a Microsoft Copilot workshop include?
A hands-on session of 3 to 4 hours where participants work with Copilot inside the Microsoft 365 apps they actually use: Word, Outlook, Teams, Excel, and PowerPoint. The application focus is tailored to the team in advance. We cover real exercises, not just demos. A significant portion of every workshop is dedicated to prompting: how to ask Copilot well, how to iterate, and how to build prompts for tasks that repeat regularly. Participants leave with 2 to 3 things they can do in Copilot immediately, not someday.
How many people can join a Copilot workshop?
The cap for a hands-on workshop is 25 participants. Above that number, I can't circulate and give people the individual attention that makes hands-on practice work. For larger teams, the right approach is either running the workshop in multiple waves (the same session repeated with different groups) or pairing a larger-audience lecture with smaller follow-up workshops for specific teams. I'll be honest about this on the intro call: if you have 60 people, one single workshop isn't the answer.
Can the workshop run over Zoom for remote or international teams?
Yes. I deliver dozens of Microsoft Copilot workshops in English, over Zoom, to distributed and international teams. Remote delivery works very well for this format because participants are already at their own computers with Copilot active, which is exactly how they'll use it in their daily work. Online workshops are also significantly easier to coordinate and schedule. In-person is available for organizations that specifically want a physical event. We decide what makes sense on the intro call.
How is this workshop different from a multi-session Copilot course?
A workshop is a single session (3 to 4 hours). The goal is to get participants using Copilot on real tasks immediately. A multi-session course (typically 4 sessions over several weeks) goes deeper: there's time between sessions for participants to practice in their actual work, come back with questions, and build real habits. Both formats work. The workshop is the faster, more focused option. If you want the deeper skill change that comes from repeated practice over time, the Copilot training for companies page covers the multi-session course in detail.
How do we get started?
Book an intro call using the calendar link below, or send an email to eyal@eyalmarcus.com. The call takes 30 to 45 minutes. By the end you'll have a clear picture of what format makes sense for your team, what it would look like, and whether this is the right fit. No obligation, no pitch deck. I'll get back to you within one business day if you reach out by email.
Let's talk about your team.
An intro call takes 30 to 45 minutes. By the end you'll know exactly what I'd recommend and what the workshop would look like for your organization.