Copilot Studio: build a status-tracking agent
Microsoft Copilot Studio

Copilot Studio: build a status-tracking agent

by HubSite 365 about Microsoft

Software Development Redmond, Washington

Makers can combine Copilot Studio and Power Automate to collect structured project updates and trigger follow-up actions.

Key insights

  • The workshop example is a Status Tracker Agent for collecting blockers, risks, priorities, and dependencies.
  • Adaptive Cards and variables help capture structured information from users.
  • A Power Automate flow can process information submitted through the agent.
  • The source material does not state the licensing, rollout, or availability requirements.

Microsoft Copilot Studio can be used to build an agent that collects project updates, while Power Automate handles follow-up processing. This approach is relevant to makers and business teams who want to turn a repetitive information-gathering task into a guided interaction. Microsoft is the publisher of the Short associated with this maker journey, but its supplied transcript contains no spoken or demonstrated details.

What it does

Research notes describe Delia Zuniga’s work with Power Platform community members, including a workshop where participants built a Status Tracker Agent. The example collects details such as blockers, risks, priorities, and dependencies. It combines conversational agent design with structured inputs and an automation flow.

In this context, Copilot Studio is used to design the agent interaction, while Power Automate can take information collected by the agent and process it as part of a workflow. Adaptive Cards provide structured fields, and variables help manage the information collected. This gives makers a way to guide users through consistent questions rather than relying only on free-form updates.

Who it is for and what you need

The approach is aimed at makers and business subject-matter experts who understand a process and want to help shape a solution. The research notes say more than 70 people took part in the workshop, but do not establish that the tools or the specific workshop are available to every user.

No licensing requirements, tenant prerequisites, geographic limits, rollout stage, or preview status are stated in the supplied material. It also does not identify a particular Copilot Studio environment or Power Automate plan. Organizations considering a similar solution should verify those requirements for their own tenant rather than infer them from the example.

How it works

  1. Choose a process that needs consistent updates, such as gathering project status from contributors.
  2. In Copilot Studio, design the agent’s topics and prompts to guide users through the information required.
  3. Use Adaptive Card inputs and variables to capture fields such as blockers, risks, priorities, and dependencies.
  4. Connect the collected information to a Power Automate flow to process it or trigger a next step.

The notes describe these components in a workshop example, but do not provide exact menu paths, configuration screens, or a complete build procedure. Treat the steps as a high-level pattern, not a verified click-by-click guide.

Limitations and open questions

The available Short transcript is empty, and the supplied Microsoft website link is a general homepage rather than documentation for this configuration. The technical and workshop details come from the research notes, which refer to the YouTube source but do not provide a separate official technical reference. Licensing, governance controls, supported connectors, and deployment guidance are not verified here.

The notes recommend organizational governance for maker solutions, including permissions, data-protection guidance, lifecycle management, and IT oversight. They do not specify how to configure those controls. The example illustrates one agent-and-flow pattern; it does not establish a product change or a newly released feature.

Sources

Frequently asked questions

What can a Copilot Studio status-tracking agent collect?

The example described in the research notes collects blockers, risks, priorities, and dependencies. It uses structured inputs to gather those details.

Can Copilot Studio send agent responses to Power Automate?

The notes describe connecting the agent to a Power Automate flow so submitted information can be processed. They do not give connector or setup details.

What license do I need for this Copilot Studio and Power Automate approach?

The supplied material does not state licensing requirements or plan details. Check the applicable requirements for your environment before building.