Microsoft Copilot Studio
Build internal agents with Microsoft Copilot Studio
Build and test an agent that answers process questions using authorised documentation, with references, clear boundaries and a review the team can continue.
Before we begin
Corporate identity and authoring access in Microsoft Copilot Studio, an authorised practice environment and administrator support. Confirm licence, features, sources, permissions and usage. The free trial supports creating and testing, not publishing; licence purchases and tenant setup are not included.
Check identity, authoring, environment, features, policies, sources and usage. A free trial does not allow publishing. Uploaded files do not demonstrate individual SharePoint permissions: that needs prepared sources and test users. Classroom material does not connect real documents or change admin policies.
See preparation and terms →By the end you will be able to
- 01
Define an internal agent’s objective, useful questions, sources and boundaries.
- 02
Prepare authorised knowledge and check answers against references.
- 03
Handle clarification or routing without claiming actions the agent has not performed.
- 04
Test cases and gaps, and leave a handover with owners and conditions for possible publication.
What we will work on
An internal agent is useful when it knows which documentation to consult and where its task ends. Build a focused tool-and-access prototype, check references and leave a handover the team can use to continue the review.
01Scope the agent and prepare its knowledge
Questions, owners, currency and access. Create the agent and instructions for one process.
You will work on
- Choose recurring questions and exclude unauthorised actions.
- Review source versions, owners and access.
- Create instructions bounding the objective and knowledge gaps.
- Practice
- Create the scope and prepare a fictional guide, procedure and notes.
- How you will check it
- Initial agent and inventory with a version, owner and use for each source.
02Answer and recognise limits
Knowledge, references and clarification. Prepare a reviewable request when information or approval is missing.
You will work on
- Check each answer against its reference.
- Request essential details for an incomplete request.
- Leave a pending summary without claiming activation.
- Practice
- Answer questions and prepare a request without inventing missing details.
- How you will check it
- A checked answer and conversation with explicit gaps.
03Test, improve and prepare the handover
A short set, changes and individual evidence. Distinguish a prototype from operational publication.
You will work on
- Test answerable questions, gaps and out-of-scope requests.
- Update a source or instruction and repeat cases.
- Document dependencies, ownership and publication conditions.
- Practice
- Complete the set, resolve an individual variation and leave a handover.
- How you will check it
- A record and maintenance guide separating actual results from prepared examples.
Answer with a source and keep approval visible.
Classroom example with fictional data
Build a classroom agent to consult an internal tool guide and access-request process. Check references, missing details and an old instruction; prepare a summary pending review without creating accounts or granting permissions. Use fictional documentation and an agreed environment.
Fictional classroom case. Brisa has a current guide, a procedure and support notes. The agent helps find instructions and prepare requests; it does not create accounts or change permissions.
- Starting point
- “I need access for Atlas” does not identify the tool or its purpose.
- First reading
- Broad instructions assume access and confuse an old guide with the current one. This is a prepared answer for analysis, not a real execution.
- What we review
- Ask for the tool and purpose, consult the current source and keep approval pending. Route knowledge gaps without invention.
- Result
- The example leaves a reviewable summary with details or gaps, a procedure reference and no claimed activation.
Check before drawing conclusions.
Ask for the missing detail
Before review
“I need access for Atlas” becomes activation of an unspecified tool.
After review
“Which tool do you need and for what task? I will prepare a summary for review.”
The procedure requires tool, team and purpose. Clarification is not approval or execution.
Uploading a source does not validate it
A learning example, not a Studio execution. Guide v2 requires approval; v1 is archive.
| Check | Evidence | Decision |
|---|---|---|
| Currency | Inventory: v2 current, v1 archived | Do not add v1 as valid knowledge. |
| Answer | Reference to v2’s approval section | Correct an answer unsupported by its source. |
| Access | Source type and tested user | An uploaded file does not prove SharePoint permissions. |
Swipe to see all columns.
Repeat cases after a change and record what was actually checked.
What we cannot conclude
- Check a link against its content.
- Publication and user access require their own preparation.
Before calling it complete
- The current version is distinguished from the archive.
- Essential missing information is requested or kept pending.
- A person retains the approval decision.
Sessions to put it into practice.
Reference edition · 12 h live
Reference edition: 12 live hours across 6 sessions of 2 hours. Individual practice and short feedback take place in the sessions, without additional mandatory tasks.
- Session 12 h
Define and create the prototype
Agree task, questions, boundaries and owners; create the agent in the prepared environment.
By the endScope and initial instructions.
- Session 22 h
Prepare the knowledge
Review and add fictional sources; check the first answer and reference.
By the endAn inventory and checked answer.
- Session 32 h
Handle gaps and changes
Test an ambiguous question, missing details and an old instruction.
By the endRevised rules and a documented correction.
- Session 42 h
Prepare a reviewable request
Collect essential details and produce a summary pending approval. Do not grant access or send messages.
By the endA request with details or explicit gaps for human review.
- Session 52 h
Test and check again
Repeat cases after a change and check identity and sources where the environment permits.
By the endCase-level evidence and comparison.
- Session 62 h
Resolve and hand over
Individual variation and source, ownership and boundary documentation. Feedback in the session.
By the endIndividual evidence and handover; publication has separate conditions.
If your team needs to go further
- A Studio-specific programme, separate from everyday Copilot use in Microsoft 365.
- Licences, tenant setup, complex connectors, autonomy and production deployment require a separate scope.
- Publication and user access depend on licences, permissions, policies and their own tests.
An individual piece of work to close.
Configure a bounded prototype, check answers against sources and record an individual variation. Leave a handover with outstanding work; trainer review and feedback take place within the 12 hours.
Scope and prepare
- Pass
- Defines task, boundaries, current sources and owners in an authorised environment.
- Needs review
- Uses unreviewed documentation or leaves actions unbounded.
Answer with support
- Pass
- Checks references, asks for essential details and routes gaps.
- Needs review
- Cites an unsupported answer or invents details.
Test and correct
- Pass
- Records actual environment results, repeats the set and resolves an individual variation.
- Needs review
- Copies examples as executions or does not check the change.
Leave a handover
- Pass
- Documents ownership, sources, tested access and outstanding work.
- Needs review
- Promises deployment or permissions that were not tested.
The trainer reviews the task and explains the result within the agreed course time. Additional reassessment is agreed for each edition.
Learn with someone who develops projects for companies.

Borja Martínez
The Optimal Flow consultant
Over two years of experience developing projects for companies across industries and sizes.
We confirm the case, practice setup, dates and trainer availability when preparing each edition with your team.
Materials to practise and leave evidence.
Fictional sources and cases, blank templates and worked examples. Actual results are recorded during the edition.
- Practice guide and timings
- Fictional sources and identified archive
- Blank scope and inventory
- Initial and revised instructions
- Questions and expectations
- Blank test record
- Explained review example
- Blank handover
- Worked handover example
- Individual variation
- Assessment rubric
- Reference answers and checks
With guidance, practice and support.
Each delivery includes working materials, feedback on practical work and assessment against the agreed objectives.
Materials you can keep
Downloadable, versioned guides, exercises and review criteria for internal use.
To prepare and complete the delivery
A short recommendation, an editable communications kit and a group learning report.
TOF’s own certificate
A certificate of achievement after the agreed assessment. It is not a vendor certification.
A month of email support
On the content covered, up to two accumulated hours for the whole group.
Your team carries out the practice. Implementation services are agreed separately. See the scope →