Power Automate Is Dead: The AI Workflows Agent That Replaced Your Job

1
00:00:00,000 --> 00:00:02,320
You think Power Automate is safe, it isn't.

2
00:00:02,320 --> 00:00:06,160
Workflow's agent just ate its lunch while you were still dragging connectors like it's 2019.

3
00:00:06,160 --> 00:00:07,160
The truth?

4
00:00:07,160 --> 00:00:12,880
Conversational, intent-driven automation beats rigid, designer-driven flows for most everyday work.

5
00:00:12,880 --> 00:00:14,920
Say what you want, get the workflow move on.

6
00:00:14,920 --> 00:00:16,800
No 47 click schema massage.

7
00:00:16,800 --> 00:00:20,040
You'll get a side-by-side reality check, not marketing,

8
00:00:20,040 --> 00:00:25,120
will measure, build time-saved, error reduction, governance impact, and licensing cost.

9
00:00:25,120 --> 00:00:28,520
And yes, we'll talk DLP, auditability environments, and approvals.

10
00:00:28,520 --> 00:00:29,400
Calm down.

11
00:00:29,400 --> 00:00:32,120
If you cling to cloud flows after this, that's a choice.

12
00:00:32,120 --> 00:00:33,040
An expensive one.

13
00:00:33,040 --> 00:00:35,400
Let's define the lanes before we raise.

14
00:00:35,400 --> 00:00:36,240
Baseline.

15
00:00:36,240 --> 00:00:39,960
What workflows agent actually is versus Power Automate?

16
00:00:39,960 --> 00:00:45,920
OK, so basically, Workflow's agent lives inside Microsoft 365 co-pilot.

17
00:00:45,920 --> 00:00:51,080
Frontier label means early, English first, changing under your feet, directional, not-cordroom evidence.

18
00:00:51,080 --> 00:00:54,840
It's an agent that turns natural language into automations across outlook teams,

19
00:00:54,840 --> 00:00:56,840
SharePoint, Planner, and Microsoft Graph.

20
00:00:56,840 --> 00:00:58,360
You describe the outcome?

21
00:00:58,360 --> 00:00:59,640
It assembles the steps.

22
00:00:59,640 --> 00:01:01,120
It's not the Power Automate designer.

23
00:01:01,120 --> 00:01:02,600
It's not pretending to be.

24
00:01:02,600 --> 00:01:09,280
Think of Power Automate as a LEGO kit, structured, deterministic, every brick placed by your meticulous, over-caffeinated hands.

25
00:01:09,280 --> 00:01:13,280
Think of Workflow's agent as an assistant who hears "Build me a carport, grab standard parts,

26
00:01:13,280 --> 00:01:15,880
and has it standing before you finish your latte."

27
00:01:15,880 --> 00:01:18,640
Will it match your exact architectural blueprint?

28
00:01:18,640 --> 00:01:19,320
Not yet.

29
00:01:19,320 --> 00:01:21,000
Will it shelter the car by lunch?

30
00:01:21,000 --> 00:01:22,000
Yes.

31
00:01:22,000 --> 00:01:25,000
Core distinction that most average users miss.

32
00:01:25,000 --> 00:01:28,000
Workflow based AI versus Agentec AI.

33
00:01:28,000 --> 00:01:31,320
Today, Workflow's agent behaves like AI-accelerated workflows.

34
00:01:31,320 --> 00:01:35,840
It understands intent, composes a sequence, and runs it with context from Graph.

35
00:01:35,840 --> 00:01:39,320
Full autonomous, multi-hour, self-healing, multi-agent sagas?

36
00:01:39,320 --> 00:01:42,160
That's the roadmap, not the Tuesday morning reality.

37
00:01:42,160 --> 00:01:43,440
What it can do now.

38
00:01:43,440 --> 00:01:49,360
Trigger on common events, read outlook, post to teams, write to SharePoint lists, create planner tasks,

39
00:01:49,360 --> 00:01:53,480
pull a manager via Graph and run embedded AI steps for summarize classify.

40
00:01:53,480 --> 00:01:55,320
It can test and show activity history.

41
00:01:55,320 --> 00:01:57,200
It handles the basics quickly.

42
00:01:57,200 --> 00:01:59,480
The edit surface is intentionally thin.

43
00:01:59,480 --> 00:02:02,680
You steer with words, not with 18 nested pains.

44
00:02:02,680 --> 00:02:04,000
What it can't do yet?

45
00:02:04,000 --> 00:02:07,120
Complex branching with five parallel approvals, long-running SLA's,

46
00:02:07,120 --> 00:02:10,320
deep connector breadth across hundreds of third-party systems,

47
00:02:10,320 --> 00:02:14,560
and visual debugging that shows you every variable's miserable little life.

48
00:02:14,560 --> 00:02:17,160
Also, when the agent triggers external actions,

49
00:02:17,160 --> 00:02:19,920
you're working under a hundred-second return window.

50
00:02:19,920 --> 00:02:23,080
Translation, don't chain attacks audit licensing reality

51
00:02:23,080 --> 00:02:25,080
because someone will ask by slide three,

52
00:02:25,080 --> 00:02:29,280
Power Automate is per user or per flow, predictable, but it adds up at scale.

53
00:02:29,280 --> 00:02:32,040
Workflow's agent sits with co-pilot and co-pilot studio

54
00:02:32,040 --> 00:02:34,200
leaning on message-based consumption.

55
00:02:34,200 --> 00:02:37,480
If you already bought co-pilot for knowledge workers who live in chat,

56
00:02:37,480 --> 00:02:40,360
the marginal cost of agent-built workflows trends down.

57
00:02:40,360 --> 00:02:43,680
If you're automating the entire back office with hundreds of headless flows,

58
00:02:43,680 --> 00:02:46,200
traditional power automate still pencils out.

59
00:02:46,200 --> 00:02:48,000
Governance and auditability.

60
00:02:48,000 --> 00:02:48,680
Breathe.

61
00:02:48,680 --> 00:02:51,480
Agent activity shows up in admin usage reports.

62
00:02:51,480 --> 00:02:55,800
DLP applies, align co-pilot agent policies with power platform DLP

63
00:02:55,800 --> 00:02:58,920
so you don't spray data across tenants like a broken sprinkler.

64
00:02:58,920 --> 00:03:02,320
Environments remain your friend, ring fans dev, test,

65
00:03:02,320 --> 00:03:04,960
prod, restrict who publishes agents.

66
00:03:04,960 --> 00:03:05,920
Approvals?

67
00:03:05,920 --> 00:03:08,920
Short, human in the loop decisions are fine in the agent lane,

68
00:03:08,920 --> 00:03:12,680
long-running approvals with escalations and SLA's belong in power automate.

69
00:03:12,680 --> 00:03:15,040
It's not purity, it's physics.

70
00:03:15,040 --> 00:03:16,720
Roadmap signals matter.

71
00:03:16,720 --> 00:03:20,160
Co-pilot studio extensibility lets you wire custom connectors

72
00:03:20,160 --> 00:03:23,160
call enterprise systems like SAP or ServiceNow

73
00:03:23,160 --> 00:03:25,040
and orchestrate multiple agents.

74
00:03:25,040 --> 00:03:28,560
Admin analytics are expanding so you can stop guessing and start pruning.

75
00:03:28,560 --> 00:03:32,560
Multi-agent coordination is coming, which is where assistant becomes team.

76
00:03:32,560 --> 00:03:34,720
Here's the simple version because you need one.

77
00:03:34,720 --> 00:03:38,840
Workflow's agent equals intent to automation for common Microsoft 365 work.

78
00:03:38,840 --> 00:03:42,800
Power automate equals enterprise grade, durable automation for complex,

