"Copilot" names three different products. GitHub Copilot is the coding agent. Microsoft 365 Copilot is chat and Agent Builder for Q&A over M365 data. Copilot Studio — at copilotstudio.microsoft.com — is where Microsoft enterprise loop engineering actually runs on schedules and connector events.
This post is the Studio map: Workflows, autonomous agents, and agent flows. It hangs off the loop-engineering hub, not a rewrite of it.
TL;DR — which Studio loop do you want?
| Question | Answer |
|---|---|
| Where do standing loops live? | Copilot Studio — not M365 Copilot chat, not GitHub Copilot CLI. |
| New default for background work? | Workflows — trigger → steps; add an agent node when a step needs reasoning. |
| Chat-first agent that also acts alone? | Autonomous agents with event triggers (schedule or connector). |
| Deterministic automation? | Agent flows — recurrence or instant trigger, rule-based path. |
| Inner reasoning loop? | Generative orchestration — LLM plans tool/topic/knowledge steps per user or autonomous turn. |
| Survives laptop closed? | Yes (cloud service). |
| Developer coding loops? | Use GitHub Copilot instead. |
Sister harness guides: Claude Code · Cursor · Codex CLI · M365 Copilot limits
The three clocks in Copilot Studio
Microsoft's own autonomous agents guidance describes agents that perceive events, decide, and act without a user prompt. In practice Studio gives you three outer clocks:
| Layer | What it is | Best for |
|---|---|---|
| Generative orchestration | LLM-driven planning inside a conversational or triggered agent | Multistep answers with tools, topics, knowledge, child agents |
| Workflows | Event-driven automation; optional agent node per step | "When X happens, do Y" across M365 and 1,500+ connectors |
| Agent flows | Deterministic trigger → actions (classic Power Automate-style harness) | Predictable recurrence, approvals, human-in-the-loop |
The inner agent loop is the same observe-act-check cycle as any coding agent: the model picks the next tool or topic step until a stop condition. Studio's contribution is triggers, connectors, governance, and capacity billing — the agent harness for business process, not repos.
Official references: Workflows overview (MCS labs), Flows overview, Generative orchestration.
Step 1: Create a scheduled Workflow (copy-paste instructions)
Workflows are the pattern Microsoft highlights for recurring background work — e.g. triage new To Do items, summarize a queue, post to Teams.
In Copilot Studio (UI path)
- Open Copilot Studio → Workflows → New workflow.
- Trigger: choose Recurrence (daily / hourly / custom cron-style schedule) or a connector event (new email, Dataverse row, Teams message, etc.).
- After the trigger, select + → Agent to add an inline agent node when the step needs judgment (not fixed branching).
- In the agent instructions, paste a goal with a verifiable stop — same discipline as loop engineering:
For each item in the trigger payload:
1. Read title, body, and requester.
2. Classify as billing / support / sales-other.
3. If billing, create a case in Dataverse with priority from keywords.
4. If uncertain, post a one-line summary to the Finance Teams channel and stop.
Do not mark complete until the case ID or Teams message ID is written to the run log.
- Add connector actions after the agent (Update row, Post message, Request approval).
- Test with sample trigger data, then Publish.
Why an agent node: Microsoft's Workflow labs describe the inline agent as non-deterministic — it reasons over trigger data and picks tools — wrapped in a deterministic workflow skeleton. That is Studio's version of "cron plus a decision-maker."
Step 2: Autonomous agent with an event trigger
For agents that already chat and should wake themselves:
- Open your agent → Triggers (or Autonomous / event triggers in generative orchestration).
- Add Scheduled or When an event occurs (Dataverse, email, webhook).
- Scope instructions narrowly — Microsoft's autonomous guidance warns against agents that "wander" without explicit authority boundaries.
- Set human approval on high-stakes actions (send external email, delete records).
Copy-paste trigger instruction template:
Trigger: every weekday at 08:00 UTC.
Goal: scan the Support queue for tickets older than 24h without an owner.
Actions allowed: assign owner from on-call roster, add internal note, escalate to P2 if VIP tag.
Stop when queue has zero unowned tickets older than 24h or after 20 ticket updates.
Never send customer-facing email without approval action.
Generative orchestration docs list event triggers as autonomy mechanisms that start the orchestrator without a user message — the Studio equivalent of Cursor Automations or Claude Code /schedule.
Step 3: Agent flow on a recurrence (deterministic loop)
When you do not need LLM judgment every step — same input → same path — use an agent flow:
- In Copilot Studio (standard harness), create an agent flow.
- Trigger: Recurrence or When another agent calls this flow.
- Actions: connectors, Human in the loop approval, Loop control (apply to each), child flows.
- Monitor in run history; each action consumes Copilot Studio capacity.
Agent flows are explicitly deterministic: Microsoft states the same input produces the same output. Use them for approvals, notifications, and ETL-shaped work; use Workflows + agent nodes when classification or summarization belongs in the loop body.
Guardrails (production)
Same loop engineering stops as coding harnesses, different surface:
| Guardrail | Studio implementation |
|---|---|
| Iteration cap | Limit items in Apply to each; split large queues across runs |
| No-progress detection | Compare run outputs in analytics; alert on identical failure reason |
| Budget ceiling | Capacity planning per environment; throttle recurrence |
| Human gate | Approval action before external send or record delete |
| Scope | Separate dev / test / prod environments; RBAC on connectors |
Microsoft's April 2026 Copilot Studio blog also highlights agent-to-agent delegation and MCP-enabled tools (preview) inside workflows — treat preview features as non-production until your admin enables them.
What this means for what you build or pay
| Choice | Build impact | Pay impact |
|---|---|---|
| Workflow + agent node | You ship business automation without a custom cron service | Capacity per action × recurrence frequency |
| Autonomous trigger on chat agent | One agent serves desk and overnight triage | Higher capacity burn; needs monitoring |
| Agent flow only | Cheapest predictable automation | Lower LLM spend; less flexible |
| Stay on Agent Builder | No standing loop — see M365 Copilot guide | M365 Copilot license only |
If your loop touches code in a repo, use GitHub Copilot or Claude Code. If it touches tickets, email, Teams, CRM, Studio is the correct harness.
Related reading
explainx.ai
- How to run loops in Microsoft 365 Copilot — what chat and Agent Builder cannot schedule
- How to run loops in GitHub Copilot — developer Autopilot and
/every - Loop engineering hub
- GitHub Copilot: 87% agent-initiated calls — that paper is GitHub only, not Studio
- Claude Code vs Cursor vs GitHub Copilot
- /loops · Loop Engineering course
Microsoft documentation
- Autonomous agents in Copilot Studio
- Generative orchestration
- Flows overview
- M365 Copilot vs Copilot Studio feature comparison
Dictionary: Copilot Studio · loop engineering · agent loop · Copilot
Workflow and trigger names reflect Microsoft Copilot Studio documentation as of August 2026. Preview features (MCP tools, agent-to-agent) may change; verify in your tenant before production rollout.