Creating an agent in Microsoft Copilot Studio (formerly Power Virtual Agents) does not necessarily mean starting with a complex architecture. You do, however, need to understand what the agent does, what its tools do, and when a real action is triggered. Agent Academy offers missions that teach these distinctions through a practical scenario.
Agent Academy: Learn by building rather than reading a manual
Agent Academy is a series of exercises focused on creating agents in Microsoft Copilot Studio, a low-code platform that requires relatively little code. Available at aka.ms/agent-academy, it organises its missions into levels, including Recruit, Operator, and Commander, as well as special operations, or Special Ops. These let you explore a specific topic, such as MCP servers or agreement orchestration with DocuSign.
A mission provides an objective and instructions to follow in the tool. To choose where to start, distinguish between the progressive path, which is useful for learning the basics, and a special operation, which is better suited to someone already somewhat familiar with Microsoft Copilot Studio. Our overview of Copilot agent proficiency levels helps place this kind of exercise within a broader learning journey.
The site also provides an example of publishing content from Markdown, a lightweight markup language used in .md files. Its pages can be stored in a GitHub repository—a place to store and track files—and then presented with navigation, images, and callouts. Rendering a Markdown site and running an agent skill are two separate matters, however: using the same file format does not give them the same role.
Agent, workflow, skill, and MCP: Four distinct roles
An agent receives a request and chooses how to respond. Its orchestrator, the mechanism that coordinates its steps, can consult knowledge, use a skill, or call a tool. A workflow, by contrast, defines a sequence of actions whose steps can be identified.
MCP describes tools, not implicit authorisation
MCP, or “Model Context Protocol,” is a protocol for presenting tools and their usage context to an agent. Understanding a tool’s description does not mean the agent should be allowed to run it without controls.
| Term | What it is | What it is for |
|---|---|---|
| Agent | Assistant guided by an orchestrator | Interpret a request and coordinate a response |
| Workflow | Sequence of steps defined in the new experience | Link actions, AI actions, and handoffs to agents |
| Agent flow | Flow available with the standard harness | Run a process in the classic experience |
| Skill | Reusable instructions and resources | Guide a task when it becomes relevant |
| MCP server | Service that exposes described tools to the agent | Connect the agent to capabilities such as DocuSign’s |
This distinction helps avoid a common mistake: a skill explains how to handle a task, while a connected tool makes it possible to act on a service. Both can be involved in the same request, but they are not interchangeable.
The new Copilot Studio experience: What changes without requiring migration
The new experience is more than a different interface. It offers the GitHub Copilot harness, an orchestration engine, alongside the standard harness, the engine used by the classic experience. In June 2026, Microsoft described it as a “production-ready preview”: that dated description is not enough to establish the current status of every feature.
A terminology shortcut also needs correcting: workflows created with the GitHub Copilot harness are not simply agent flows under a new name. Microsoft Learn distinguishes between the two experiences and describes native artificial intelligence (AI) actions, handoffs to agents, and per-node testing for workflows. Our update on the GitHub Copilot harness reaching general availability in August 2026 helps track this development without assuming that every associated feature necessarily has the same status.
A new engine does not mean forced migration
Think “two available paths,” not “the old path has been removed.” Microsoft Learn explains how to return to classic agents and agent flows by turning off “New experience” on the home page or choosing “Other ways to build.”
For a team that already has classic agents, the right approach is therefore to compare the capabilities its project needs before choosing an experience. There is no reason to rebuild an agent solely because a new interface exists.
How a skill guides the agent without replacing its tools
Think of a skill as a folder of instructions that a colleague consults when a particular task comes up. An MCP tool is more like access to a service: it can, for example, ask DocuSign to prepare an agreement. The analogy stops at permissions: an agent may select an instruction or a tool based on the request, but that guarantees neither that its decision is correct nor that it is authorised to take the action.
A skill is not necessarily a single Markdown file. Microsoft Learn’s documentation on skills explains that it can bring together scripts, templates, and reference documents. These resources give the orchestrator a reusable method; the MCP server, meanwhile, exposes the operations of an external service.
In the agreement orchestration mission, a checklist skill can guide the preparation of a meeting after a document has been sent. In this scenario, the Work IQ calendar provides capabilities related to Microsoft 365 resources through Microsoft Graph, the interface for accessing those resources. Our analysis of the new Copilot Studio harness explores this distinction between orchestration, instructions, and actions further.
A practical example: Prepare a contract, collect signatures, schedule the next step
Consider this test scenario: an HR team wants to prepare a job offer for a fictional recipient, have it signed, and then arrange a follow-up meeting. DocuSign, an agreement management and electronic signature service, handles the document process. The agent provides an interface for preparing the request and coordinating the additional steps; it does not replace the DocuSign workflow.
Open the mission and prepare access
In Agent Academy, find the special operation dedicated to agreement orchestration. Arrange access to Microsoft Copilot Studio and a DocuSign environment suitable for testing. Use test identities and data: even a fictional address that actually receives invitations can have real-world effects.
Create the agent and give it a limited role
In the new experience, create an agent responsible for preparing offers. Describe its objective and ask it to summarise the details—recipient, position, and compensation—before anything is sent. Asking for confirmation is an operational control, not proof that the data is correct.
Connect the required capabilities
Add the DocuSign MCP server presented in the mission so the agent can identify and call the appropriate workflow. Then add the Work IQ calendar capability and the checklist skill if you want to test the follow-up meeting. Each addition broadens what the agent can attempt to do: check access before proceeding.
Test a request and confirm its details
In the agent preview, ask it to prepare a test contract, then check its summary. If the compensation is wrong, correct it before confirming. The preview lets you test the agent before publishing it, but it does not automatically turn a call to DocuSign into a mere simulation.
Check the results in each service
In the DocuSign workflow, check the web form, the fields carried over into the template, the resulting document, and the signature recipients, including the manager if the process calls for one. Separately check any calendar invitation and whether the document was stored in SharePoint, Microsoft 365’s document service, if that step was configured in the workflow.
The key point is how responsibilities are divided. The agent may decide to call a tool, while DocuSign runs its own form, document generation, and signature process. Requesting a meeting after sending the document does not, by itself, mean the meeting waits until all parties have signed.
Before publishing: Check actions, costs, and access
A successful conversational test does not prove that the business process is complete. Review tool calls and their results in the preview, then check the agreement’s status in DocuSign, the invitation recipients, and whether the document is in the intended location. The traces shown to the maker help diagnose execution; do not mistake them for a guarantee of full visibility into the model’s internal reasoning.
Consider costs before starting the exercises. Microsoft says that creating, testing, evaluating, and using agents that use the GitHub Copilot harness may consume Copilot Credits, the unit of consumption for agents since 1 September 2025. Its licensing documentation lists several ways to access Microsoft Copilot Studio, including a Microsoft 365 Copilot licence, a trial licence, or a maker role assigned in the Power Platform admin centre. Being able to open the tool does not mean every test is free of charge.
Finally, an MCP server gives the agent a selection of tools to call. Steve Goodman of Practical 365 recommends planning the security architecture before deploying MCP servers, particularly with third-party or internal integrations. For HR agreements, start by limiting access, controlling recipients, and retaining human approval before sending.
Frequently asked questions
Do I need to abandon classic agents and flows?
No. Microsoft still provides access to the classic experience and its agent flows. Choose the experience according to the capabilities you need, without assuming that an existing agent must be migrated.
Can I test the agent without publishing it?
Yes, the preview lets you try it before publishing. However, if the test calls a connected service such as DocuSign, check what was actually created or sent in that service.
Is a skill enough to send an agreement?
No. A skill provides instructions and possibly resources to the agent; sending depends on a tool and the corresponding access. In this scenario, those capabilities are exposed by the DocuSign MCP server.
Does a trial licence guarantee free missions?
No. Microsoft states that operations performed with agents using the GitHub Copilot harness may consume Copilot Credits, including during testing. Check the licence and expected consumption in your environment before running multiple tests.
Start with a controlled test
Before your first orchestration mission
- Choose a mission suited to your level and confirm which Copilot Studio experience you are using.
- Check access to Microsoft Copilot Studio, the DocuSign environment, and potential Copilot Credits consumption.
- Prepare test data and controlled recipients.
- Require confirmation of the details before sending, then verify the results in DocuSign, the calendar, and SharePoint.
If your only goal is to understand orchestration, start with a mission that involves no sensitive external action. If you test the DocuSign contract, make it a supervised exercise first: publishing can wait until access and every step of the process have been checked.
Further reading
- What’s new in Microsoft Copilot Studio — to check how the new experience is evolving.
- Compare Copilot Studio runtimes — to choose an engine based on the capabilities you need.
- Agent skills: How they work and what they contain — for a closer look at what a skill can include.
- Plan a secure MCP deployment in Copilot Studio — to assess risks before connecting tools.