79
00:03:42,800 --> 00:03:44,480
long-running, governed processes.

80
00:03:44,480 --> 00:03:47,920
The counter-intuitive part, fewer knobs mean fewer places to break.

81
00:03:47,920 --> 00:03:49,400
Yes, fewer.

82
00:03:49,400 --> 00:03:52,440
Your habit of overtuning every toggle is not a virtue.

83
00:03:52,440 --> 00:03:53,720
It's a failure mode.

84
00:03:53,720 --> 00:03:57,000
Remember this detail, it's going to matter when we time the laps.

85
00:03:57,000 --> 00:04:01,040
Agent is faster to build and safer against configuration drift.

86
00:04:01,040 --> 00:04:05,280
Power automate is stronger at runtime resilience and forensic clarity.

87
00:04:05,280 --> 00:04:08,080
Now that you know the rules of the track, let's run the laps.

88
00:04:08,080 --> 00:04:09,680
Use case one approvals.

89
00:04:09,680 --> 00:04:12,360
Clicky click versus say it and ship it.

90
00:04:12,360 --> 00:04:13,560
Why this matters?

91
00:04:13,560 --> 00:04:17,760
Approvals are everywhere, purchase orders, content publishes, policy exceptions,

92
00:04:17,760 --> 00:04:22,360
every hour of delay is a tax you pay because someone somewhere is babysitting a form.

93
00:04:22,360 --> 00:04:25,880
The difference between approved in minutes and approved by next Tuesday

94
00:04:25,880 --> 00:04:28,280
is usually how many knobs you insist on turning.

95
00:04:28,280 --> 00:04:30,760
What we're building, single-approval, simple routing,

96
00:04:30,760 --> 00:04:32,920
and a confirmation back to the requester.

97
00:04:32,920 --> 00:04:35,720
No committee, no escalations, no legal review.

98
00:04:35,720 --> 00:04:38,920
Just the daily yes, no that gums up your calendar.

99
00:04:38,920 --> 00:04:41,000
Power automate first, you add a trigger.

100
00:04:41,000 --> 00:04:45,000
When an item is created or when a requester arrives, you map fields,

101
00:04:45,000 --> 00:04:47,280
you drop in and start and wait for an approval.

102
00:04:47,280 --> 00:04:50,040
You pick approved reject, first to respond.

103
00:04:50,040 --> 00:04:54,240
You wire conditions, add reminders because humans ghost, sprinkle variables.

104
00:04:54,240 --> 00:04:57,760
Then you test catch a failed schema because the title field got renamed,

105
00:04:57,760 --> 00:04:59,200
fix it and redeploy.

106
00:04:59,200 --> 00:05:02,040
It works, it's deterministic, it's also brittle,

107
00:05:02,040 --> 00:05:04,360
any list change, any content type tweak,

108
00:05:04,360 --> 00:05:06,680
and your perfect little contraption, solx.

109
00:05:06,680 --> 00:05:08,440
Enter workflows agent, you say,

110
00:05:08,440 --> 00:05:11,800
when a new request arrives in the SharePoint list at this URL,

111
00:05:11,800 --> 00:05:15,400
ask Alex to approve, then email me the result and comment.

112
00:05:15,400 --> 00:05:19,240
The agent reads your intent, grabs a trigger, queries graph for Alex,

113
00:05:19,240 --> 00:05:23,160
composes the approval, sends the notification and shows you a test run.

114
00:05:23,160 --> 00:05:25,640
No pains for lunging, no schema diff anxiety.

115
00:05:25,640 --> 00:05:28,800
You steer with words, refine with words, test with a click.

116
00:05:28,800 --> 00:05:29,760
Build time.

117
00:05:29,760 --> 00:05:33,880
Agent wins by minutes, sometimes hours because the added surface is conversation,

118
00:05:33,880 --> 00:05:35,240
not a UI labyrinth.

119
00:05:35,240 --> 00:05:39,240
You'll get a working path faster than you can argue about which approval flavor to pick.

120
00:05:39,240 --> 00:05:44,160
The truth, most of you overbuilt approvals because the designer tempts you with options.

121
00:05:44,160 --> 00:05:47,320
The agent simply refuses to enable your tinkering habit.

122
00:05:47,320 --> 00:05:51,920
Error surface, power, automate collapses, runtime errors with explicit rules,

123
00:05:51,920 --> 00:05:54,960
but it expands configuration errors, field mismatches,

124
00:05:54,960 --> 00:05:58,880
missing connections, renamed columns, workflows.

125
00:05:58,880 --> 00:06:02,440
Agent narrows configuration errors because you aren't binding every field.

126
00:06:02,440 --> 00:06:04,000
It composes the glue for you.

127
00:06:04,000 --> 00:06:05,840
Fewer knobs, fewer misalignments,

128
00:06:05,840 --> 00:06:08,520
and yes, average user, that's good governance fit.

129
00:06:08,520 --> 00:06:12,120
DLP still applies, align co-pilot agent and power platform policies,

130
00:06:12,120 --> 00:06:15,240
so approval payloads don't wander into forbidden clouds.

131
00:06:15,240 --> 00:06:20,080
Auditability, power automate offers beautiful visual traces and long term approval records,

132
00:06:20,080 --> 00:06:21,840
great for audits and post mortems.

133
00:06:21,840 --> 00:06:26,040
Work flows, agent logs, activity and admin reports and keeps conversational context,

134
00:06:26,040 --> 00:06:28,080
but it doesn't give you the same cinematic replay.

135
00:06:28,080 --> 00:06:30,480
For short, everyday approvals, that's fine.

136
00:06:30,480 --> 00:06:34,520
For anything regulated with SLA's, stay with power automate, licensing.

137
00:06:34,520 --> 00:06:39,280
If your org already pays for co-pilot, the marginal cost of these conversational approvals dips towards zero,

138
00:06:39,280 --> 00:06:41,640
especially when approvals happen in chat.

139
00:06:41,640 --> 00:06:45,360
If you're pushing thousands of back office approvals with no chat surface,

140
00:06:45,360 --> 00:06:47,400
your power automate licenses still make sense.

141
00:06:47,400 --> 00:06:49,600
Don't be cute, run the math, per cohort.

142
00:06:49,600 --> 00:06:53,400
Limits and surprises, agent runs within that 100 second window when it reaches out.

143
00:06:53,400 --> 00:06:56,240
That's fine for a simple decision and a couple notifications.

144
00:06:56,240 --> 00:06:59,440
It's not fine for elaborate pre-approval validation across six systems.

145
00:06:59,440 --> 00:07:03,040
Also, you won't get the same visual debugging because the point is to avoid needing it.

146
00:07:03,040 --> 00:07:05,960
Findings, agent wind speed and intent capture,

147
00:07:05,960 --> 00:07:09,560
power automate winds complex branching escalations and SLA's,

148
00:07:09,560 --> 00:07:11,000
the counter-intuitive part.

149
00:07:11,000 --> 00:07:13,960
Fewer knobs equals fewer breakpoints.

150
00:07:13,960 --> 00:07:16,120
Your love of micro-controls is not rigor,

151
00:07:16,120 --> 00:07:18,760
its fragility disguised as craftsmanship.

152
00:07:18,760 --> 00:07:19,960
Practical guidance.

153
00:07:19,960 --> 00:07:22,640
In your prompt, specify the SharePoint URL,

154
00:07:22,640 --> 00:07:25,560
the approver by name or role and the return channel.

155
00:07:25,560 --> 00:07:27,760
Don't make the agent guess destinations.

156
00:07:27,760 --> 00:07:30,200
For compliance heavy cases, use a hybrid.

