Copilot Workshop
for IT Teams
Microsoft 365 Copilot, hands-on, 1.5 to 4 hours
Bottom line: the Copilot workshop for IT teams shows your team how to use Copilot on its real tasks, and how those tasks change once it does. The service desk works on incident threads and knowledge-base articles. Admins work on change requests and vendor documents. Your Microsoft 365 owners work on rollout messages, and on what Copilot can reach. It's Microsoft 365 Copilot, not GitHub Copilot (developers, wrong page).
I've worked and trained on AI since early 2022, and I've run 264 AI sessions in 112 organisations (updated October 2026).
Why the IT team needs its own Copilot session
IT gets the Copilot questions first, and usually has had the least hands-on time with it. The licences get bought, the announcement goes out, and then the tickets start. Why is nobody using it? What can it see? Who approved that agent? (Your people use Copilot, Claude or Gemini whether or not IT has a view, and the questions land on IT either way.)
According to Recon Analytics (February 2026), only 35.8% of US workers who have Copilot available at work use it as their main AI tool (that's from their survey of 150,000+ respondents, US only). A licence on its own does not create use. If your rollout is already wobbling, here's why Copilot rollouts stall in month two.
During a Copilot rollout, IT answers those questions better after a morning of using Copilot on its own work. That's my Microsoft Copilot training for IT teams: Copilot from the inside, not from a vendor slide.
What the IT team does in the Copilot workshop
Training for IT admins and service desk staff differs from end-user training. End-user training teaches Copilot inside someone else's job. Here the IT team brings its own work, which is where Microsoft 365 Copilot training for an IT department should start.
01Incident threads
A long thread, summarised for the person who joins late. Classic Copilot for IT support work.
02Change requests and knowledge-base articles
A first draft from your own notes. Copilot writes version 1, you write the version people actually read.
03Vendor documents
A long document turned into a checklist you can work through.
04Rollout communications
The message to users about what is changing and what to do about it.
These are tasks your people bring along, not guaranteed outputs. Each person leaves with the prompts they wrote themselves on their own tasks, ready to reuse the next morning. That's the whole promise (I'd rather keep it small and true).
Is this a Copilot admin course?
No. The Copilot workshop for IT teams is a workshop, not a configuration project. I don't touch your tenant, and nothing in it is changed.
What IT sees that end users never see
Microsoft states in its Copilot privacy documentation (2026) that Copilot only surfaces organisational data to which an individual user has at least view permissions. That sounds reassuring until you remember how many files people can already open.
So the question IT hears is rarely "what can Copilot see" and more often "what can this person already open". In the workshop your team asks Copilot exactly that, for a given person, and looks at the answer together.
EU data questions have their own page: Copilot, GDPR and EU data residency. Agents that need an admin's approval are worth understanding before users start asking for them.
How the Copilot workshop for IT teams runs
A Copilot workshop for IT teams runs 1.5 to 4 hours depending on the format, with up to 20 participants. Everyone is on their own machine and I need to reach each person. A larger IT group splits into 2 workshops, or switches to a lecture.
It runs on site or online, with the same hands-on format and the same limit of 20. Based in the UK? There's more on Copilot training for UK organisations.
Invite your Copilot champions, a security contact and a service desk lead alongside the IT admins, since those are the people who answer the questions after rollout. The Champions in a Box programme explains the champion role.
The same hands-on format exists for executives, finance teams and HR teams. For mixed roles in one room, there's the general Copilot workshop.
Who runs it
I've worked and trained on AI since early 2022, with 264 AI sessions in 112 organisations so far (updated October 2026). The product changes constantly, and so do the workshops and lectures (what you saw in the menu last month may already have moved).
I have no commercial interest in Microsoft. If you're wondering about my bias, it's toward people actually using the thing.
Common questions
Is the Copilot workshop for IT admins or for end users?
It's Copilot for IT admins, service desk staff and Microsoft 365 owners. They use Copilot on their own work and see it the way users do. It is not end-user training, and it is not an admin course.
Will you configure our tenant or run a security audit?
No. It is a workshop, not a configuration project. Participants work on their own tasks, and nothing in your tenant is changed. I don't run security audits or implementation projects.
Does the workshop cover oversharing and permissions?
It shows what Copilot can reach from the user's side, which is what IT gets asked about. It is not a permissions audit. More in Copilot, GDPR and EU data residency.
How many people can join, and what about a large IT team?
Up to 20 per workshop, for 1.5 to 4 hours. For Copilot training for large teams, a bigger IT group splits into 2 or more workshops, or switches to a lecture (less hands-on, but it fits more people).
Can the Copilot workshop for IT teams run online?
Yes. It runs on site or online, with the same hands-on format and the same limit of 20 people.
Who else should attend besides IT?
Your Copilot champions, a security contact and a service desk lead, since they answer the questions after rollout. For a session covering all roles, see Microsoft Copilot training for companies.
Let's find your session.
Tell me who is on your IT team and where the Copilot questions are landing. I'll suggest a format that fits.