Add new post: Agents and Workflows in Copilot Studio - Three Integration Patterns by jpad5 · Pull Request #310 · microsoft/mcscatblog

jpad5 · 2026-06-01T15:20:01Z

Summary

New post: Agents and Workflows in Copilot Studio: Integration Patterns That Actually Hold Up in Production
Walks the three canonical patterns (Reasoning-in-the-Loop, Conversation-First Automation, Fire-and-Follow-up), covers the new Workflows designer (preview) with Classify and Human review nodes, and ends with a contract-first expense-report scenario.
Adds header SVG, expense architecture SVG, and Workflows designer screenshots under assets/posts/agents-workflows-integration-patterns-production/.

Checklist

Ran review pass and addressed feedback
Local server renders correctly (bundle exec jekyll serve -l --future)
All images have alt text and captions
Internal links to related posts (combining-agent-flows gotchas, child/connected agents, human-in-the-loop custom connector)
Tags chosen for Chirpy "Further Reading" overlap (copilot-studio, agent-flows, workflows, classify-node, human-review, architecture)

- Scope article to MCS context; clarify target audience - Add MCS-specific architecture diagram showing PP connector layer - Fix auth comparison: in MCS both use same connector/connection framework - Correct DLP claim: DLP applies at connector level, MCP tools may be ungoverned - Fix performance claims: MCP adds tool discovery overhead in MCS - Fix control level: makers cannot override MCP tool descriptions in MCS - Add orchestration delegation tradeoff - Rewrite conclusion with MCS-specific guidance

…n for Copilot Studio

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Agent-Logs-Url: https://github.com/microsoft/mcscatblog/sessions/856073da-077c-4d90-880f-fbc7064b52f1 Co-authored-by: jpad5 <94862471+jpad5@users.noreply.github.com>

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Agent-Logs-Url: https://github.com/microsoft/mcscatblog/sessions/03832e33-a332-4d70-a41e-ae2f24065683 Co-authored-by: jpad5 <94862471+jpad5@users.noreply.github.com>

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…rt 2

- Replace simulated Copilot Studio calls with real CopilotClient SDK code - Split single 40-line code block into two focused OBO exchange sections - Add dual OBO flow explanation (Power Platform API + Enterprise API) - Update Program.cs wiring to show CopilotClient SDK registration - Remove redundant CopilotClient SDK Integration section - Add 3rd internal link (connector-consent-card-obo) - Replace sso tag with m365-agents-sdk for better Further Reading overlap - Remove [Demo] prefix from title - Reduce em-dash overuse throughout

…tterns That Actually Hold Up in Production

…ately)

ChrisGarty · 2026-06-02T17:48:26Z

+> **Trigger choice picks identity.** Manual runs as the invoking user, Recurrence runs as the workflow owner, Connector/HTTP runs as the configured connection, and agent-call runs as the conversation user. Match the trigger to the identity you actually want crossing the first boundary; this is one of the easiest things to get wrong, and one of the hardest to debug after the fact.
+{: .prompt-tip }
+
+The patterns below are *designer-agnostic*. Wherever I say "agent flow," you can read it as "agent flow or workflow." Where the new designer changes the picture in a meaningful way, I'll call it out inline.


@jpad5 , high level problems I see: flows vs agent flows vs workflows is not differentiated enough; mixture of "agent flow" and "workflow" terminology used e.g. "Pattern 2: Conversation-First Automation (agents that call agent flows)"; new workflow designer is part of the discussion which causes the patterns commentary to be not as clear as it could be.

I'm super-sympathetic to the problem I'm highlighting here, because I've wanted to provide some "deterministic vs generative" commentary and it is really difficult right now. I've been holding back on similar posts.

Here are some suggestions...

Either focus on workflows:

Focus on rebranding of flows (cloud flows + agent flows) as "workflows"

Explain new workflow designer as a new way to build a workflow (while the others remain) with new capabilities like inline agent definition and calling

Focus on new workflows from then on: don't mention agent flows, don't mention flows, only workflows

Explain patterns

Or focus on agent flows:

Briefly mention that new workflow designer is a way to build workflows, but explain that workflows are only in preview, so you are focusing on agent flows.

Or perhaps both, but put workflows in a specific section:

Focus entirely on agent flows for the majority of the post since that is all possible in production now.

Then add a section at the end that describes how that commentary is going to change with new workflows: Agent nodes incline, M365 Copilot node, Human in the loop, etc.

What do you think?

github-actions · 2026-06-03T12:31:12Z

Blog preview check passed for 6e6455a.

The Jekyll site compiled successfully and generated previews for the newly added post.

\_posts/2026\-06\-02\-agents\-workflows\-integration\-patterns\.md -> /mcscatblog/posts/agents\-workflows\-integration\-patterns/

Preview artifacts:

Rendered HTML: download artifact
Screenshots: download artifact

Open the workflow run

- Rename _posts file and asset folder: drop '-production' suffix - Restructure intro: hook, LLM-boundary thesis, scope note merged with terminology - Standardize on 'workflow' (vs 'flow' as a noun) throughout - Add Pattern 3 callback wiring detail, idempotency warning, sample payloads - Add decision-matrix table, inline-vs-existing agent guidance, agent vs prompt node table - Tighten expense walkthrough with employee dialogue and color-key legend - Reduce em-dash density; trim redundant captions - Tags: add agent-node, agent-flows for better Chirpy Further Reading overlap - Add generator scripts under tools/ for header and expense-architecture SVGs