157
00:07:30,200 --> 00:07:34,720
Agent collects context and kicks off a durable power automate approval with the full audit spine.

158
00:07:34,720 --> 00:07:36,840
If that's done, perfect.

159
00:07:36,840 --> 00:07:39,720
Next, we stress your favorite busy work, Data Sync.

160
00:07:39,720 --> 00:07:44,320
Use case two, Data Sync, SharePoint list updates with planner, Teams, Pinks.

161
00:07:44,320 --> 00:07:46,760
Status propagation is the daily paper cut.

162
00:07:46,760 --> 00:07:51,400
Someone updates a SharePoint item and suddenly five people need to know one task needs to exist

163
00:07:51,400 --> 00:07:52,920
and Teams wants a tidy summary.

164
00:07:52,920 --> 00:07:56,400
Do you want it consistent and fast or handcrafted and fragile?

165
00:07:56,400 --> 00:08:00,000
The scenario on item, create or modify, notify the manager,

166
00:08:00,000 --> 00:08:02,800
create a planner task and post a summary in Teams.

167
00:08:02,800 --> 00:08:06,040
No poetry, just signals to the right humans reliably,

168
00:08:06,040 --> 00:08:08,880
power automate version first because you love suffering.

169
00:08:08,880 --> 00:08:10,880
Trigger, when an item is created or modified,

170
00:08:10,880 --> 00:08:13,280
fetch the item, get the creator's manager via graph.

171
00:08:13,280 --> 00:08:17,360
Compose the email body, add a planner task with due date rules and checklist.

172
00:08:17,360 --> 00:08:19,880
Map the SharePoint link into the task description.

173
00:08:19,880 --> 00:08:23,480
Post a message to a specific Teams channel with a neat card.

174
00:08:23,480 --> 00:08:27,880
Then you handle the fun parts, planner group and plan IDs, channel IDs,

175
00:08:27,880 --> 00:08:33,480
HTML versus plain text, and the witchfield just got renamed by a well-meaning intern surprise.

176
00:08:33,480 --> 00:08:36,040
It's robust, it's explicit, and it's maintenance heavy.

177
00:08:36,040 --> 00:08:40,360
The good news, you can pin exact destinations, plan ABC, channel XYZ,

178
00:08:40,360 --> 00:08:41,640
and it will never guess.

179
00:08:41,640 --> 00:08:44,560
The bad news, every mapping is a place to drift.

180
00:08:44,560 --> 00:08:46,960
Enter Workflow's agent, you say.

181
00:08:46,960 --> 00:08:50,360
When a SharePoint item in this list, URL is created or modified,

182
00:08:50,360 --> 00:08:53,920
email the creator's manager a summary, create a planner task for me,

183
00:08:53,920 --> 00:08:57,680
then post a summary to the Teams channel operations updates.

184
00:08:57,680 --> 00:09:03,280
The agent assembles, trigger, manager lookup, summary generation, task creation, teams post.

185
00:09:03,280 --> 00:09:05,880
Done, you didn't pick goods, you didn't map 10 fields,

186
00:09:05,880 --> 00:09:09,360
it infers, say in defaults and shows you a test run, build time.

187
00:09:09,360 --> 00:09:14,840
Agent wins by a mile for this pattern, you'll be functional before you found the planner plan ID in Power Automate.

188
00:09:14,840 --> 00:09:18,000
Why? Because the agent treats this as a template, one it knows,

189
00:09:18,000 --> 00:09:21,360
and fills blanks with graph context, misrouting risk.

190
00:09:21,360 --> 00:09:22,760
Here's what most people miss.

191
00:09:22,760 --> 00:09:25,320
Defaults are helpful until they're wrong.

192
00:09:25,320 --> 00:09:28,040
Workflow's agent can guess destinations if you're vague,

193
00:09:28,040 --> 00:09:33,080
that means your planner task might land in my tasks when you intended onboarding 2025

194
00:09:33,080 --> 00:09:35,440
or your Teams post might hit the last use channel.

195
00:09:35,440 --> 00:09:40,400
It's preventable, specify the SharePoint list URL, the exact planner group and plan,

196
00:09:40,400 --> 00:09:42,320
and the Teams team and channel by name.

197
00:09:42,320 --> 00:09:45,520
The more precise the words, the less room for creative interpretation.

198
00:09:45,520 --> 00:09:49,880
Governance and environments, keep the same separation you pretend to have in Power Automate,

199
00:09:49,880 --> 00:09:51,680
dev, test, port.

200
00:09:51,680 --> 00:09:54,520
Apply DLP across copilot, agent and power platform,

201
00:09:54,520 --> 00:09:57,520
so SharePoint to Teams traffic doesn't hop into consumer connectors.

202
00:09:57,520 --> 00:10:01,240
Auditability? Power Automate still gives you the cleanest bread crumbs.

203
00:10:01,240 --> 00:10:06,320
The agent shows runs in admin reports, but the visual trace in PA is superior for post-mortems.

204
00:10:06,320 --> 00:10:07,440
Cost at scale.

205
00:10:07,440 --> 00:10:10,600
If your people live in chat and already have copilot sending notifications

206
00:10:10,600 --> 00:10:13,920
and creating tasks conversationally, is cost-efficient.

207
00:10:13,920 --> 00:10:16,240
Message-based consumption amortize as well.

208
00:10:16,240 --> 00:10:19,320
If you're syncing thousands of headless updates across departments

209
00:10:19,320 --> 00:10:23,920
with no chat touchpoints, your per-flow, per-user, power-automate licenses are still economical.

210
00:10:23,920 --> 00:10:27,960
Arrow surface. Power Automate minimizes runtime surprises because you nailed every mapping.

211
00:10:27,960 --> 00:10:30,280
It maximizes configuration overhead.

212
00:10:30,280 --> 00:10:32,720
The agent minimizes configuration overhead.

213
00:10:32,720 --> 00:10:35,320
And by doing so removes common human mistakes.

214
00:10:35,320 --> 00:10:39,760
Wrong plan ID, wrong channel ID, broken HTML, trade-off accepted findings.

215
00:10:39,760 --> 00:10:43,200
Agent is faster for standard patterns, notified task post.

216
00:10:43,200 --> 00:10:48,240
Power Automate wins deterministic routing, advanced formatting and reusable templates.

217
00:10:48,240 --> 00:10:49,600
Your PMO can clone.

218
00:10:49,600 --> 00:10:52,920
The hybrid sweet spot, let the agent catch the event summarized context

219
00:10:52,920 --> 00:10:56,880
and then call a power automate flow for the durable ID locked updates,

220
00:10:56,880 --> 00:10:59,680
especially when you need guaranteed routing and retries.

221
00:10:59,680 --> 00:11:03,800
Practical rule, say the URL, say the group, say the plans, don't let AI guess.

222
00:11:03,800 --> 00:11:05,720
Notifications are cute, incidents are not.

223
00:11:05,720 --> 00:11:09,840
Speaking of which, let's raise the stakes and watch classification under pressure.

224
00:11:09,840 --> 00:11:13,960
Use case three, incident triage, IT alerts to teams with assignment.

225
00:11:13,960 --> 00:11:15,920
Incidents aren't notifications, they're timers.

226
00:11:15,920 --> 00:11:20,120
Every minute a SEV-2 sits in the wrong channel, someone's SLA turns into confetti.

227
00:11:20,120 --> 00:11:23,440
You want first response speed without turning your workspace into a siren.

228
00:11:23,440 --> 00:11:25,760
The scenario, incoming alert, classified,

229
00:11:25,760 --> 00:11:30,080
root to the correct teams channel, create and assign a planar task with due date rules.

