Lead Infrastructure Engineer / Vice President | Microsoft MCT & MVP | Speaker & Blogger
Microsoft 365 Copilot Agent Builder adds skills, co-editing permissions and scheduled prompts, giving makers more ways to configure and reuse agents. These changes matter to employees building no-code agents and to the people who help manage or share them. Daniel Christian [MVP] demonstrates the updated workflow by building a business travel agent in Microsoft 365 Copilot.
Agent Builder lets users create an agent by describing its purpose in natural language or by configuring it manually. In the demonstration, the maker asks Copilot to create a travel concierge, then reviews the generated name, description and instructions. The agent uses an uploaded company travel policy as a reference for its recommendations.
The demonstrated changes affect how makers find the builder, add reference files and extend an agent with skills. They also change how a maker can share editing access and schedule a prompt to run again. These are practical additions to an agent-building workflow, rather than a change to which model the maker can select.
Agent Builder offers response choices such as Auto, Quick response and Think deeper in the demonstrated interface. The maker cannot select a specific model there. That distinction is useful for users comparing this experience with Copilot Studio, where the demonstrated model-selection controls are different.
The workflow is aimed at employees who want to create an agent without writing code, along with colleagues who will help maintain or use it. The example uses a travel policy PDF and two skills for itinerary planning and packing. It also uses calendar commitments in suggested prompts, illustrating how the maker can tailor an agent to a particular task.
The demonstration account has a Microsoft 365 E5 license and a Microsoft Copilot license. Treat that as the setup used for the example, not as a complete licensing guide. Makers should check their organization’s Copilot configuration and access before planning a rollout. The example starts at the Microsoft 365 Copilot home page.
Scheduling reuses a prompt with the agent that has already been configured, including its attachments and skills. For the travel example, a prompt requests a three-day client trip plan using calendar commitments and recommendations for flights, hotels and ground transportation. The response refers to the attached travel policy.
Skills require the exact filename SKILL.md when uploaded as an individual file; a differently named Markdown file produces an upload error in the demonstrated workflow. Alternatively, package the skill in a ZIP that includes SKILL.md, or use Create with chat to build the skill through a guided conversation.
Agent Builder does not provide a control to choose a specific model in the demonstrated interface. Makers can choose among the available response modes, including Auto, Quick response and Think deeper, but those choices are not model selection. Users who need a different level of agent-building control should distinguish this experience from Copilot Studio rather than assuming the same controls are available.
Sharing an agent also means deciding who can change it and who can only chat with it. Review the selected people and access level before adding them, especially before enabling organization-wide chat access. The workflow’s scheduled prompt is based on a prompt already run with the configured agent, so check the wording and schedule before saving.
Switch to Chat, select Plugins in the left navigation, and choose New agent. The option may not appear while Work is selected.
Upload a file named SKILL.md or a ZIP package that includes SKILL.md. You can also create a skill through the Create with chat option.
Yes. The demonstrated Share options include Edit access for a co-editor and Can chat access for someone who only uses the agent.
Run the prompt with the agent, open the response’s ellipsis menu, choose Schedule this prompt, review the schedule and save it.