Workflow BlueprintsSERIES CM-WF · COPILOT STUDIO WORKFLOWS (PREVIEW)

Automation that can exercise judgment

Classic automation breaks the moment a step needs reading comprehension. Copilot Studio workflows fix that with three AI nodes: the prompt node (one model call), the agent node (an inline or published agent with tools and knowledge), and the M365 Copilot node (hand a step to Copilot, Researcher, or Analyst, grounded in the running user's work). Each blueprint below is a complete, buildable design.

runs in Copilot Studioconsumes Copilot Credits per actionagent node honors user permissions
membersintermediateagents: inline agent (Work IQ)

The Morning Briefing Machine

Every workday at 7:30 AM, a workflow lists your day's meetings, has an inline agent build a brief for each one using Work IQ, and delivers the stack to your inbox before your commute ends.

⚡ Schedule — weekdays 7:30 AM→List today's events (Outlook)→Loop: each meeting→Agent node (Work IQ)→Compose HTML brief→Send email + Teams card
outcome: Walk into every meeting already caught up — without spending the first 30 minutes of your day preparing.
membersadvancedagents: inline agent (product KB knowledge)

Ticket Triage with Judgment

A new Dataverse ticket fires a workflow that pulls customer history, has an agent node classify the ticket against your product KB, and routes it — P1s page on-call in Teams, everything else lands assigned with a draft reply waiting for human review.

⚡ Event — new row in Dataverse tickets table→Dataverse trigger (new ticket)→Get customer history→Agent node (structured output)→Branch on priority + confidence→Teams page (P1)→Assign + queue draft for review
outcome: Every ticket arrives pre-classified, pre-prioritized, and pre-drafted — with a human still holding the send button.
free demostarteragents: Researcher (via M365 Copilot node)

The Opportunity Research Pack

A new opportunity in your CRM triggers Researcher to build a one-page account brief — recent news, leadership, likely pain points, your history with them — attached to the record and posted to the seller's Teams before they've even noticed the lead.

⚡ Event — new opportunity in Dynamics 365 (or any CRM / SharePoint list)→D365 trigger (new opportunity)→M365 Copilot node (Researcher)→Attach brief to record→Post adaptive card to seller's Teams
outcome: Every new opportunity arrives with the research already done — sellers start at the conversation, not the Googling.
membersintermediateagents: inline agent (travel-policy knowledge)

Expense Review on Autopilot

Every submitted expense report gets its line items extracted by a prompt node, checked against the travel policy by an agent grounded on the policy SharePoint, and either auto-approved or routed to Approvals with the agent's per-line reasoning attached.

⚡ Event — expense report submitted→Expense submission trigger→Prompt node (line-item extraction)→Agent node (policy SharePoint)→Branch: all compliant?→Auto-approve + post to AP→Approvals with reasoning
outcome: Compliant reports clear in minutes; finance only ever sees the exceptions — with the reason each line was flagged already written.