230
00:11:30,080 --> 00:11:33,000
No heroics, just the right eyeballs quickly.

231
00:11:33,000 --> 00:11:38,120
Power Automate first, you wire an HTTP trigger or a connector from your monitoring tool.

232
00:11:38,120 --> 00:11:43,080
You normalize the payload because of course they renamed severity to priority last week.

233
00:11:43,080 --> 00:11:44,520
You build conditions.

234
00:11:44,520 --> 00:11:50,000
If SEV-1 and database post in DB on call, if network, root to NOC,

235
00:11:50,000 --> 00:11:52,760
else go to incidents triage.

236
00:11:52,760 --> 00:11:56,600
You enrich with metadata, add a retry policy and write a graceful failure path

237
00:11:56,600 --> 00:11:58,840
that DMs the on call if teams posting fails.

238
00:11:58,840 --> 00:12:02,680
You then create a planar task in the exact plan with a link to the incident ticket,

239
00:12:02,680 --> 00:12:07,560
assigned to the rotation owner, set due date math and drop a card into the channel with a deep link.

240
00:12:07,560 --> 00:12:10,600
Deterministic, resilient, verbose to build.

241
00:12:10,600 --> 00:12:12,840
But when it fails, you know which step coughed.

242
00:12:12,840 --> 00:12:15,320
Enter workflows agent, you say.

243
00:12:15,320 --> 00:12:18,160
When a new incident alert arrives via this webhook,

244
00:12:18,160 --> 00:12:22,960
classified by service and severity, post a concise summary to the correct teams channel,

245
00:12:22,960 --> 00:12:27,960
then create and assign a planar task to the on call for that service with the incident link.

246
00:12:27,960 --> 00:12:29,520
The agent handles the obvious.

247
00:12:29,520 --> 00:12:33,960
It embeds classification with AI, picks the channel, posts and spins up the task.

248
00:12:33,960 --> 00:12:36,520
It feels like cheating because spoiler alert it is.

249
00:12:36,520 --> 00:12:41,240
You skipped 16 decisions and let the agent infer them from context and prior runs.

250
00:12:41,240 --> 00:12:43,920
Build time, agent wins overwhelmingly.

251
00:12:43,920 --> 00:12:46,960
Classification is baked, you don't handcraft keyword matrices.

252
00:12:46,960 --> 00:12:51,680
You'll have a functioning flow before your PA version has finished its payload schema therapy.

253
00:12:51,680 --> 00:12:53,760
Misclassification and error rate.

254
00:12:53,760 --> 00:12:55,200
Here's what most people miss.

255
00:12:55,200 --> 00:12:57,280
Deterministic isn't the same as correct.

256
00:12:57,280 --> 00:13:00,400
In PA, you're only as good as your conditions, which age poorly.

257
00:13:00,400 --> 00:13:05,680
In the agent, AI classification adapts better to weird phrasing, until it doesn't.

258
00:13:05,680 --> 00:13:10,720
That's why you add a safety rail, specify a default triage channel for low confidence classifications

259
00:13:10,720 --> 00:13:14,520
and instruct the agent to include its confidence score in the post.

260
00:13:14,520 --> 00:13:17,560
If confidence threshold, root to triage words.

261
00:13:17,560 --> 00:13:20,520
Not a tree of doom, auditability and troubleshooting.

262
00:13:20,520 --> 00:13:24,360
Power automate gives you a visual breadcrumb trail, per-action results and retry logs.

263
00:13:24,360 --> 00:13:25,640
Post mortems love that.

264
00:13:25,640 --> 00:13:29,640
Workflow's agent shows activity in admin reports and you can open the run to see the steps

265
00:13:29,640 --> 00:13:31,240
but you won't get the same microscope in it.

266
00:13:31,240 --> 00:13:36,520
If you need to prove why an alert hit the wrong channel, PA wins the courtroom drama.

267
00:13:36,520 --> 00:13:38,120
Approvals integration.

268
00:13:38,120 --> 00:13:40,720
If a Sav1 requires an instant manager acknowledgement,

269
00:13:40,720 --> 00:13:45,520
PA's start and wait for an approval with reminders and escalation is the adult in the room.

270
00:13:45,520 --> 00:13:49,120
The agent can request a quick confirmation but long-running,

271
00:13:49,120 --> 00:13:51,680
SLA track the approval still belong in PA.

272
00:13:51,680 --> 00:13:52,720
Governance.

273
00:13:52,720 --> 00:13:54,080
DLP carries over.

274
00:13:54,080 --> 00:13:57,760
Keep your monitoring, webhooks and teams posts inside approved boundaries.

275
00:13:57,760 --> 00:14:01,760
Separate environments so your test storm doesn't ping production on call.

276
00:14:01,760 --> 00:14:05,600
Restrict who can publish agents you don't want interns redefining Sav1.

277
00:14:05,600 --> 00:14:06,400
Licensing.

278
00:14:06,400 --> 00:14:09,600
If your response surface is chat heavy and you've bought co-pilot,

279
00:14:09,600 --> 00:14:11,760
the agent's message-based model is efficient.

280
00:14:11,760 --> 00:14:15,200
If you're processing high volume headless alerts across many systems,

281
00:14:15,200 --> 00:14:19,200
PA's per flow economics and scaling control still makes sense.

282
00:14:19,200 --> 00:14:20,000
Findings.

283
00:14:20,000 --> 00:14:23,280
Agent wins first response speed and flexible classification.

284
00:14:23,280 --> 00:14:26,640
PA wins resilience, traceability and surgical control.

285
00:14:26,640 --> 00:14:28,240
The hybrid pattern is obvious.

286
00:14:28,240 --> 00:14:30,960
Agent classifies, posts the first ping,

287
00:14:30,960 --> 00:14:32,960
and on confirmed Sav1,

288
00:14:32,960 --> 00:14:36,880
hands off to a PA flow for durable tasks, escalations and retries.

289
00:14:36,880 --> 00:14:40,160
Fast, where speed matters, explicit where accountability lives.

290
00:14:40,160 --> 00:14:45,280
Use case 4, CRM updates, account notes and follow-ups from Outlook.

291
00:14:45,280 --> 00:14:47,520
Sales ops doesn't forgive sloppiness.

292
00:14:47,520 --> 00:14:51,280
If the email hits your inbox but not your CRM, the forecast becomes fiction.

293
00:14:51,280 --> 00:14:54,560
You want zero friction capture and zero surprise follow-ups.

294
00:14:54,560 --> 00:14:59,280
Yes, that means prying the notes out of Outlook and landing them in the right record every time.

295
00:14:59,280 --> 00:15:02,320
The scenario, an email from a key account arrives.

296
00:15:02,320 --> 00:15:05,440
You summarize the substance, write a CRM note on the correct account

297
00:15:05,440 --> 00:15:08,320
and create a follow-up task for the owner with a due date.

298
00:15:08,320 --> 00:15:10,560
Bonus points for linking the original email.

299
00:15:10,560 --> 00:15:11,840
Power automate first.

300
00:15:11,840 --> 00:15:13,440
You start with an Outlook trigger.

301
00:15:13,440 --> 00:15:16,080
When a new email arrives and matches a condition set,

302
00:15:16,080 --> 00:15:17,520
like domain equals contoso.

303
00:15:17,520 --> 00:15:19,200
Commodestender is an attract list.

304
00:15:19,200 --> 00:15:20,880
You pass the subject and body.

305
00:15:20,880 --> 00:15:24,320
You look up the account in the CRM connector by email domain.

306
00:15:24,320 --> 00:15:26,160
Then, because accounts are messy,

