Short answer
Most staff need a half day to use Copilot well on their own work. Power users need a full day for agents and reusable instructions. Admins need one to two days for Copilot Studio, Power Automate, and governance. Leaders need a half-day briefing. A whole organization can usually be trained within a few weeks.
By role
| Role | Time | What they leave able to do |
|---|---|---|
| All staff | Half day | Use Copilot in mail, meetings, documents, and data on their own work |
| Power users | One day | Write reusable instructions, build agents over team content, use Researcher |
| Admins and IT | One to two days | Build and govern Copilot Studio agents and Power Automate flows, forecast credits |
| Leaders | Half day | Decide what to license, what to build, and what to measure |
Scroll the table sideways to see every column.
Why not a one-hour webinar?
A webinar shows what Copilot is. It rarely changes how people work, because the change comes from practice on their own documents, mail, and meetings, with someone there to fix the prompt that did not work. That is why licenses bought after a demo often go unused.
Splitting it up
A half-day course can run as two 90-minute sessions. Two-day admin cohorts can run across a week. Hands-on time stays the same.
A whole organization
Start with leaders and power users, so they can answer questions for everyone else. Then run staff sessions in groups of up to 15 in parallel. Most organizations finish within a few weeks.
Based on Microsoft's published documentation as of October 2026. Microsoft changes names, features, and billing often; confirm details in your own tenant.