Copilot StudioIntermediate30 minDay 4 · Nov 3, 2026

Give your agent a tool that takes action

Move from answering questions to doing work. Add a tool that creates a task or posts to Teams, and require confirmation before it acts.

Today's task

Upgrade the Team Helpdesk agent you built in Ground your agent in SharePoint so it can log a request for the user. When someone asks for a new laptop, the agent collects the details and creates a task (in Planner, a SharePoint list or a Teams channel post) for the office manager.

Steps

Heads-up: Microsoft updates Copilot Studio often and offers more than one authoring experience. If your screens look different from these steps, look for the same settings by name.

  1. Open your agent and go to its Tools (earlier versions of Copilot Studio called these Actions).
  2. Add a tool using a connector. Good first choices:
    • Create a task in Microsoft Planner
    • Create item in a SharePoint list
    • Post message in a Teams channel
  3. Define the inputs the tool needs, such as requester name, item requested and business reason. Give each input a clear description, because the agent uses those descriptions to know what to ask for.
  4. Describe when to use the tool. For example:

    Use this when an employee wants to request new equipment. Collect the item and a business reason first.

  5. Turn on confirmation. In the tool's settings, set Ask the end user before running to Yes. It defaults to No, so the agent would otherwise act without asking.

  6. Test it: "I need a new monitor, mine flickers." Watch the agent ask for missing details, confirm, and create the task.

What to notice

  • Good descriptions matter. The model decides when and how to call tools based on their names and descriptions. Vague descriptions lead to wrong calls.
  • Every tool has an identity behind it. Check the tool's Authentication setting. End user (the default) runs the tool as each person using the agent. Maker-provided runs it as the connection owner for everyone, so if that's you, every request is created with your access. If you use Maker-provided, connect with a dedicated, least-privilege service account.

Governance tip: Confirmation is your first guardrail for any action with consequences, such as sending messages, changing records or anything involving money. Leave it on until you've watched the agent behave correctly many times.

Go further

Rather have it built?

We build and govern Microsoft AI agents for businesses like yours.

If you'd rather skip the learning curve, Louder IT designs, builds and runs agents in Copilot Studio and Azure, with guardrails included.