307
00:15:26,160 --> 00:15:29,440
you add a fallback, try contact first, then roll up to account.

308
00:15:29,440 --> 00:15:31,520
You map fields into a create note action,

309
00:15:31,520 --> 00:15:33,360
subject body regarding object ID.

310
00:15:33,360 --> 00:15:34,640
You attach the email link.

311
00:15:34,640 --> 00:15:36,720
Next, you create a follow-up task,

312
00:15:36,720 --> 00:15:39,280
assign to the owner, set due date rules,

313
00:15:39,280 --> 00:15:43,280
say two business days from received at a category and set a reminder.

314
00:15:43,280 --> 00:15:45,440
You wrap it with IDempotency.

315
00:15:45,440 --> 00:15:47,360
Generate a hash from message ID

316
00:15:47,360 --> 00:15:49,840
to avoid duplicate notes when the message forwards.

317
00:15:49,840 --> 00:15:52,400
Finally, you add try catch branches.

318
00:15:52,400 --> 00:15:54,800
If the account look up returns multiple matches,

319
00:15:54,800 --> 00:15:56,800
send a human validation card.

320
00:15:56,800 --> 00:15:58,800
If the CRM API throttles,

321
00:15:58,800 --> 00:16:01,040
retry with exponential back off.

322
00:16:01,040 --> 00:16:02,800
Deterministic, durable.

323
00:16:02,800 --> 00:16:04,560
Annoyingly verbose to build,

324
00:16:04,560 --> 00:16:08,240
but future you will thank you when someone asks why three notes appeared.

325
00:16:08,240 --> 00:16:09,280
Enter workflows agent.

326
00:16:09,280 --> 00:16:12,560
You say, when I get an email from any contact at the Fabricum account,

327
00:16:12,560 --> 00:16:14,560
summarize the key points in two sentences,

328
00:16:14,560 --> 00:16:17,360
add it as a note on the Fabricum account in CRM,

329
00:16:17,360 --> 00:16:19,280
include a link back to the email,

330
00:16:19,280 --> 00:16:22,400
then create a follow-up task for the account owner due in two days.

331
00:16:22,400 --> 00:16:27,200
The agent ingests the email, runs an embedded summarized step,

332
00:16:27,200 --> 00:16:30,240
resolves Fabricum via graph context and your CRM connector,

333
00:16:30,240 --> 00:16:32,000
writes the note and creates the task.

334
00:16:32,000 --> 00:16:35,920
It feels like cheating because it collapses the mapping ceremony into intent.

335
00:16:35,920 --> 00:16:38,000
You don't handpick fields, you describe outcomes.

336
00:16:38,000 --> 00:16:40,480
Build time, agent obliterates the setup overhead.

337
00:16:40,480 --> 00:16:44,000
Your life before your PA version finishes the contact account fallback logic.

338
00:16:44,000 --> 00:16:44,960
That's the point.

339
00:16:44,960 --> 00:16:47,520
Capture from context is where agents shine.

340
00:16:47,520 --> 00:16:48,960
Field mismatch errors.

341
00:16:48,960 --> 00:16:51,840
Power automate still wins structured validation.

342
00:16:51,840 --> 00:16:56,720
If your CRM requires a regarding relationship type or a specific schema for notes,

343
00:16:56,720 --> 00:16:59,040
PA lets you enforce it explicitly

344
00:16:59,040 --> 00:17:01,680
and fail loud with a human in the loop check.

345
00:17:01,680 --> 00:17:03,920
The agent composes reasonable defaults.

346
00:17:03,920 --> 00:17:06,080
If your CRM is unusually pedantic,

347
00:17:06,080 --> 00:17:09,440
you may see occasional "why did it pick that field" moments.

348
00:17:09,440 --> 00:17:10,480
Avoid guessing.

349
00:17:10,480 --> 00:17:12,240
Name the account explicitly in your prompt

350
00:17:12,240 --> 00:17:15,760
or include the CRM URL for the record to reduce ambiguity.

351
00:17:15,760 --> 00:17:16,880
Execution constraints.

352
00:17:16,880 --> 00:17:20,320
Remember the 100 second agent timeout when calling external systems.

353
00:17:20,320 --> 00:17:22,080
Simple note plus task fits.

354
00:17:22,080 --> 00:17:25,120
Long chains, like enrichment calls to three back office systems, don't.

355
00:17:25,120 --> 00:17:28,000
That's where you hand off audit, trail and idem potency.

356
00:17:28,000 --> 00:17:29,760
Power automate gives you the visual trace,

357
00:17:29,760 --> 00:17:32,400
the message id, dedupe and a clean story for audits.

358
00:17:32,400 --> 00:17:34,320
The agent logs activity in admin reports,

359
00:17:34,320 --> 00:17:36,720
but you won't get the same surgical playback yet.

360
00:17:36,720 --> 00:17:38,880
If your sales obs leader breathes compliance,

361
00:17:38,880 --> 00:17:41,120
don't trust AI will remember.

362
00:17:41,120 --> 00:17:44,560
Implement idem potency in PA, licensing economics.

363
00:17:44,560 --> 00:17:47,840
If your sellers already have co-pilot and live-in outlook in teams,

364
00:17:47,840 --> 00:17:49,840
the marginal cost of agent-driven summaries

365
00:17:49,840 --> 00:17:51,840
and task creation trends down.

366
00:17:51,840 --> 00:17:55,920
If you're automating for a large field org with strict CRM rules and no chat surface,

367
00:17:55,920 --> 00:17:58,560
PA's per flow predictability still pencils out.

368
00:17:58,560 --> 00:18:01,600
Findings, agent wins on capture from context and speed,

369
00:18:01,600 --> 00:18:03,680
power automate wins on structured validation,

370
00:18:03,680 --> 00:18:05,600
idem potency and retries.

371
00:18:05,600 --> 00:18:06,800
Practical hybrid.

372
00:18:06,800 --> 00:18:08,800
Let the agent summarize and gather context,

373
00:18:08,800 --> 00:18:13,040
then trigger a PA flow with the email, message id and resolved account id

374
00:18:13,040 --> 00:18:15,840
to perform the durable schema locked updates.

375
00:18:15,840 --> 00:18:18,000
Conversational front and enterprise grade spine,

376
00:18:18,000 --> 00:18:20,400
you get speed without gambling the pipeline.

377
00:18:20,400 --> 00:18:24,640
Use case five, IT onboarding, from request to checklist.

378
00:18:24,640 --> 00:18:27,040
Onboarding is where cute automations go to die.

379
00:18:27,040 --> 00:18:31,680
It's recurring, cross-app, approval laden and audited by people who enjoy policies.

380
00:18:31,680 --> 00:18:35,120
Day one chaos equals lost productivity and a help desk bonfire.

381
00:18:35,120 --> 00:18:38,560
The scenario, intake request approvals account setup tasks,

382
00:18:38,560 --> 00:18:41,600
teams channel posts, confirmations and status reporting.

383
00:18:41,600 --> 00:18:44,320
Many hands, many systems, many ways to trip,

384
00:18:44,320 --> 00:18:45,840
power automate first.

385
00:18:45,840 --> 00:18:48,240
You build an intake form or share point list.

386
00:18:48,240 --> 00:18:50,720
Trigger on submission, kick off a parallel branch,

387
00:18:50,720 --> 00:18:53,760
HR approval, manager approval, device approval.

388
00:18:53,760 --> 00:18:56,640
Each branch has retries, escalations and timeouts,

389
00:18:56,640 --> 00:18:58,720
because humans again ghost.

390
00:18:58,720 --> 00:19:02,640
Once approved, you orchestrate, create accounts, assign licenses,