jpad5 · 2026-06-03T20:31:19Z

Pre-merge polish pass applied:

Structural

Renamed post file and asset folder to drop -production suffix.
Restructured intro: tightened hook, merged terminology note into the audience callout to avoid back-to-back info callouts.
Standardized on workflow (vs flow) as a noun throughout the body.
Trimmed redundant caption in §3 (Support Email Triage).

Section 5 (Fire-and-Follow-up)

Added explicit callback wiring breakdown (outbound + async worker + inbound HTTP-trigger workflow).
Added sample synchronous-ack and async-callback JSON payloads in a collapsible <details> block.
Added idempotency warning and Fire-and-Forget anti-pattern callout.

Section 7 (Decision framework)

Added agent node vs prompt node capability comparison table.
Added inline vs existing agent rule of thumb.

Section 8 (Expense walkthrough)

Added employee-facing dialogue to show user-visible UX before architecture.
Added color-key legend mapping diagram colors to the LLM boundary.
Tightened red-bullet copy on Human review; preserved link to companion post on custom-connector approval shapes.

Front matter

Final description: "Agents think. Workflows execute. Together they deliver more than either can alone — three patterns for pairing them in Copilot Studio, plus a decision matrix."
Added tags agent-node and agent-flows for stronger Chirpy "Further Reading" overlap with the companion gotchas post.

Tooling

Added tools/gen_header.py and tools/gen_expense_arch.py (SVG generators for the header and architecture diagrams).

Em-dash sweep

Reduced em-dash density in body prose; kept idiomatic uses (description, parenthetical aside, stage directions in dialogue).

…inology consistency

…tency

…rand note, drop trigger UI hedge

…coexist (not a rename)

jpad5 and others added 19 commits March 26, 2026 18:55

Add new post: [Demo] Your Service, Your Auth: The Hosted Agent Patter…

1ca14ff

…n for Copilot Studio

Remove draft post: compare-mcp-servers-pp-connectors-v2

a799132

Update _posts/2026-03-26-hosted-agent-service-pattern.md

5a26b59

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update _posts/2026-03-26-hosted-agent-service-pattern.md

d8a53ae

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update _posts/2026-03-26-hosted-agent-service-pattern.md

2bc1451

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Fix intro wording: clarify what dev controls vs Copilot Studio controls

1161e64

Agent-Logs-Url: https://github.com/microsoft/mcscatblog/sessions/856073da-077c-4d90-880f-fbc7064b52f1 Co-authored-by: jpad5 <94862471+jpad5@users.noreply.github.com>

Update _posts/2026-03-26-hosted-agent-service-pattern.md

2d8af86

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update _posts/2026-03-26-hosted-agent-service-pattern.md

fdfd4c1

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update _posts/2026-03-26-hosted-agent-service-pattern.md

9528e3f

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Fix title: align to 'Hosted Agent Service Pattern' used throughout post

01cf5a9

Agent-Logs-Url: https://github.com/microsoft/mcscatblog/sessions/03832e33-a332-4d70-a41e-ae2f24065683 Co-authored-by: jpad5 <94862471+jpad5@users.noreply.github.com>

Update _posts/2026-03-26-hosted-agent-service-pattern.md

3c2ff37

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Resolve merge conflict: keep PR version of overview section

eb44896

Add Part 1 framing and What's Next section teasing Agent Framework Pa…

1b56845

…rt 2

Merge remote-tracking branch 'origin/main' into jpad5-4

d101bc4

Merge remote-tracking branch 'origin/main' into jpad5-5

2ddaf9f

Add new post: Agents and Workflows in Copilot Studio - Integration Pa…

e943482

…tterns That Actually Hold Up in Production

Remove hosted-agent-service files from this PR (will be handled separ…

b21a28b

…ately)

ChrisGarty self-requested a review June 2, 2026 17:45

ChrisGarty requested changes Jun 2, 2026

View reviewed changes

Change date to trigger compilation

781aa31

jpad5 added 2 commits June 3, 2026 13:52

Fix expense architecture diagram: 'Agent Flow' -> 'Workflow' for term…

8d37551

…inology consistency

Apply editorial review: terminology consistency and legend cleanup

08070f3

jpad5 changed the title ~~Add new post: Agents and Workflows in Copilot Studio - Integration Patterns That Actually Hold Up in Production~~ Add new post: Agents and Workflows in Copilot Studio - Three Integration Patterns Jun 3, 2026

jpad5 added 2 commits June 3, 2026 14:03

Audience callout: flow-first -> workflow-first for terminology consis…

1dd26ab

…tency

Tighten workflows-first framing: simpler audience callout, single reb…

40c8d28

…rand note, drop trigger UI hedge

Fix workflow terminology callout: agent flows GA + workflows preview …

6e6455a

…coexist (not a rename)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add new post: Agents and Workflows in Copilot Studio - Three Integration Patterns#310

Add new post: Agents and Workflows in Copilot Studio - Three Integration Patterns#310
jpad5 wants to merge 26 commits into
mainfrom
jpad5-5

jpad5 commented Jun 1, 2026

Uh oh!

ChrisGarty Jun 2, 2026

Uh oh!

github-actions Bot commented Jun 3, 2026 •

edited

Loading

Uh oh!

jpad5 commented Jun 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

jpad5 commented Jun 1, 2026

Summary

Checklist

Uh oh!

ChrisGarty Jun 2, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jpad5 commented Jun 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

github-actions Bot commented Jun 3, 2026 •

edited

Loading