Copilot Studio Foundations — Standard Harness
Build, publish and cost a working agent in twelve hours. No coding.
Learn more →
Training
Your team builds a real agent. On your tenant.
No sandbox, no slide-only days. Everyone leaves with something running in your own environment and the pipeline to ship the next one.
- Format
- Remote or on-site
- Length
- 2 to 5 days
- Group size
- Up to 12
- Environment
- Your tenant
- Lead time
- From 3 weeks
Programmes
Starting points, all of them adaptable.
Pick the closest fit and we'll adjust the agenda to your stack before the first day.
Platform
5 programmes
Microsoft Copilot Studio
Copilot Studio Foundations — GitHub Copilot Harness
Build an agent that plans its own steps, reads documents and produces finished work — then prove, publish and cost it. No coding.
Learn more →Copilot Studio Practitioner — Standard Harness
Move a working agent to generative orchestration, extend it with your own connector, bound its sensitive actions, and prove it with a regression suite.
Learn more →Copilot Studio Practitioner— GitHub Copilot Harness
Split one agent into a front door and three specialists, share behaviour as a skill, fix the action that must not vary, and gate every release on evaluation.
Learn more →Copilot Studio Enterprise — Architecture, Scale & Governance
Govern an agent estate end to end: requirements, zones, enforced policies, a gated pipeline, a release gate, and monitoring that proves it. No agent-building required.
Learn more →
Platform
1 programme
Azure AI
Azure AI Foundations — Agents, Retrieval & Production
Build a grounded AI agent on Azure and take it to production: retrieval you tune, tools you define once, evaluation, identity and document-level security.
Learn more →A typical day
Short teaching, long building.
Roughly a third explanation, two thirds hands-on. People remember what they built, not what they watched.
09:30
Frame the problem
We start from something your team actually needs, not a pizza-ordering bot. The rest of the day builds towards it.
10:00
Teach the concept
Thirty to forty minutes, with the reasoning behind the design and the failure modes that come with it.
10:45
Build it
Everyone builds on their own. We circulate. Getting stuck is part of it — that's where the questions come from.
14:00
Break it
We deliberately break what was built: bad input, missing permissions, a flow that times out. This is the part most training skips.
16:30
Review and record
What was built, what broke, what to do differently. Written up and sent afterwards so it survives the week.
How it runs
Two ways to deliver it.
Remote
Half-day blocks across a week so nobody loses five full days. Recorded for anyone who misses a session, and a shared channel stays open for two weeks afterwards.
On-site
Full days at your office. Better for teams who need the platform, security and delivery people in one room — most of the useful arguments happen at the whiteboard, not in chat.
Before you ask
The practical questions.
What do we need in place beforehand?
A Copilot Studio licence for each attendee and a non-production environment they can build in. We send a short checklist a fortnight ahead and will talk to your platform team directly if access needs arranging.
Our team is mixed — developers and analysts. Is that a problem?
No, and it's usually better. The exercises have an optional deeper path for developers, and the design discussions benefit from people who know the business process rather than the platform.
Can you train more than twelve people?
We cap a hands-on group at twelve because beyond that we can't get round everyone while they build. For larger groups we run consecutive cohorts, which usually works out better anyway.
What happens after the last day?
You get the written summary, the labs, and the pipeline built during the course. A shared channel stays open for two weeks for follow-up questions.
Next step
Tell us about your team.
Roughly how many people, what they build today, and when you'd want to run it. We'll come back with a shape and a quote — no sales sequence.
Start the conversation