391
00:19:02,640 --> 00:19:04,880
add to groups, create a mailbox alias,

392
00:19:04,880 --> 00:19:07,920
provision a one drive, drop a welcome post in the team,

393
00:19:07,920 --> 00:19:12,480
open tickets in ITSM and assemble a checklist in planar with dependencies.

394
00:19:12,480 --> 00:19:13,520
You add guards.

395
00:19:13,520 --> 00:19:16,480
If license assignment fails, rollback group additions.

396
00:19:16,480 --> 00:19:19,600
If HR approval times out, cancel downstream tasks.

397
00:19:19,600 --> 00:19:21,600
You tag every action with correlation IDs

398
00:19:21,600 --> 00:19:24,320
and stash everything in a durable store for audits.

399
00:19:24,320 --> 00:19:28,240
It's long running, explicit and frankly, exemplary engineering.

400
00:19:28,240 --> 00:19:30,000
Enter workflows agent, you say,

401
00:19:30,000 --> 00:19:32,640
when a new hire request is submitted at this SharePoint URL,

402
00:19:32,640 --> 00:19:35,200
collect the details, confirm with the manager,

403
00:19:35,200 --> 00:19:37,520
create a planar checklist for onboarding tasks,

404
00:19:37,520 --> 00:19:39,680
post a welcome in the team new hires,

405
00:19:39,680 --> 00:19:41,920
and notify IT when approvals are in.

406
00:19:41,920 --> 00:19:44,400
The agent races through intake, nudges the manager,

407
00:19:44,400 --> 00:19:46,560
sets up the checklist and gets the comms moving.

408
00:19:46,560 --> 00:19:48,960
It feels instantaneous because the conversational front

409
00:19:48,960 --> 00:19:51,520
eliminates the configuration ceremony.

410
00:19:51,520 --> 00:19:53,120
But, and this is the adult moment,

411
00:19:53,120 --> 00:19:57,280
deep branching, SLA's and conditional rollbacks inside a 100 second window?

412
00:19:57,280 --> 00:20:01,360
No, build time agent is unbeatable for intake, confirmation and kickoff.

413
00:20:01,360 --> 00:20:03,600
You'll have a working front door and a living checklist

414
00:20:03,600 --> 00:20:06,480
before your PA flow finishes its third parallel branch,

415
00:20:06,480 --> 00:20:08,160
reduction in handoffs and errors.

416
00:20:08,160 --> 00:20:12,800
The agent's summarization and manager confirmation kill the missing fields plague.

417
00:20:12,800 --> 00:20:15,600
No more back and forth for the start date or job code.

418
00:20:15,600 --> 00:20:17,600
Power automate then takes a clean payload

419
00:20:17,600 --> 00:20:20,720
and does the durable, reversible, audited, heavy lifting.

420
00:20:20,720 --> 00:20:22,720
Governance, keep environment separated.

421
00:20:22,720 --> 00:20:25,840
DLP aligned across co-pilot agent and power platform.

422
00:20:25,840 --> 00:20:29,120
Lock publishing rights, approvals with SLA's and escalation rules

423
00:20:29,120 --> 00:20:31,120
live in power automate non-negotiable.

424
00:20:31,120 --> 00:20:32,480
Quick confirmation pings?

425
00:20:32,480 --> 00:20:34,080
Agents fine.

426
00:20:34,080 --> 00:20:34,880
Licensing?

427
00:20:34,880 --> 00:20:36,560
If HR and managers live in chat,

428
00:20:36,560 --> 00:20:39,600
the marginal cost of the agent intake drops to near zero.

429
00:20:39,600 --> 00:20:43,040
The marathon, licensing assignment, group membership, ITSM,

430
00:20:43,040 --> 00:20:46,400
still justifies PA licensing where scale and durability matter.

431
00:20:46,400 --> 00:20:47,840
Findings.

432
00:20:47,840 --> 00:20:49,040
Agents starts the play,

433
00:20:49,040 --> 00:20:50,800
power automate runs the marathon.

434
00:20:50,800 --> 00:20:53,760
Refactor the front door to agent for speed and clarity.

435
00:20:53,760 --> 00:20:56,240
Keep the backbone in PA for reliability,

436
00:20:56,240 --> 00:20:57,680
retries and audits.

437
00:20:57,680 --> 00:21:00,720
Rule of thumb, conversational front end, enterprise grade back end.

438
00:21:00,720 --> 00:21:02,160
Use the right spine.

439
00:21:02,160 --> 00:21:03,200
The scorecard.

440
00:21:03,200 --> 00:21:05,600
Build time, errors, governance, cost.

441
00:21:05,600 --> 00:21:06,800
Time to hand out trophies.

442
00:21:06,800 --> 00:21:07,920
Build time first.

443
00:21:07,920 --> 00:21:10,240
Work flows, agent slashes setup for common patterns,

444
00:21:10,240 --> 00:21:12,800
approvals, notify task post intake and kickoff.

445
00:21:12,800 --> 00:21:14,640
You'll be live in minutes, not afternoons.

446
00:21:14,640 --> 00:21:17,040
Power automate is slower because you're explicit.

447
00:21:17,040 --> 00:21:19,440
Every mapping, every branch, but predictably so.

448
00:21:20,160 --> 00:21:23,280
Verdict agent for speed PA for precision, errors,

449
00:21:23,280 --> 00:21:25,360
two kinds, configuration and runtime.

450
00:21:25,360 --> 00:21:27,040
Agent reduces configuration errors

451
00:21:27,040 --> 00:21:29,760
by refusing to let you micromanage every field.

452
00:21:29,760 --> 00:21:31,920
Fewer knobs, fewer misalignments.

453
00:21:31,920 --> 00:21:34,080
Power automate minimizes runtime errors

454
00:21:34,080 --> 00:21:37,040
through explicit rules, retries and idempotency.

455
00:21:37,040 --> 00:21:40,080
Verdict agent lowers setup mistakes.

456
00:21:40,080 --> 00:21:41,680
PA lowers production surprises.

457
00:21:41,680 --> 00:21:44,320
Governance agent now surfaces usage analytics

458
00:21:44,320 --> 00:21:46,080
in admin reports, respects DLP

459
00:21:46,080 --> 00:21:48,400
and can be ring-fanced by environment and role.

460
00:21:48,400 --> 00:21:49,280
Good progress.

461
00:21:49,280 --> 00:21:51,440
Power automate still wins audit trails,

462
00:21:51,440 --> 00:21:53,360
visual traces, environment maturity

463
00:21:53,360 --> 00:21:54,960
and approvals with SLAs.

464
00:21:54,960 --> 00:21:57,680
Verdict agent acceptable for everyday work.

465
00:21:57,680 --> 00:22:00,400
PA for regulated long-running processes.

466
00:22:00,400 --> 00:22:01,280
Licensing.

467
00:22:01,280 --> 00:22:04,240
If you've bought co-pilot and your automation's live in chat,

468
00:22:04,240 --> 00:22:06,560
agent workflows write message-based economics

469
00:22:06,560 --> 00:22:09,600
and undercut per user per flow for those cohorts.

470
00:22:09,600 --> 00:22:11,200
If you're running a broad portfolio

471
00:22:11,200 --> 00:22:13,040
of headless cross-system automations,

472
00:22:13,040 --> 00:22:14,880
PA's licensing stays rational.

473
00:22:14,880 --> 00:22:17,200
Verdict, cohort math, not ideology.

474
00:22:17,200 --> 00:22:18,080
Decision matrix.

475
00:22:18,880 --> 00:22:21,360
Simple, intent-friendly, human in the loop.

476
00:22:21,360 --> 00:22:22,320
Agent.

