Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Features in this article are powered by the GitHub Copilot harness, which uses Copilot Credits for usage-based billing. Learn more about Copilot Credits in Overview of billing for agents powered by the GitHub Copilot harness.
Usage-based billing applies to using, building, testing, and evaluating agents. These actions might consume Copilot Credits.
Agents powered by the GitHub Copilot harness in Microsoft Copilot Studio use natural language instructions, knowledge, and tools to help you build agents that can reason over context and take action. In this article, you create an agent, save it, and optionally update its primary language, solution, and schema name.
Sign in to Copilot Studio.
On the Home page, select the Agent tile.
Alternatively, select Agents in the side pane to go to the Agents page, and then select New Agent.
Your agent opens in the agent designer with the Build tab active and the name field in focus.
Enter a name for your agent in the name field.
Optionally, change the primary language, solution, and schema name for your agent.
Note
The last agent name you enter before the first save determines the schema name for your agent. Then, this unique system name used to reference the agent becomes read-only.
In the Instructions section, describe how the agent should behave, including its role, tone, and any rules or guidelines it must follow.
Select the Save
icon.If you skipped entering a name for your agent, a message appears prompting you for the name:
- Enter the name you want.
- Select Save.
The Share button, the Preview tab, and the Evaluate tab become available.
Change the primary language, solution, and schema name
Select the three dots (…) on the toolbar, and then select Settings. The Agent settings panel appears with its Agent details tab in focus.
Select the primary language you want for your agent.
Select the solution you want, if applicable.
Optionally, replace the default schema name with a more distinctive name. You can't change the first part of the schema name here: the selected solution determines this prefix.