477
00:22:22,320 --> 00:22:25,920
Complex, long-running, regulated,

478
00:22:25,920 --> 00:22:28,400
power automate, hybrid wins most.

479
00:22:28,400 --> 00:22:30,720
Agent for capture and orchestration prompts.

480
00:22:30,720 --> 00:22:33,120
PA for durable execution and audits.

481
00:22:33,120 --> 00:22:35,840
The practical migration filter you'll use tomorrow.

482
00:22:35,840 --> 00:22:37,840
If it needs a gant chart to explain,

483
00:22:37,840 --> 00:22:38,880
keep it in PA.

484
00:22:38,880 --> 00:22:40,400
If you can state it in one sentence

485
00:22:40,400 --> 00:22:41,760
without gasping for air,

486
00:22:41,760 --> 00:22:42,960
draft it in agent.

487
00:22:42,960 --> 00:22:44,320
And when in doubt, split.

488
00:22:44,320 --> 00:22:45,520
Agent collects context.

489
00:22:45,520 --> 00:22:48,480
PA does the irreversible stuff with retries and receipts.

490
00:22:48,480 --> 00:22:50,080
Here's the uncomfortable truth you needed.

491
00:22:50,080 --> 00:22:52,000
Your manual flow hoarding is the bottleneck.

492
00:22:52,000 --> 00:22:54,000
The agent didn't kill power automate.

493
00:22:54,000 --> 00:22:56,160
It killed your excuse to spend a week wiring

494
00:22:56,160 --> 00:22:58,560
what a sentence can start in 30 seconds.

495
00:22:58,560 --> 00:23:00,640
Refactor plan, what to keep, what to move,

496
00:23:00,640 --> 00:23:02,880
what to retire, inventory first,

497
00:23:02,880 --> 00:23:04,320
not vibes, facts.

498
00:23:04,320 --> 00:23:07,840
Pull your flow catalog and tag each by four attributes.

499
00:23:07,840 --> 00:23:11,760
Complexity, single branch versus gant chart.

500
00:23:11,760 --> 00:23:14,000
Run time length, seconds versus days,

501
00:23:14,000 --> 00:23:15,440
regulatory sensitivity,

502
00:23:15,440 --> 00:23:16,960
non-internal audited,

503
00:23:16,960 --> 00:23:18,160
and user touch points.

504
00:23:18,400 --> 00:23:20,560
Chat email prompts versus headless.

505
00:23:20,560 --> 00:23:22,960
You'll find three piles faster than you expect.

506
00:23:22,960 --> 00:23:25,360
Keep in power, automate anything long-running,

507
00:23:25,360 --> 00:23:26,960
multi-branch or regulated.

508
00:23:26,960 --> 00:23:28,400
That's your onboarding spine,

509
00:23:28,400 --> 00:23:30,800
multi-stage approvals with escalations,

510
00:23:30,800 --> 00:23:32,320
finance closed checklists,

511
00:23:32,320 --> 00:23:33,680
ITSM rollbacks,

512
00:23:33,680 --> 00:23:35,920
and any integration that needs item potency,

513
00:23:35,920 --> 00:23:37,760
retries and forensic logs.

514
00:23:37,760 --> 00:23:40,560
If a missed SLA triggers an audit, it stays.

515
00:23:40,560 --> 00:23:42,000
If a flow touches five systems

516
00:23:42,000 --> 00:23:43,680
and needs compensation logic, it stays.

517
00:23:43,680 --> 00:23:45,360
Adult automation lives here.

518
00:23:45,360 --> 00:23:46,720
Move to workflows agent,

519
00:23:46,720 --> 00:23:48,480
intake summaries, notifications,

520
00:23:48,480 --> 00:23:50,880
status digest and simple approvals.

521
00:23:50,880 --> 00:23:53,840
Anywhere, say it, run it, confirm it, applies.

522
00:23:53,840 --> 00:23:54,880
Examples.

523
00:23:54,880 --> 00:23:56,720
One approver, yes, no list updates

524
00:23:56,720 --> 00:23:58,640
that ping a manager and create a task,

525
00:23:58,640 --> 00:24:00,240
daily summaries to teams.

526
00:24:00,240 --> 00:24:02,080
Quick CRM node capture from Outlook.

527
00:24:02,080 --> 00:24:04,640
The 100-second constraint isn't a problem for these.

528
00:24:04,640 --> 00:24:05,840
You'll slash build time

529
00:24:05,840 --> 00:24:08,240
and eliminate the config drift clown show.

530
00:24:08,240 --> 00:24:10,320
Hybrid handoffs, the Workhorse pattern,

531
00:24:10,320 --> 00:24:11,600
agent collects context,

532
00:24:11,600 --> 00:24:13,120
validates with a human in chat,

533
00:24:13,120 --> 00:24:16,160
and then triggers a power automate flow for durable actions.

534
00:24:16,160 --> 00:24:18,880
You respect the time window by sending a compact payload,

535
00:24:18,880 --> 00:24:21,360
IDs and essentials, not your life story.

536
00:24:21,360 --> 00:24:23,280
The PA flow owns the heavy lifting,

537
00:24:23,280 --> 00:24:26,640
schema locked rides, retries, audit stamps and SLAs.

538
00:24:26,640 --> 00:24:28,000
You get the speed of conversation

539
00:24:28,000 --> 00:24:29,280
in the spine of engineering.

540
00:24:29,280 --> 00:24:31,920
Governance set up before migration, yes, before.

541
00:24:31,920 --> 00:24:33,200
Create dev test,

542
00:24:33,200 --> 00:24:36,160
prod environments for agents and PA aligned one to one.

543
00:24:36,160 --> 00:24:39,360
Align DLP policies across co-pilot agent and power platform

544
00:24:39,360 --> 00:24:41,120
so data parts stay legal.

545
00:24:41,120 --> 00:24:42,560
Define who can publish agents

546
00:24:42,560 --> 00:24:44,720
and who can bind them to production data.

547
00:24:44,720 --> 00:24:46,240
Turn on admin usage reports

548
00:24:46,240 --> 00:24:48,640
and decide retention for agent conversations now,

549
00:24:48,640 --> 00:24:50,400
not after legal emails you.

550
00:24:50,400 --> 00:24:52,480
Playbook, pilot 10% of flows,

551
00:24:52,480 --> 00:24:56,000
pick representative cohorts, approvals, data sync, sales notes,

552
00:24:56,000 --> 00:24:58,320
rebuild the front door and agent wear appropriate

553
00:24:58,320 --> 00:25:00,400
or move the whole thing if it's simple.

554
00:25:00,400 --> 00:25:03,200
Measure build time delta and error delta for each cohort.

555
00:25:03,200 --> 00:25:06,560
If the numbers hold expand by cohort, not by enthusiasm,

556
00:25:06,560 --> 00:25:08,320
document prompt patterns that work.

557
00:25:08,320 --> 00:25:11,040
URLs, exact group plan names, channel names,

558
00:25:11,040 --> 00:25:12,240
and standardize them.

559
00:25:12,240 --> 00:25:14,560
Anti-patterns to avoid because I know you,

560
00:25:14,560 --> 00:25:17,280
don't rebuild complex PA logic inside the agent,

561
00:25:17,280 --> 00:25:19,440
you're fighting physics and you will lose.

562
00:25:19,440 --> 00:25:23,520
Don't let AI guest destinations names URLs IDs in the prompt every time.

563
00:25:23,520 --> 00:25:24,960
Don't promote agents straight to prod

564
00:25:24,960 --> 00:25:26,720
because it worked in my tenant.

565
00:25:26,720 --> 00:25:29,280
And don't confuse fewer knobs with less governance,

566
00:25:29,280 --> 00:25:30,560
the knobs move to policy,

567
00:25:30,560 --> 00:25:34,640
which takes us to the part IT actually cares about, controls.

568
00:25:34,640 --> 00:25:37,280
Governance, security, and admin reality check.

569
00:25:37,280 --> 00:25:40,000
DLP first, align co-pilot agent policies

570
00:25:40,000 --> 00:25:41,520
with your power platform DLP

571
00:25:41,520 --> 00:25:44,800
so data can't leak across tenants or into consumer connectors.

572
00:25:44,800 --> 00:25:47,120
If SharePoint and Teams are business only,

573
00:25:47,120 --> 00:25:48,480
enforce it consistently.

574
00:25:48,480 --> 00:25:51,120
Any connector allowed in PA that's disallowed in co-pilot

575
00:25:51,120 --> 00:25:53,040
is a policy bug waiting to happen.

576
00:25:53,040 --> 00:25:55,680
Fix the matrix, don't trust tribal memory.

577
00:25:55,680 --> 00:25:56,800
Auditability.

578
00:25:56,800 --> 00:26:00,080
Turn on the agents user report in the Microsoft 365 admin center

579
00:26:00,080 --> 00:26:03,200
and decide retention for both conversations and actions.

580
00:26:03,200 --> 00:26:06,560
Define who can access run histories and how long they're kept.

581
00:26:06,560 --> 00:26:10,160
Power automate still wins cinematic replays with per-action traces.

582
00:26:10,160 --> 00:26:11,600
Use that where audits live.

583
00:26:11,600 --> 00:26:13,440
For agent, establish the rule.

584
00:26:13,440 --> 00:26:16,800
For regulated processes, the agent must hand off to a PA flow

585
00:26:16,800 --> 00:26:18,240
that provides the audit spine.

586
00:26:18,240 --> 00:26:20,400
Conversational shadows don't pass audits.

587
00:26:20,400 --> 00:26:23,840
Environments, separate dev test prod for both agents and PA.

588
00:26:23,840 --> 00:26:25,600
Mirror data sources and permissions,

589
00:26:25,600 --> 00:26:26,720
so tests are real.

590
00:26:26,720 --> 00:26:28,560
Restrict who can publish agents to prod?

591
00:26:28,560 --> 00:26:30,960
Our back at the door approvals for promotion.

592
00:26:30,960 --> 00:26:33,360
Yes, require change tickets for flows and agents

593
00:26:33,360 --> 00:26:34,880
that touch regulated data.

594
00:26:34,880 --> 00:26:37,680
No, it's just AI is not a get out of governance free card.

595
00:26:37,680 --> 00:26:39,840
Approvals, standardized patterns.

596
00:26:39,840 --> 00:26:42,720
Quick short approvals with a clear trail are fine and agent.

597
00:26:42,720 --> 00:26:45,600
Long running, SLA tract approvals with escalation rules

598
00:26:45,600 --> 00:26:47,120
stay in power automate.

599
00:26:47,120 --> 00:26:48,480
Create templates for both,

600
00:26:48,480 --> 00:26:50,240
so people stop improvising governance.

601
00:26:50,240 --> 00:26:52,160
If an approval can block payroll,

602
00:26:52,160 --> 00:26:54,560
it belongs in PA with SLA's,

603
00:26:54,560 --> 00:26:56,720
reminders and escalation chains.

604
00:26:56,720 --> 00:26:58,800
Non-negotiable observability.

605
00:26:58,800 --> 00:27:01,440
Instrument the agent side with co-pilot studio analytics

606
00:27:01,440 --> 00:27:04,000
and Azure AI safety metrics were available.

607
00:27:04,000 --> 00:27:07,120
Watch classification confidence, failure rates and fallback routes.

608
00:27:07,120 --> 00:27:10,000
On the PA side, keep your solution level telemetry,

609
00:27:10,000 --> 00:27:12,880
retry counts, exception parts, average duration.

610
00:27:12,880 --> 00:27:14,000
Review both monthly.

611
00:27:14,000 --> 00:27:15,280
If you're not looking at the numbers,

612
00:27:15,280 --> 00:27:16,480
you're not running production.

613
00:27:16,480 --> 00:27:17,680
You're hoping?

614
00:27:17,680 --> 00:27:18,800
Risk posture.

615
00:27:18,800 --> 00:27:20,800
Frontier features are shiny and early.

616
00:27:20,800 --> 00:27:22,880
Ring fans them, pilot with select users,

617
00:27:22,880 --> 00:27:25,040
define rollback plans and isolate data,

618
00:27:25,040 --> 00:27:27,920
document what's in frontier and what's in production support.

619
00:27:27,920 --> 00:27:29,920
If a feature label says directional,

620
00:27:29,920 --> 00:27:33,040
translate that to not a legal dependency in your policy,

621
00:27:33,040 --> 00:27:34,560
your lawyers will not grimly.

622
00:27:34,560 --> 00:27:36,080
Data residency and privacy.

623
00:27:36,080 --> 00:27:39,440
Agents inherit Microsoft 365 security baselines,

624
00:27:39,440 --> 00:27:41,920
but your policy must state which data is in scope

625
00:27:41,920 --> 00:27:43,840
for agent processing and which is not.

626
00:27:43,840 --> 00:27:46,800
Sensitive HR, fine with proper DLP and handoffs,

627
00:27:46,800 --> 00:27:47,920
cross tenant finance,

628
00:27:47,920 --> 00:27:49,920
probably not in agent without a PA spine

629
00:27:49,920 --> 00:27:51,120
and explicit approvals.

630
00:27:51,120 --> 00:27:53,680
Write it down, enforce it, change control,

631
00:27:53,680 --> 00:27:56,000
treat prompt text like code, version it,

632
00:27:56,000 --> 00:27:59,200
store blessed prompts in a repo or at least a secured list.

633
00:27:59,200 --> 00:28:02,000
If someone fixes the words and breaks routing,

634
00:28:02,000 --> 00:28:04,720
you need a diff and a rollback, not a witch hunt.

635
00:28:04,720 --> 00:28:07,280
Bottom line, the agent is not shadow IT

636
00:28:07,280 --> 00:28:09,040
if you govern it where it lives.

637
00:28:09,040 --> 00:28:12,000
Policy environments are bi-at-t observability.

638
00:28:12,000 --> 00:28:14,960
Power automate remains your audit grade execution engine.

639
00:28:14,960 --> 00:28:16,640
Together, they are governable.

640
00:28:16,640 --> 00:28:17,920
Separately, they are chaos.

641
00:28:17,920 --> 00:28:18,960
Choose together.

642
00:28:18,960 --> 00:28:21,040
The blunt verdict and your next move.

643
00:28:21,040 --> 00:28:22,320
The takeaway.

644
00:28:22,320 --> 00:28:23,680
Power automate isn't dead.

645
00:28:23,680 --> 00:28:25,360
Your manual flow holding is.

646
00:28:25,360 --> 00:28:26,880
Agent front for speed,

647
00:28:26,880 --> 00:28:29,360
PA spine for durability and hybrids

648
00:28:29,360 --> 00:28:31,120
for anything that pays the bills.

649
00:28:31,120 --> 00:28:33,360
If this saved you time, repay the debt.

650
00:28:33,360 --> 00:28:37,040
Refactor one approval and one data sink into agent this week.

651
00:28:37,040 --> 00:28:38,880
Measure time and error deltas.

652
00:28:38,880 --> 00:28:41,440
Then graduate to a hybrid CRM update.

653
00:28:41,440 --> 00:28:44,400
Subscribe for the full migration workshop next episode.