1
00:00:00,040 --> 00:00:02,279
Welcome to the M365 FM podcast,
2
00:00:02,279 --> 00:00:03,680
where we explore the people,
3
00:00:03,680 --> 00:00:05,679
ideas and technologies shaping
4
00:00:05,679 --> 00:00:07,200
the future of work somewhere in
5
00:00:07,200 --> 00:00:08,119
your company.
6
00:00:08,119 --> 00:00:10,800
An AI agent is reading your
files, and the only place that
7
00:00:10,800 --> 00:00:13,039
knows who owns it is a page most
people never open.
8
00:00:13,039 --> 00:00:15,839
That sounds dramatic, but it is
just the normal state of AI at
9
00:00:15,839 --> 00:00:16,800
work right now.
10
00:00:16,800 --> 00:00:18,079
Agents are easy to build and
11
00:00:18,079 --> 00:00:19,719
easy to forget, so they pile up
12
00:00:19,719 --> 00:00:21,519
across teams, tools, and
13
00:00:21,519 --> 00:00:22,199
laptops.
14
00:00:22,199 --> 00:00:25,559
Welcome to the M365 FM podcast,
where we explore the people,
15
00:00:25,559 --> 00:00:28,239
ideas and technologies shaping
the future of work.
16
00:00:28,239 --> 00:00:30,660
Today we're talking about
Microsoft Agent three sixty
17
00:00:30,660 --> 00:00:33,640
five, the control room Microsoft
built inside the Microsoft three
18
00:00:33,640 --> 00:00:36,399
hundred sixty five Admin Center
to keep track of all of them.
19
00:00:36,399 --> 00:00:39,399
By the end, you'll know what it
is, how it works, and where it
20
00:00:39,399 --> 00:00:40,840
honestly falls short.
21
00:00:40,840 --> 00:00:43,119
What an AI agent actually is.
22
00:00:43,119 --> 00:00:45,520
The word agent gets thrown
around like everyone already
23
00:00:45,520 --> 00:00:47,880
agrees on what it means, and
most people don't.
24
00:00:47,880 --> 00:00:49,719
An agent is software that does
work for you.
25
00:00:49,719 --> 00:00:50,759
Instead of just answering
26
00:00:50,759 --> 00:00:52,439
questions, a chat bot waits for
27
00:00:52,439 --> 00:00:53,359
you to type something and
28
00:00:53,359 --> 00:00:54,719
replies while an agent goes
29
00:00:54,719 --> 00:00:55,920
further and actually finishes a
30
00:00:55,920 --> 00:00:56,320
task.
31
00:00:56,320 --> 00:00:58,039
It follows the instructions
someone gave.
32
00:00:58,039 --> 00:01:01,039
It draws on the knowledge it's
allowed to use, and then reaches
33
00:01:01,039 --> 00:01:02,600
for tools to get the job done.
34
00:01:02,600 --> 00:01:05,480
Those tools are what turn a
clever reply into finished work.
35
00:01:05,480 --> 00:01:08,000
They let an agent open a file,
send an email, or update a
36
00:01:08,000 --> 00:01:10,640
record picture, an agent that
watches a shared in-box and
37
00:01:10,640 --> 00:01:13,439
drafts a reply to every customer
question that lands there.
38
00:01:13,439 --> 00:01:14,760
You still hit send, but the
39
00:01:14,760 --> 00:01:16,159
slow, repetitive part is already
40
00:01:16,159 --> 00:01:16,719
finished.
41
00:01:16,719 --> 00:01:18,040
Now imagine a second one on a
42
00:01:18,040 --> 00:01:19,239
support queue, reading each
43
00:01:19,239 --> 00:01:20,280
ticket and sending it to the
44
00:01:20,280 --> 00:01:21,680
right team with a summary
45
00:01:21,680 --> 00:01:22,400
attached.
46
00:01:22,400 --> 00:01:23,560
Then there's the quiet one that
47
00:01:23,560 --> 00:01:24,920
answers HR questions like how
48
00:01:24,920 --> 00:01:26,079
much vacation you have left
49
00:01:26,079 --> 00:01:27,000
straight from the employee
50
00:01:27,000 --> 00:01:27,400
handbook.
51
00:01:27,400 --> 00:01:29,760
None of this feels like science
fiction anymore.
52
00:01:29,760 --> 00:01:31,519
And that quiet ordinariness is
53
00:01:31,519 --> 00:01:33,120
exactly why agents spread so
54
00:01:33,120 --> 00:01:33,439
fast.
55
00:01:33,439 --> 00:01:36,799
Once one team proves they work,
people build them in places you
56
00:01:36,799 --> 00:01:38,079
might already recognize.
57
00:01:38,079 --> 00:01:41,319
Microsoft Copilot Studio is the
main workshop, and it's where
58
00:01:41,319 --> 00:01:43,040
most custom agents get made.
59
00:01:43,040 --> 00:01:44,120
Others come out of Agent
60
00:01:44,120 --> 00:01:46,079
Builder, inside copilot, out of
61
00:01:46,079 --> 00:01:47,480
SharePoint, or out of Microsoft
62
00:01:47,480 --> 00:01:47,840
Foundry.
63
00:01:47,840 --> 00:01:49,319
Over on the other side, the
64
00:01:49,319 --> 00:01:51,079
Admin Center sorts them by type
65
00:01:51,079 --> 00:01:52,000
so it can tell a simple
66
00:01:52,000 --> 00:01:53,519
instructions only agent apart
67
00:01:53,519 --> 00:01:54,879
from one running a custom engine
68
00:01:54,879 --> 00:01:56,120
or a full business process, you
69
00:01:56,120 --> 00:01:57,099
don't need those labels to
70
00:01:57,099 --> 00:01:57,920
follow along.
71
00:01:57,920 --> 00:02:01,280
What matters is that every agent
is a small worker with a job, a
72
00:02:01,280 --> 00:02:03,859
set of permissions, and an owner
hold on to that owner idea
73
00:02:03,859 --> 00:02:06,359
because it becomes the whole
story in a minute.
74
00:02:06,359 --> 00:02:09,120
Why agents pile up and why that
becomes a problem.
75
00:02:09,120 --> 00:02:11,960
Creating an agent has never been
easier, and that's the problem.
76
00:02:11,960 --> 00:02:14,419
A person in finance can build
one before lunch without telling
77
00:02:14,419 --> 00:02:18,000
it, and a person in HR can do
the same by the afternoon.
78
00:02:18,000 --> 00:02:20,759
Multiply that across a few
thousand people and the agents
79
00:02:20,759 --> 00:02:23,039
start to outnumber the people
who understand them.
80
00:02:23,039 --> 00:02:25,800
Management gets scattered too,
because some agents live in
81
00:02:25,800 --> 00:02:28,919
copilot studios, some in the
teams admin center, and some in
82
00:02:28,919 --> 00:02:30,319
the security tools.
83
00:02:30,319 --> 00:02:31,759
No single person ends up with
84
00:02:31,759 --> 00:02:33,319
the full picture, which is how a
85
00:02:33,319 --> 00:02:34,759
small convenience turns into a
86
00:02:34,759 --> 00:02:35,719
quiet liability.
87
00:02:35,719 --> 00:02:36,960
Microsoft says it plainly in its
88
00:02:36,960 --> 00:02:38,520
own guidance you can't govern
89
00:02:38,520 --> 00:02:39,919
what you can't see, and you
90
00:02:39,919 --> 00:02:40,879
can't secure what you don't
91
00:02:40,879 --> 00:02:41,479
understand.
92
00:02:41,479 --> 00:02:44,120
That line matters because the
controls most companies already
93
00:02:44,120 --> 00:02:47,120
have were built for people,
apps, and data, not for software
94
00:02:47,120 --> 00:02:48,360
that acts on its own.
95
00:02:48,360 --> 00:02:50,439
When the pieces don't talk to
each other, you get what the
96
00:02:50,439 --> 00:02:52,479
industry calls agent sprawl.
97
00:02:52,479 --> 00:02:53,680
It's a fancy name for a simple
98
00:02:53,680 --> 00:02:55,159
mess, where agents multiply
99
00:02:55,159 --> 00:02:56,300
across teams with no clear
100
00:02:56,300 --> 00:02:56,919
oversight.
101
00:02:56,919 --> 00:02:59,759
Nobody can say for sure what
each one can reach or how it
102
00:02:59,759 --> 00:03:00,879
behaves over time.
103
00:03:00,879 --> 00:03:03,800
This scenario plays out
constantly in real companies.
104
00:03:03,800 --> 00:03:04,900
Someone builds an agent to
105
00:03:04,900 --> 00:03:06,520
summarize sales calls, uses it
106
00:03:06,520 --> 00:03:07,879
for a month, and then changes
107
00:03:07,879 --> 00:03:08,439
jobs.
108
00:03:08,439 --> 00:03:09,879
The agent keeps running, still
109
00:03:09,879 --> 00:03:11,080
connected to the same customer
110
00:03:11,080 --> 00:03:12,900
data, still posting summaries to
111
00:03:12,900 --> 00:03:14,000
a channel nobody watches
112
00:03:14,000 --> 00:03:14,639
anymore.
113
00:03:14,639 --> 00:03:15,840
Nobody made a bad decision on
114
00:03:15,840 --> 00:03:17,680
purpose because the agent simply
115
00:03:17,680 --> 00:03:18,560
outlived the person who
116
00:03:18,560 --> 00:03:19,120
understood it.
117
00:03:19,120 --> 00:03:21,639
There was no shared place to
notice, which is the quiet part
118
00:03:21,639 --> 00:03:22,400
of the problem.
119
00:03:22,400 --> 00:03:24,280
Shadow AI is the other half of
the story.
120
00:03:24,280 --> 00:03:26,840
People install agents on their
own laptops and sign up for
121
00:03:26,840 --> 00:03:29,599
outside tools that connect to
company data, and those agents
122
00:03:29,599 --> 00:03:31,520
run outside the normal controls.
123
00:03:31,520 --> 00:03:33,000
Microsoft now leans on Defender
124
00:03:33,000 --> 00:03:34,800
and Intune to find some of them,
125
00:03:34,800 --> 00:03:35,960
which tells you how common this
126
00:03:35,960 --> 00:03:36,560
has become.
127
00:03:36,560 --> 00:03:40,120
The mess is real, it's growing,
and it needs a home.
128
00:03:40,120 --> 00:03:41,080
What the agent three hundred
129
00:03:41,080 --> 00:03:42,400
sixty five Admin Center actually
130
00:03:42,400 --> 00:03:43,000
is.
131
00:03:43,000 --> 00:03:44,439
If the mess needs a home, agent
132
00:03:44,439 --> 00:03:45,479
three hundred sixty five is the
133
00:03:45,479 --> 00:03:46,039
address.
134
00:03:46,039 --> 00:03:49,199
It's Microsoft's control room
for AI agents, and it lives in
135
00:03:49,199 --> 00:03:52,280
the Microsoft three hundred
sixty five admin center that IT
136
00:03:52,280 --> 00:03:53,879
teams already open every day.
137
00:03:53,879 --> 00:03:56,520
If you've watched an admin
assign licenses or manage apps,
138
00:03:56,520 --> 00:03:59,400
this is a sibling of that page,
except the list is agents
139
00:03:59,400 --> 00:04:00,159
instead of people.
140
00:04:00,159 --> 00:04:02,039
One thing is worth getting
straight right away, and that is
141
00:04:02,039 --> 00:04:03,159
what this tool is not.
142
00:04:03,159 --> 00:04:04,879
Agent three six five doesn't
build agents.
143
00:04:04,879 --> 00:04:07,199
Building happens in copilot,
studio, agent builder,
144
00:04:07,199 --> 00:04:08,400
SharePoint or foundry.
145
00:04:08,400 --> 00:04:11,120
And agent three sixty five is
everything that comes after.
146
00:04:11,120 --> 00:04:12,319
It's where an agent gets
147
00:04:12,319 --> 00:04:14,039
approved, watched, governed, and
148
00:04:14,039 --> 00:04:15,639
eventually retired, which makes
149
00:04:15,639 --> 00:04:17,079
it more like a front desk than a
150
00:04:17,079 --> 00:04:17,720
workshop.
151
00:04:17,720 --> 00:04:20,079
The whole product rests on three
plain ideas.
152
00:04:20,079 --> 00:04:22,879
Observe means you can finally
see every agent in one place.
153
00:04:22,879 --> 00:04:25,439
Governance is how you set the
rules for what agents may do and
154
00:04:25,439 --> 00:04:26,319
who may use them.
155
00:04:26,319 --> 00:04:28,800
Secure is where you protect the
data they touch, because an
156
00:04:28,800 --> 00:04:32,000
agent that can read your files
can also leak them by accident.
157
00:04:32,000 --> 00:04:33,879
Once you spot those three ideas,
158
00:04:33,879 --> 00:04:35,639
the menu stop feeling random and
159
00:04:35,639 --> 00:04:36,759
the whole thing starts to make
160
00:04:36,759 --> 00:04:37,040
sense.
161
00:04:37,040 --> 00:04:39,920
When you open the agents section
of the admin center, you land in
162
00:04:39,920 --> 00:04:41,000
a few familiar places.
163
00:04:41,000 --> 00:04:42,040
There's an overview that acts
164
00:04:42,040 --> 00:04:43,560
like a dashboard, an all agents
165
00:04:43,560 --> 00:04:44,759
area that holds the registry,
166
00:04:44,759 --> 00:04:46,560
the map and the requests queue,
167
00:04:46,560 --> 00:04:47,600
and a settings page for the
168
00:04:47,600 --> 00:04:47,959
rules.
169
00:04:47,959 --> 00:04:50,360
You don't need to memorize any
of that today because the shape
170
00:04:50,360 --> 00:04:51,920
matters more than the labels.
171
00:04:51,920 --> 00:04:53,639
Now here's where it gets
interesting.
172
00:04:53,639 --> 00:04:56,199
The most useful part of that
home is just a list, and that
173
00:04:56,199 --> 00:04:59,040
list holds a surprise most
people don't see coming.
174
00:04:59,040 --> 00:05:00,079
The agent registry.
175
00:05:00,079 --> 00:05:01,600
One list for every agent.
176
00:05:01,600 --> 00:05:04,519
The registry is the heart of the
entire setup, and it's exactly
177
00:05:04,519 --> 00:05:05,240
what it sounds like.
178
00:05:05,240 --> 00:05:07,839
It's one list of every agent
available to your company.
179
00:05:07,839 --> 00:05:10,279
No matter which tool built it or
which team shared it.
180
00:05:10,279 --> 00:05:11,720
For a beginner, the easiest way
181
00:05:11,720 --> 00:05:13,339
to read that list is to ask who
182
00:05:13,339 --> 00:05:15,519
made each agent for kinds show
183
00:05:15,519 --> 00:05:16,639
up and they're simpler than they
184
00:05:16,639 --> 00:05:17,000
sound.
185
00:05:17,000 --> 00:05:19,839
Some agents are built and
maintained by Microsoft itself,
186
00:05:19,839 --> 00:05:22,160
and some come from outside
partners who publish their
187
00:05:22,160 --> 00:05:23,600
agents for anyone to use.
188
00:05:23,600 --> 00:05:25,959
Others are built and published
by your own company for a
189
00:05:25,959 --> 00:05:29,199
specific job, like a claims
helper for the insurance team.
190
00:05:29,199 --> 00:05:30,360
A last group is shared by an
191
00:05:30,360 --> 00:05:31,600
individual creator who built
192
00:05:31,600 --> 00:05:32,759
something handy and passed it
193
00:05:32,759 --> 00:05:33,360
around.
194
00:05:33,360 --> 00:05:35,639
At the top of the registry, you
get three numbers that tell you
195
00:05:35,639 --> 00:05:36,800
how healthy things are.
196
00:05:36,800 --> 00:05:39,040
The first is the total count of
agents in the company.
197
00:05:39,040 --> 00:05:40,319
The second is the number of
198
00:05:40,319 --> 00:05:41,720
agents without owners, meaning
199
00:05:41,720 --> 00:05:42,839
the person who made them has
200
00:05:42,839 --> 00:05:43,600
left.
201
00:05:43,600 --> 00:05:46,360
The third counts the unmanaged
agents which run outside agent
202
00:05:46,360 --> 00:05:48,600
three sixty five, so they sit
outside its protection.
203
00:05:48,600 --> 00:05:51,160
Those three numbers are the
pulse of the whole estate, and
204
00:05:51,160 --> 00:05:53,360
watching them is a lot like
watching a bank balance.
205
00:05:53,360 --> 00:05:54,959
A wall of names wouldn't help
anyone.
206
00:05:54,959 --> 00:05:56,480
So the list comes with filters.
207
00:05:56,480 --> 00:05:58,920
You can narrow it down by where
an agent shows up, whether
208
00:05:58,920 --> 00:06:01,600
that's copilot teams, outlook,
the Microsoft three hundred
209
00:06:01,600 --> 00:06:03,959
sixty five apps, or SharePoint,
you can filter by the platform
210
00:06:03,959 --> 00:06:06,519
it was built on as well, or by
who published it.
211
00:06:06,519 --> 00:06:08,560
Once you find what you're
looking for, you can pin an
212
00:06:08,560 --> 00:06:10,240
agent so people can find it.
213
00:06:10,240 --> 00:06:13,439
You can upload a custom agent as
a zip file or export the whole
214
00:06:13,439 --> 00:06:14,360
list to excel.
215
00:06:14,360 --> 00:06:16,879
This is the part that catches
almost everyone off guard.
216
00:06:16,879 --> 00:06:19,800
The same agent can appear in the
registry twice, once as shared
217
00:06:19,800 --> 00:06:22,079
by creator and once as published
by your org.
218
00:06:22,079 --> 00:06:23,279
And that is not a mistake.
219
00:06:23,279 --> 00:06:24,680
It's by design, because those
220
00:06:24,680 --> 00:06:25,680
are two different lifecycle
221
00:06:25,680 --> 00:06:26,800
records with two different sets
222
00:06:26,800 --> 00:06:27,399
of actions.
223
00:06:27,399 --> 00:06:30,199
One row might offer delete,
while another offers only block,
224
00:06:30,199 --> 00:06:32,160
which is a good reason to look
before you click.
225
00:06:32,160 --> 00:06:34,079
Microsoft even warns admins not
226
00:06:34,079 --> 00:06:35,480
to treat the duplicates as an
227
00:06:35,480 --> 00:06:37,160
inventory error, which is a
228
00:06:37,160 --> 00:06:38,620
quiet way of saying people do
229
00:06:38,620 --> 00:06:39,800
exactly that.
230
00:06:39,800 --> 00:06:42,000
What an admin can actually do to
an agent.
231
00:06:42,000 --> 00:06:43,519
Seeing the list is the easy half
232
00:06:43,519 --> 00:06:44,800
and the other half is acting on
233
00:06:44,800 --> 00:06:45,199
it.
234
00:06:45,199 --> 00:06:47,839
The actions themselves are more
familiar than they sound.
235
00:06:47,839 --> 00:06:49,519
An admin can install an agent
236
00:06:49,519 --> 00:06:50,560
for a group, so it's ready
237
00:06:50,560 --> 00:06:52,000
without anyone hunting for it,
238
00:06:52,000 --> 00:06:53,759
or uninstall it when it's no
239
00:06:53,759 --> 00:06:54,439
longer wanted.
240
00:06:54,439 --> 00:06:56,995
They can block an agent across
the whole company, which stops
241
00:06:56,995 --> 00:06:59,470
everyone from using it and
unblock it later.
242
00:06:59,470 --> 00:07:00,550
If the decision changes.
243
00:07:00,550 --> 00:07:01,709
They can also delete an agent,
244
00:07:01,709 --> 00:07:03,029
though delete is gentler than it
245
00:07:03,029 --> 00:07:03,790
sounds.
246
00:07:03,790 --> 00:07:05,389
A deleted agent drops into a
247
00:07:05,389 --> 00:07:06,910
thirty day recovery window and
248
00:07:06,910 --> 00:07:08,350
can be restored before it's gone
249
00:07:08,350 --> 00:07:09,029
for good.
250
00:07:09,029 --> 00:07:11,670
Approval is where governance
gets real when someone wants to
251
00:07:11,670 --> 00:07:14,910
roll an agent out more widely,
the request lands in a queue.
252
00:07:14,910 --> 00:07:18,029
An AI administrator then reviews
what the agent does, which data
253
00:07:18,029 --> 00:07:19,470
it reaches, and who owns it.
254
00:07:19,470 --> 00:07:21,949
If it's approved, that admin
decides who gets the agent,
255
00:07:21,949 --> 00:07:24,709
whether that's one team, a few
groups, or the entire company.
256
00:07:24,709 --> 00:07:26,870
That last choice is the
difference between a quiet pilot
257
00:07:26,870 --> 00:07:28,470
and a company wide rollout.
258
00:07:28,470 --> 00:07:30,790
And it's made on purpose rather
than by accident.
259
00:07:30,790 --> 00:07:33,629
Ownership gets its own set of
tools because agents outlive the
260
00:07:33,629 --> 00:07:34,870
people who build them.
261
00:07:34,870 --> 00:07:37,790
An admin can hand an ownerless
agent to a new person.
262
00:07:37,790 --> 00:07:39,149
If the agent was made an agent
263
00:07:39,149 --> 00:07:40,430
builder, they can even add a
264
00:07:40,430 --> 00:07:41,029
second owner.
265
00:07:41,029 --> 00:07:41,949
So the whole thing doesn't
266
00:07:41,949 --> 00:07:43,230
depend on one employee staying
267
00:07:43,230 --> 00:07:43,870
forever.
268
00:07:43,870 --> 00:07:46,790
There are also bulk rules that
quietly handle the boring work.
269
00:07:46,790 --> 00:07:48,350
One rule can install Microsoft's
270
00:07:48,350 --> 00:07:50,110
own agents for everyone at once,
271
00:07:50,110 --> 00:07:51,389
and another can reassign
272
00:07:51,389 --> 00:07:52,750
ownerless agents to the former
273
00:07:52,750 --> 00:07:53,750
owner's manager.
274
00:07:53,750 --> 00:07:54,910
A third can block Ownerless
275
00:07:54,910 --> 00:07:56,329
agents that nobody has used in
276
00:07:56,329 --> 00:07:56,870
months.
277
00:07:56,870 --> 00:07:58,310
Underneath all of that sits the
278
00:07:58,310 --> 00:07:59,750
security template, which is the
279
00:07:59,750 --> 00:08:01,149
most useful idea for a beginner
280
00:08:01,149 --> 00:08:02,069
to understand.
281
00:08:02,069 --> 00:08:05,029
It's a ready made bundle of
protections drawn from intra for
282
00:08:05,029 --> 00:08:08,069
identity, purview for data
Defender for threats, and
283
00:08:08,069 --> 00:08:09,189
SharePoint for sharing.
284
00:08:09,189 --> 00:08:11,949
The whole bundle can be applied
to an agent in a single step.
285
00:08:11,949 --> 00:08:14,790
Picture a finance team building
an agent that reads contracts,
286
00:08:14,790 --> 00:08:18,310
and instead of a dozen separate
security decisions, it applies
287
00:08:18,310 --> 00:08:20,310
one template and moves on.
288
00:08:20,310 --> 00:08:23,870
Reading the dashboard usage risk
and the agent map.
289
00:08:23,870 --> 00:08:26,649
Once the agents are approved,
the job shifts from doing to
290
00:08:26,649 --> 00:08:29,430
watching, and the dashboard is
built for exactly that.
291
00:08:29,430 --> 00:08:31,009
The overview page shows a thirty
292
00:08:31,009 --> 00:08:32,029
day snapshot of the whole
293
00:08:32,029 --> 00:08:32,669
estate.
294
00:08:32,669 --> 00:08:34,149
It counts the agents, the people
295
00:08:34,149 --> 00:08:35,429
using them, the hours of work
296
00:08:35,429 --> 00:08:36,629
they did, and the outside
297
00:08:36,629 --> 00:08:37,149
platforms.
298
00:08:37,149 --> 00:08:39,149
The registry connects to those
numbers.
299
00:08:39,149 --> 00:08:40,309
Answer a question every leader
300
00:08:40,309 --> 00:08:41,590
eventually asks, which is
301
00:08:41,590 --> 00:08:42,750
whether any of this is worth the
302
00:08:42,750 --> 00:08:43,269
money.
303
00:08:43,269 --> 00:08:45,750
The dashboard also lines up the
jobs that need a human.
304
00:08:45,750 --> 00:08:48,230
There's a card for requests
waiting on approval, one for
305
00:08:48,230 --> 00:08:50,909
agents without owners, one for
agents with errors, and one for
306
00:08:50,909 --> 00:08:51,870
agents at risk.
307
00:08:51,870 --> 00:08:53,389
That last card is the one to
notice.
308
00:08:53,389 --> 00:08:56,009
Security tools like purview,
entra, and Defender each watch
309
00:08:56,009 --> 00:08:58,950
for different trouble, and the
registry pulls their warnings
310
00:08:58,950 --> 00:08:59,669
into one column.
311
00:08:59,669 --> 00:09:00,830
You can click into.
312
00:09:00,830 --> 00:09:03,629
From there, an admin sees the
signals grouped by how serious
313
00:09:03,629 --> 00:09:05,950
they are, along with how many
times each one fired.
314
00:09:05,950 --> 00:09:08,590
When the list gets long, a list
stops helping, and that's where
315
00:09:08,590 --> 00:09:09,870
the agent map earns its place.
316
00:09:09,870 --> 00:09:11,090
Instead of rows of names, it
317
00:09:11,090 --> 00:09:13,029
draws agents as icons grouped by
318
00:09:13,029 --> 00:09:14,429
the platform they came from, so
319
00:09:14,429 --> 00:09:15,629
you can see the pattern at a
320
00:09:15,629 --> 00:09:15,909
glance.
321
00:09:15,909 --> 00:09:18,669
You can filter the map by
status, publisher, platform,
322
00:09:18,669 --> 00:09:19,789
channel, or usage.
323
00:09:19,789 --> 00:09:21,029
Drilling into a single agent
324
00:09:21,029 --> 00:09:22,230
shows its owner and how it's
325
00:09:22,230 --> 00:09:22,909
behaving.
326
00:09:22,909 --> 00:09:26,070
A newer preview view goes a step
further and shows one agent, the
327
00:09:26,070 --> 00:09:28,990
people who use it and the tools
it calls, and the tool lights up
328
00:09:28,990 --> 00:09:30,669
when its error rate climbs.
329
00:09:30,669 --> 00:09:33,149
The honest part is that none of
this is instant or complete.
330
00:09:33,149 --> 00:09:34,269
The risk numbers in the admin
331
00:09:34,269 --> 00:09:35,350
center can lag behind the
332
00:09:35,350 --> 00:09:36,710
security portals by up to an
333
00:09:36,710 --> 00:09:37,149
hour.
334
00:09:37,149 --> 00:09:40,190
The overview card shows only the
top five platforms, so the full
335
00:09:40,190 --> 00:09:41,830
picture lives in the registry.
336
00:09:41,830 --> 00:09:44,870
Draft agents are only visible
from Copilot Studio for now, and
337
00:09:44,870 --> 00:09:47,629
the map itself needs the higher
tier license, which means the
338
00:09:47,629 --> 00:09:50,149
view you get depends on what
your company bought.
339
00:09:50,149 --> 00:09:52,070
Common mistakes and honest
limits.
340
00:09:52,070 --> 00:09:55,070
Nobody gets this right on the
first try, and the mistakes tend
341
00:09:55,070 --> 00:09:56,110
to follow a pattern.
342
00:09:56,110 --> 00:09:57,509
The most common one is blocking
343
00:09:57,509 --> 00:09:58,470
agents before you have a
344
00:09:58,470 --> 00:09:59,990
registry, which is like firing
345
00:09:59,990 --> 00:10:01,230
people before you know who works
346
00:10:01,230 --> 00:10:01,629
for you.
347
00:10:01,629 --> 00:10:04,070
Admins block the loudest agent
they've heard about and never
348
00:10:04,070 --> 00:10:06,309
find the quiet ones doing damage
in the background.
349
00:10:06,309 --> 00:10:07,990
The fix is unglamorous and
effective.
350
00:10:07,990 --> 00:10:09,190
Turn the registry on.
351
00:10:09,190 --> 00:10:11,789
Let it fill up and only then
start making decisions.
352
00:10:11,789 --> 00:10:14,389
The next trap is ignoring
ownerless agents until the
353
00:10:14,389 --> 00:10:15,669
number is frightening.
354
00:10:15,669 --> 00:10:18,250
Every departure adds to that
count, and an agent left behind
355
00:10:18,250 --> 00:10:20,230
keeps its access to whatever
data it was given.
356
00:10:20,230 --> 00:10:22,350
That is a risk that grows in the
dark.
357
00:10:22,350 --> 00:10:25,350
Another common slip is assuming
delete means gone.
358
00:10:25,350 --> 00:10:28,029
Delete actually opens a thirty
day window where the agent stays
359
00:10:28,029 --> 00:10:30,509
recoverable and stays recorded
in the audit log.
360
00:10:30,509 --> 00:10:32,009
There's also the duplicate row
361
00:10:32,009 --> 00:10:33,230
where an admin deletes one
362
00:10:33,230 --> 00:10:34,350
entry, thinking it's a glitch
363
00:10:34,350 --> 00:10:35,590
and is surprised the agent never
364
00:10:35,590 --> 00:10:35,909
left.
365
00:10:35,909 --> 00:10:39,350
One more is reading early usage
numbers as the whole truth data
366
00:10:39,350 --> 00:10:41,950
for outside agents only starts
counting the day the license
367
00:10:41,950 --> 00:10:44,669
switches on, so the first weeks
always look thin.
368
00:10:44,669 --> 00:10:46,870
Then there are the limits
Microsoft states plainly, and
369
00:10:46,870 --> 00:10:47,669
they're worth repeating.
370
00:10:47,669 --> 00:10:50,309
Without the polish, not every
agent appears automatically.
371
00:10:50,309 --> 00:10:52,990
Anything built outside
Microsoft's channels without a
372
00:10:52,990 --> 00:10:56,570
Microsoft agent identity needs
extra steps or a registry sink
373
00:10:56,570 --> 00:10:57,509
to show up.
374
00:10:57,509 --> 00:10:59,090
Admin actions can quietly fail
375
00:10:59,090 --> 00:11:00,230
on agents behind a power
376
00:11:00,230 --> 00:11:01,870
platform firewall in active
377
00:11:01,870 --> 00:11:03,110
enforcement mode because the
378
00:11:03,110 --> 00:11:04,409
request arrives from the wrong
379
00:11:04,409 --> 00:11:05,149
address.
380
00:11:05,149 --> 00:11:06,870
An AI administrator can monitor
381
00:11:06,870 --> 00:11:08,230
plenty, but can't change every
382
00:11:08,230 --> 00:11:09,610
identity setting, since some of
383
00:11:09,610 --> 00:11:10,710
that needs a more privileged
384
00:11:10,710 --> 00:11:11,149
role.
385
00:11:11,149 --> 00:11:12,309
Draft agents from several
386
00:11:12,309 --> 00:11:13,909
platforms still aren't visible,
387
00:11:13,909 --> 00:11:15,269
and several of the best views,
388
00:11:15,269 --> 00:11:16,509
including the risk column and
389
00:11:16,509 --> 00:11:18,129
the map, need the higher tier
390
00:11:18,129 --> 00:11:18,830
license.
391
00:11:18,830 --> 00:11:21,190
None of that makes the tool
weak, and it makes it honest.
392
00:11:21,190 --> 00:11:22,389
Honesty is what you want from
393
00:11:22,389 --> 00:11:23,509
something whose job is keeping
394
00:11:23,509 --> 00:11:24,750
an eye on software that can act
395
00:11:24,750 --> 00:11:25,389
without you.
396
00:11:25,389 --> 00:11:26,509
The point of listing the limits
397
00:11:26,509 --> 00:11:27,710
is so you don't expect a magic
398
00:11:27,710 --> 00:11:28,389
switch.
399
00:11:28,389 --> 00:11:31,269
What you get is a control room
and not a babysitter, and a
400
00:11:31,269 --> 00:11:34,149
control room only helps if
someone is actually in it.
401
00:11:34,149 --> 00:11:36,470
How it fits with Microsoft three
hundred sixty five and Azure.
402
00:11:36,470 --> 00:11:37,549
The admin center is the front
403
00:11:37,549 --> 00:11:38,529
door, but the muscle behind
404
00:11:38,529 --> 00:11:39,769
agent three hundred sixty five
405
00:11:39,769 --> 00:11:40,950
comes from tools that people in
406
00:11:40,950 --> 00:11:42,029
the Microsoft world already
407
00:11:42,029 --> 00:11:42,509
know.
408
00:11:42,509 --> 00:11:43,769
Microsoft Entra gives every
409
00:11:43,769 --> 00:11:45,190
agent an identity, so an agent
410
00:11:45,190 --> 00:11:46,389
has permissions the same way an
411
00:11:46,389 --> 00:11:47,269
employee does.
412
00:11:47,269 --> 00:11:48,629
Microsoft Defender watches for
413
00:11:48,629 --> 00:11:49,789
threats and attacks, and
414
00:11:49,789 --> 00:11:51,190
Microsoft Purview looks after
415
00:11:51,190 --> 00:11:52,750
the data an agent touches so it
416
00:11:52,750 --> 00:11:53,830
doesn't overshare.
417
00:11:53,830 --> 00:11:54,429
Microsoft.
418
00:11:54,429 --> 00:11:56,950
Intune handles the devices some
agents run on.
419
00:11:56,950 --> 00:11:58,269
None of these are new products,
420
00:11:58,269 --> 00:11:59,309
and that's the whole design,
421
00:11:59,309 --> 00:12:00,649
because agent three sixty five
422
00:12:00,649 --> 00:12:01,990
simply extends controls you
423
00:12:01,990 --> 00:12:03,350
already trust to a new kind of
424
00:12:03,350 --> 00:12:04,590
worker.
425
00:12:04,590 --> 00:12:07,350
Azure enters the picture in a
specific and satisfying way.
426
00:12:07,350 --> 00:12:10,190
Agents built with Microsoft
Foundry Run on Azure, and an
427
00:12:10,190 --> 00:12:13,029
admin can start or stop one
right from the admin center,
428
00:12:13,029 --> 00:12:13,909
starting at provisions.
429
00:12:13,909 --> 00:12:15,190
The underlying compute and
430
00:12:15,190 --> 00:12:16,309
stopping it releases that
431
00:12:16,309 --> 00:12:16,710
compute.
432
00:12:16,710 --> 00:12:19,269
It's a small detail with a real
consequence, because the control
433
00:12:19,269 --> 00:12:21,029
room reaches all the way down
into the cloud.
434
00:12:21,029 --> 00:12:22,629
Resources and agent depends on.
435
00:12:22,629 --> 00:12:24,669
There's also a bridge to the
wider world.
436
00:12:24,669 --> 00:12:26,429
A registry sync feature still in
437
00:12:26,429 --> 00:12:28,090
preview can connect agent three
438
00:12:28,090 --> 00:12:29,429
sixty five to outside platforms
439
00:12:29,429 --> 00:12:30,789
like Amazon Bedrock and Google
440
00:12:30,789 --> 00:12:31,429
Cloud.
441
00:12:31,429 --> 00:12:33,909
Agents built there then show up
in the same list.
442
00:12:33,909 --> 00:12:35,389
Microsoft has lined up partner
443
00:12:35,389 --> 00:12:36,470
agents from companies like
444
00:12:36,470 --> 00:12:38,470
spark, Zendesk, and N810 that
445
00:12:38,470 --> 00:12:39,710
plug straight into the control
446
00:12:39,710 --> 00:12:39,990
room.
447
00:12:39,990 --> 00:12:42,750
That matters because most
companies won't run everything
448
00:12:42,750 --> 00:12:44,470
inside one vendor's walls.
449
00:12:44,470 --> 00:12:47,149
Then there's the money, because
that always anchors the story.
450
00:12:47,149 --> 00:12:50,070
Agent three sixty five costs
fifteen dollars per user per
451
00:12:50,070 --> 00:12:52,830
month on its own, or it comes
included in Microsoft three
452
00:12:52,830 --> 00:12:57,029
hundred sixty five E7 and it
works best alongside E5.
453
00:12:57,029 --> 00:12:58,389
A single licensed user is enough
454
00:12:58,389 --> 00:12:59,470
to switch it on for the whole
455
00:12:59,470 --> 00:13:00,149
tenant.
456
00:13:00,149 --> 00:13:01,350
So why should someone who never
457
00:13:01,350 --> 00:13:02,710
opens the admin center care at
458
00:13:02,710 --> 00:13:03,070
all?
459
00:13:03,070 --> 00:13:04,429
The answer is that this page
460
00:13:04,429 --> 00:13:05,909
decides which agents you're
461
00:13:05,909 --> 00:13:07,590
allowed to use at work, and that
462
00:13:07,590 --> 00:13:08,830
decision quietly shapes your
463
00:13:08,830 --> 00:13:09,149
day.
464
00:13:09,149 --> 00:13:11,909
It shapes everything from the
replies you draft to the tickets
465
00:13:11,909 --> 00:13:13,470
you never have to read.
466
00:13:13,470 --> 00:13:15,149
A quick recap and a question for
you.
467
00:13:15,149 --> 00:13:16,629
So here's where we've landed.
468
00:13:16,629 --> 00:13:18,149
AI agents do real work now and
469
00:13:18,149 --> 00:13:19,710
they multiply faster than anyone
470
00:13:19,710 --> 00:13:20,549
can track.
471
00:13:20,549 --> 00:13:22,070
Agent three sixty five gives a
472
00:13:22,070 --> 00:13:23,350
company one place to keep those
473
00:13:23,350 --> 00:13:24,870
agents visible, approved and
474
00:13:24,870 --> 00:13:25,509
accountable.
475
00:13:25,509 --> 00:13:26,710
It won't build a single agent
476
00:13:26,710 --> 00:13:27,789
for you, and it won't close
477
00:13:27,789 --> 00:13:28,629
every gap.
478
00:13:28,629 --> 00:13:29,990
What it does is turn a scattered
479
00:13:29,990 --> 00:13:31,750
mess into one list you can
480
00:13:31,750 --> 00:13:32,350
actually manage.
481
00:13:32,350 --> 00:13:33,990
Which brings me to my question
for you.
482
00:13:33,990 --> 00:13:37,029
If you had to hand one task to
an agent tomorrow, what would
483
00:13:37,029 --> 00:13:39,470
you trust it to do without
checking on it first?
484
00:13:39,470 --> 00:13:42,210
I would really like to hear your
answer, because that choice says
485
00:13:42,210 --> 00:13:44,710
a lot about how comfortable
we've become with software that
486
00:13:44,710 --> 00:13:46,429
works while we look away.
487
00:13:46,429 --> 00:13:47,750
If this made the topic feel less
488
00:13:47,750 --> 00:13:50,250
intimidating, subscribe to M365
489
00:13:50,250 --> 00:13:51,789
FM to master the tools and the
490
00:13:51,789 --> 00:13:53,669
mindset shaping the future of
491
00:13:53,669 --> 00:13:54,269
work.
00:00:00,040 --> 00:00:02,279
Welcome to the M365 FM podcast,
2
00:00:02,279 --> 00:00:03,680
where we explore the people,
3
00:00:03,680 --> 00:00:05,679
ideas and technologies shaping
4
00:00:05,679 --> 00:00:07,200
the future of work somewhere in
5
00:00:07,200 --> 00:00:08,119
your company.
6
00:00:08,119 --> 00:00:10,800
An AI agent is reading your
files, and the only place that
7
00:00:10,800 --> 00:00:13,039
knows who owns it is a page most
people never open.
8
00:00:13,039 --> 00:00:15,839
That sounds dramatic, but it is
just the normal state of AI at
9
00:00:15,839 --> 00:00:16,800
work right now.
10
00:00:16,800 --> 00:00:18,079
Agents are easy to build and
11
00:00:18,079 --> 00:00:19,719
easy to forget, so they pile up
12
00:00:19,719 --> 00:00:21,519
across teams, tools, and
13
00:00:21,519 --> 00:00:22,199
laptops.
14
00:00:22,199 --> 00:00:25,559
Welcome to the M365 FM podcast,
where we explore the people,
15
00:00:25,559 --> 00:00:28,239
ideas and technologies shaping
the future of work.
16
00:00:28,239 --> 00:00:30,660
Today we're talking about
Microsoft Agent three sixty
17
00:00:30,660 --> 00:00:33,640
five, the control room Microsoft
built inside the Microsoft three
18
00:00:33,640 --> 00:00:36,399
hundred sixty five Admin Center
to keep track of all of them.
19
00:00:36,399 --> 00:00:39,399
By the end, you'll know what it
is, how it works, and where it
20
00:00:39,399 --> 00:00:40,840
honestly falls short.
21
00:00:40,840 --> 00:00:43,119
What an AI agent actually is.
22
00:00:43,119 --> 00:00:45,520
The word agent gets thrown
around like everyone already
23
00:00:45,520 --> 00:00:47,880
agrees on what it means, and
most people don't.
24
00:00:47,880 --> 00:00:49,719
An agent is software that does
work for you.
25
00:00:49,719 --> 00:00:50,759
Instead of just answering
26
00:00:50,759 --> 00:00:52,439
questions, a chat bot waits for
27
00:00:52,439 --> 00:00:53,359
you to type something and
28
00:00:53,359 --> 00:00:54,719
replies while an agent goes
29
00:00:54,719 --> 00:00:55,920
further and actually finishes a
30
00:00:55,920 --> 00:00:56,320
task.
31
00:00:56,320 --> 00:00:58,039
It follows the instructions
someone gave.
32
00:00:58,039 --> 00:01:01,039
It draws on the knowledge it's
allowed to use, and then reaches
33
00:01:01,039 --> 00:01:02,600
for tools to get the job done.
34
00:01:02,600 --> 00:01:05,480
Those tools are what turn a
clever reply into finished work.
35
00:01:05,480 --> 00:01:08,000
They let an agent open a file,
send an email, or update a
36
00:01:08,000 --> 00:01:10,640
record picture, an agent that
watches a shared in-box and
37
00:01:10,640 --> 00:01:13,439
drafts a reply to every customer
question that lands there.
38
00:01:13,439 --> 00:01:14,760
You still hit send, but the
39
00:01:14,760 --> 00:01:16,159
slow, repetitive part is already
40
00:01:16,159 --> 00:01:16,719
finished.
41
00:01:16,719 --> 00:01:18,040
Now imagine a second one on a
42
00:01:18,040 --> 00:01:19,239
support queue, reading each
43
00:01:19,239 --> 00:01:20,280
ticket and sending it to the
44
00:01:20,280 --> 00:01:21,680
right team with a summary
45
00:01:21,680 --> 00:01:22,400
attached.
46
00:01:22,400 --> 00:01:23,560
Then there's the quiet one that
47
00:01:23,560 --> 00:01:24,920
answers HR questions like how
48
00:01:24,920 --> 00:01:26,079
much vacation you have left
49
00:01:26,079 --> 00:01:27,000
straight from the employee
50
00:01:27,000 --> 00:01:27,400
handbook.
51
00:01:27,400 --> 00:01:29,760
None of this feels like science
fiction anymore.
52
00:01:29,760 --> 00:01:31,519
And that quiet ordinariness is
53
00:01:31,519 --> 00:01:33,120
exactly why agents spread so
54
00:01:33,120 --> 00:01:33,439
fast.
55
00:01:33,439 --> 00:01:36,799
Once one team proves they work,
people build them in places you
56
00:01:36,799 --> 00:01:38,079
might already recognize.
57
00:01:38,079 --> 00:01:41,319
Microsoft Copilot Studio is the
main workshop, and it's where
58
00:01:41,319 --> 00:01:43,040
most custom agents get made.
59
00:01:43,040 --> 00:01:44,120
Others come out of Agent
60
00:01:44,120 --> 00:01:46,079
Builder, inside copilot, out of
61
00:01:46,079 --> 00:01:47,480
SharePoint, or out of Microsoft
62
00:01:47,480 --> 00:01:47,840
Foundry.
63
00:01:47,840 --> 00:01:49,319
Over on the other side, the
64
00:01:49,319 --> 00:01:51,079
Admin Center sorts them by type
65
00:01:51,079 --> 00:01:52,000
so it can tell a simple
66
00:01:52,000 --> 00:01:53,519
instructions only agent apart
67
00:01:53,519 --> 00:01:54,879
from one running a custom engine
68
00:01:54,879 --> 00:01:56,120
or a full business process, you
69
00:01:56,120 --> 00:01:57,099
don't need those labels to
70
00:01:57,099 --> 00:01:57,920
follow along.
71
00:01:57,920 --> 00:02:01,280
What matters is that every agent
is a small worker with a job, a
72
00:02:01,280 --> 00:02:03,859
set of permissions, and an owner
hold on to that owner idea
73
00:02:03,859 --> 00:02:06,359
because it becomes the whole
story in a minute.
74
00:02:06,359 --> 00:02:09,120
Why agents pile up and why that
becomes a problem.
75
00:02:09,120 --> 00:02:11,960
Creating an agent has never been
easier, and that's the problem.
76
00:02:11,960 --> 00:02:14,419
A person in finance can build
one before lunch without telling
77
00:02:14,419 --> 00:02:18,000
it, and a person in HR can do
the same by the afternoon.
78
00:02:18,000 --> 00:02:20,759
Multiply that across a few
thousand people and the agents
79
00:02:20,759 --> 00:02:23,039
start to outnumber the people
who understand them.
80
00:02:23,039 --> 00:02:25,800
Management gets scattered too,
because some agents live in
81
00:02:25,800 --> 00:02:28,919
copilot studios, some in the
teams admin center, and some in
82
00:02:28,919 --> 00:02:30,319
the security tools.
83
00:02:30,319 --> 00:02:31,759
No single person ends up with
84
00:02:31,759 --> 00:02:33,319
the full picture, which is how a
85
00:02:33,319 --> 00:02:34,759
small convenience turns into a
86
00:02:34,759 --> 00:02:35,719
quiet liability.
87
00:02:35,719 --> 00:02:36,960
Microsoft says it plainly in its
88
00:02:36,960 --> 00:02:38,520
own guidance you can't govern
89
00:02:38,520 --> 00:02:39,919
what you can't see, and you
90
00:02:39,919 --> 00:02:40,879
can't secure what you don't
91
00:02:40,879 --> 00:02:41,479
understand.
92
00:02:41,479 --> 00:02:44,120
That line matters because the
controls most companies already
93
00:02:44,120 --> 00:02:47,120
have were built for people,
apps, and data, not for software
94
00:02:47,120 --> 00:02:48,360
that acts on its own.
95
00:02:48,360 --> 00:02:50,439
When the pieces don't talk to
each other, you get what the
96
00:02:50,439 --> 00:02:52,479
industry calls agent sprawl.
97
00:02:52,479 --> 00:02:53,680
It's a fancy name for a simple
98
00:02:53,680 --> 00:02:55,159
mess, where agents multiply
99
00:02:55,159 --> 00:02:56,300
across teams with no clear
100
00:02:56,300 --> 00:02:56,919
oversight.
101
00:02:56,919 --> 00:02:59,759
Nobody can say for sure what
each one can reach or how it
102
00:02:59,759 --> 00:03:00,879
behaves over time.
103
00:03:00,879 --> 00:03:03,800
This scenario plays out
constantly in real companies.
104
00:03:03,800 --> 00:03:04,900
Someone builds an agent to
105
00:03:04,900 --> 00:03:06,520
summarize sales calls, uses it
106
00:03:06,520 --> 00:03:07,879
for a month, and then changes
107
00:03:07,879 --> 00:03:08,439
jobs.
108
00:03:08,439 --> 00:03:09,879
The agent keeps running, still
109
00:03:09,879 --> 00:03:11,080
connected to the same customer
110
00:03:11,080 --> 00:03:12,900
data, still posting summaries to
111
00:03:12,900 --> 00:03:14,000
a channel nobody watches
112
00:03:14,000 --> 00:03:14,639
anymore.
113
00:03:14,639 --> 00:03:15,840
Nobody made a bad decision on
114
00:03:15,840 --> 00:03:17,680
purpose because the agent simply
115
00:03:17,680 --> 00:03:18,560
outlived the person who
116
00:03:18,560 --> 00:03:19,120
understood it.
117
00:03:19,120 --> 00:03:21,639
There was no shared place to
notice, which is the quiet part
118
00:03:21,639 --> 00:03:22,400
of the problem.
119
00:03:22,400 --> 00:03:24,280
Shadow AI is the other half of
the story.
120
00:03:24,280 --> 00:03:26,840
People install agents on their
own laptops and sign up for
121
00:03:26,840 --> 00:03:29,599
outside tools that connect to
company data, and those agents
122
00:03:29,599 --> 00:03:31,520
run outside the normal controls.
123
00:03:31,520 --> 00:03:33,000
Microsoft now leans on Defender
124
00:03:33,000 --> 00:03:34,800
and Intune to find some of them,
125
00:03:34,800 --> 00:03:35,960
which tells you how common this
126
00:03:35,960 --> 00:03:36,560
has become.
127
00:03:36,560 --> 00:03:40,120
The mess is real, it's growing,
and it needs a home.
128
00:03:40,120 --> 00:03:41,080
What the agent three hundred
129
00:03:41,080 --> 00:03:42,400
sixty five Admin Center actually
130
00:03:42,400 --> 00:03:43,000
is.
131
00:03:43,000 --> 00:03:44,439
If the mess needs a home, agent
132
00:03:44,439 --> 00:03:45,479
three hundred sixty five is the
133
00:03:45,479 --> 00:03:46,039
address.
134
00:03:46,039 --> 00:03:49,199
It's Microsoft's control room
for AI agents, and it lives in
135
00:03:49,199 --> 00:03:52,280
the Microsoft three hundred
sixty five admin center that IT
136
00:03:52,280 --> 00:03:53,879
teams already open every day.
137
00:03:53,879 --> 00:03:56,520
If you've watched an admin
assign licenses or manage apps,
138
00:03:56,520 --> 00:03:59,400
this is a sibling of that page,
except the list is agents
139
00:03:59,400 --> 00:04:00,159
instead of people.
140
00:04:00,159 --> 00:04:02,039
One thing is worth getting
straight right away, and that is
141
00:04:02,039 --> 00:04:03,159
what this tool is not.
142
00:04:03,159 --> 00:04:04,879
Agent three six five doesn't
build agents.
143
00:04:04,879 --> 00:04:07,199
Building happens in copilot,
studio, agent builder,
144
00:04:07,199 --> 00:04:08,400
SharePoint or foundry.
145
00:04:08,400 --> 00:04:11,120
And agent three sixty five is
everything that comes after.
146
00:04:11,120 --> 00:04:12,319
It's where an agent gets
147
00:04:12,319 --> 00:04:14,039
approved, watched, governed, and
148
00:04:14,039 --> 00:04:15,639
eventually retired, which makes
149
00:04:15,639 --> 00:04:17,079
it more like a front desk than a
150
00:04:17,079 --> 00:04:17,720
workshop.
151
00:04:17,720 --> 00:04:20,079
The whole product rests on three
plain ideas.
152
00:04:20,079 --> 00:04:22,879
Observe means you can finally
see every agent in one place.
153
00:04:22,879 --> 00:04:25,439
Governance is how you set the
rules for what agents may do and
154
00:04:25,439 --> 00:04:26,319
who may use them.
155
00:04:26,319 --> 00:04:28,800
Secure is where you protect the
data they touch, because an
156
00:04:28,800 --> 00:04:32,000
agent that can read your files
can also leak them by accident.
157
00:04:32,000 --> 00:04:33,879
Once you spot those three ideas,
158
00:04:33,879 --> 00:04:35,639
the menu stop feeling random and
159
00:04:35,639 --> 00:04:36,759
the whole thing starts to make
160
00:04:36,759 --> 00:04:37,040
sense.
161
00:04:37,040 --> 00:04:39,920
When you open the agents section
of the admin center, you land in
162
00:04:39,920 --> 00:04:41,000
a few familiar places.
163
00:04:41,000 --> 00:04:42,040
There's an overview that acts
164
00:04:42,040 --> 00:04:43,560
like a dashboard, an all agents
165
00:04:43,560 --> 00:04:44,759
area that holds the registry,
166
00:04:44,759 --> 00:04:46,560
the map and the requests queue,
167
00:04:46,560 --> 00:04:47,600
and a settings page for the
168
00:04:47,600 --> 00:04:47,959
rules.
169
00:04:47,959 --> 00:04:50,360
You don't need to memorize any
of that today because the shape
170
00:04:50,360 --> 00:04:51,920
matters more than the labels.
171
00:04:51,920 --> 00:04:53,639
Now here's where it gets
interesting.
172
00:04:53,639 --> 00:04:56,199
The most useful part of that
home is just a list, and that
173
00:04:56,199 --> 00:04:59,040
list holds a surprise most
people don't see coming.
174
00:04:59,040 --> 00:05:00,079
The agent registry.
175
00:05:00,079 --> 00:05:01,600
One list for every agent.
176
00:05:01,600 --> 00:05:04,519
The registry is the heart of the
entire setup, and it's exactly
177
00:05:04,519 --> 00:05:05,240
what it sounds like.
178
00:05:05,240 --> 00:05:07,839
It's one list of every agent
available to your company.
179
00:05:07,839 --> 00:05:10,279
No matter which tool built it or
which team shared it.
180
00:05:10,279 --> 00:05:11,720
For a beginner, the easiest way
181
00:05:11,720 --> 00:05:13,339
to read that list is to ask who
182
00:05:13,339 --> 00:05:15,519
made each agent for kinds show
183
00:05:15,519 --> 00:05:16,639
up and they're simpler than they
184
00:05:16,639 --> 00:05:17,000
sound.
185
00:05:17,000 --> 00:05:19,839
Some agents are built and
maintained by Microsoft itself,
186
00:05:19,839 --> 00:05:22,160
and some come from outside
partners who publish their
187
00:05:22,160 --> 00:05:23,600
agents for anyone to use.
188
00:05:23,600 --> 00:05:25,959
Others are built and published
by your own company for a
189
00:05:25,959 --> 00:05:29,199
specific job, like a claims
helper for the insurance team.
190
00:05:29,199 --> 00:05:30,360
A last group is shared by an
191
00:05:30,360 --> 00:05:31,600
individual creator who built
192
00:05:31,600 --> 00:05:32,759
something handy and passed it
193
00:05:32,759 --> 00:05:33,360
around.
194
00:05:33,360 --> 00:05:35,639
At the top of the registry, you
get three numbers that tell you
195
00:05:35,639 --> 00:05:36,800
how healthy things are.
196
00:05:36,800 --> 00:05:39,040
The first is the total count of
agents in the company.
197
00:05:39,040 --> 00:05:40,319
The second is the number of
198
00:05:40,319 --> 00:05:41,720
agents without owners, meaning
199
00:05:41,720 --> 00:05:42,839
the person who made them has
200
00:05:42,839 --> 00:05:43,600
left.
201
00:05:43,600 --> 00:05:46,360
The third counts the unmanaged
agents which run outside agent
202
00:05:46,360 --> 00:05:48,600
three sixty five, so they sit
outside its protection.
203
00:05:48,600 --> 00:05:51,160
Those three numbers are the
pulse of the whole estate, and
204
00:05:51,160 --> 00:05:53,360
watching them is a lot like
watching a bank balance.
205
00:05:53,360 --> 00:05:54,959
A wall of names wouldn't help
anyone.
206
00:05:54,959 --> 00:05:56,480
So the list comes with filters.
207
00:05:56,480 --> 00:05:58,920
You can narrow it down by where
an agent shows up, whether
208
00:05:58,920 --> 00:06:01,600
that's copilot teams, outlook,
the Microsoft three hundred
209
00:06:01,600 --> 00:06:03,959
sixty five apps, or SharePoint,
you can filter by the platform
210
00:06:03,959 --> 00:06:06,519
it was built on as well, or by
who published it.
211
00:06:06,519 --> 00:06:08,560
Once you find what you're
looking for, you can pin an
212
00:06:08,560 --> 00:06:10,240
agent so people can find it.
213
00:06:10,240 --> 00:06:13,439
You can upload a custom agent as
a zip file or export the whole
214
00:06:13,439 --> 00:06:14,360
list to excel.
215
00:06:14,360 --> 00:06:16,879
This is the part that catches
almost everyone off guard.
216
00:06:16,879 --> 00:06:19,800
The same agent can appear in the
registry twice, once as shared
217
00:06:19,800 --> 00:06:22,079
by creator and once as published
by your org.
218
00:06:22,079 --> 00:06:23,279
And that is not a mistake.
219
00:06:23,279 --> 00:06:24,680
It's by design, because those
220
00:06:24,680 --> 00:06:25,680
are two different lifecycle
221
00:06:25,680 --> 00:06:26,800
records with two different sets
222
00:06:26,800 --> 00:06:27,399
of actions.
223
00:06:27,399 --> 00:06:30,199
One row might offer delete,
while another offers only block,
224
00:06:30,199 --> 00:06:32,160
which is a good reason to look
before you click.
225
00:06:32,160 --> 00:06:34,079
Microsoft even warns admins not
226
00:06:34,079 --> 00:06:35,480
to treat the duplicates as an
227
00:06:35,480 --> 00:06:37,160
inventory error, which is a
228
00:06:37,160 --> 00:06:38,620
quiet way of saying people do
229
00:06:38,620 --> 00:06:39,800
exactly that.
230
00:06:39,800 --> 00:06:42,000
What an admin can actually do to
an agent.
231
00:06:42,000 --> 00:06:43,519
Seeing the list is the easy half
232
00:06:43,519 --> 00:06:44,800
and the other half is acting on
233
00:06:44,800 --> 00:06:45,199
it.
234
00:06:45,199 --> 00:06:47,839
The actions themselves are more
familiar than they sound.
235
00:06:47,839 --> 00:06:49,519
An admin can install an agent
236
00:06:49,519 --> 00:06:50,560
for a group, so it's ready
237
00:06:50,560 --> 00:06:52,000
without anyone hunting for it,
238
00:06:52,000 --> 00:06:53,759
or uninstall it when it's no
239
00:06:53,759 --> 00:06:54,439
longer wanted.
240
00:06:54,439 --> 00:06:56,995
They can block an agent across
the whole company, which stops
241
00:06:56,995 --> 00:06:59,470
everyone from using it and
unblock it later.
242
00:06:59,470 --> 00:07:00,550
If the decision changes.
243
00:07:00,550 --> 00:07:01,709
They can also delete an agent,
244
00:07:01,709 --> 00:07:03,029
though delete is gentler than it
245
00:07:03,029 --> 00:07:03,790
sounds.
246
00:07:03,790 --> 00:07:05,389
A deleted agent drops into a
247
00:07:05,389 --> 00:07:06,910
thirty day recovery window and
248
00:07:06,910 --> 00:07:08,350
can be restored before it's gone
249
00:07:08,350 --> 00:07:09,029
for good.
250
00:07:09,029 --> 00:07:11,670
Approval is where governance
gets real when someone wants to
251
00:07:11,670 --> 00:07:14,910
roll an agent out more widely,
the request lands in a queue.
252
00:07:14,910 --> 00:07:18,029
An AI administrator then reviews
what the agent does, which data
253
00:07:18,029 --> 00:07:19,470
it reaches, and who owns it.
254
00:07:19,470 --> 00:07:21,949
If it's approved, that admin
decides who gets the agent,
255
00:07:21,949 --> 00:07:24,709
whether that's one team, a few
groups, or the entire company.
256
00:07:24,709 --> 00:07:26,870
That last choice is the
difference between a quiet pilot
257
00:07:26,870 --> 00:07:28,470
and a company wide rollout.
258
00:07:28,470 --> 00:07:30,790
And it's made on purpose rather
than by accident.
259
00:07:30,790 --> 00:07:33,629
Ownership gets its own set of
tools because agents outlive the
260
00:07:33,629 --> 00:07:34,870
people who build them.
261
00:07:34,870 --> 00:07:37,790
An admin can hand an ownerless
agent to a new person.
262
00:07:37,790 --> 00:07:39,149
If the agent was made an agent
263
00:07:39,149 --> 00:07:40,430
builder, they can even add a
264
00:07:40,430 --> 00:07:41,029
second owner.
265
00:07:41,029 --> 00:07:41,949
So the whole thing doesn't
266
00:07:41,949 --> 00:07:43,230
depend on one employee staying
267
00:07:43,230 --> 00:07:43,870
forever.
268
00:07:43,870 --> 00:07:46,790
There are also bulk rules that
quietly handle the boring work.
269
00:07:46,790 --> 00:07:48,350
One rule can install Microsoft's
270
00:07:48,350 --> 00:07:50,110
own agents for everyone at once,
271
00:07:50,110 --> 00:07:51,389
and another can reassign
272
00:07:51,389 --> 00:07:52,750
ownerless agents to the former
273
00:07:52,750 --> 00:07:53,750
owner's manager.
274
00:07:53,750 --> 00:07:54,910
A third can block Ownerless
275
00:07:54,910 --> 00:07:56,329
agents that nobody has used in
276
00:07:56,329 --> 00:07:56,870
months.
277
00:07:56,870 --> 00:07:58,310
Underneath all of that sits the
278
00:07:58,310 --> 00:07:59,750
security template, which is the
279
00:07:59,750 --> 00:08:01,149
most useful idea for a beginner
280
00:08:01,149 --> 00:08:02,069
to understand.
281
00:08:02,069 --> 00:08:05,029
It's a ready made bundle of
protections drawn from intra for
282
00:08:05,029 --> 00:08:08,069
identity, purview for data
Defender for threats, and
283
00:08:08,069 --> 00:08:09,189
SharePoint for sharing.
284
00:08:09,189 --> 00:08:11,949
The whole bundle can be applied
to an agent in a single step.
285
00:08:11,949 --> 00:08:14,790
Picture a finance team building
an agent that reads contracts,
286
00:08:14,790 --> 00:08:18,310
and instead of a dozen separate
security decisions, it applies
287
00:08:18,310 --> 00:08:20,310
one template and moves on.
288
00:08:20,310 --> 00:08:23,870
Reading the dashboard usage risk
and the agent map.
289
00:08:23,870 --> 00:08:26,649
Once the agents are approved,
the job shifts from doing to
290
00:08:26,649 --> 00:08:29,430
watching, and the dashboard is
built for exactly that.
291
00:08:29,430 --> 00:08:31,009
The overview page shows a thirty
292
00:08:31,009 --> 00:08:32,029
day snapshot of the whole
293
00:08:32,029 --> 00:08:32,669
estate.
294
00:08:32,669 --> 00:08:34,149
It counts the agents, the people
295
00:08:34,149 --> 00:08:35,429
using them, the hours of work
296
00:08:35,429 --> 00:08:36,629
they did, and the outside
297
00:08:36,629 --> 00:08:37,149
platforms.
298
00:08:37,149 --> 00:08:39,149
The registry connects to those
numbers.
299
00:08:39,149 --> 00:08:40,309
Answer a question every leader
300
00:08:40,309 --> 00:08:41,590
eventually asks, which is
301
00:08:41,590 --> 00:08:42,750
whether any of this is worth the
302
00:08:42,750 --> 00:08:43,269
money.
303
00:08:43,269 --> 00:08:45,750
The dashboard also lines up the
jobs that need a human.
304
00:08:45,750 --> 00:08:48,230
There's a card for requests
waiting on approval, one for
305
00:08:48,230 --> 00:08:50,909
agents without owners, one for
agents with errors, and one for
306
00:08:50,909 --> 00:08:51,870
agents at risk.
307
00:08:51,870 --> 00:08:53,389
That last card is the one to
notice.
308
00:08:53,389 --> 00:08:56,009
Security tools like purview,
entra, and Defender each watch
309
00:08:56,009 --> 00:08:58,950
for different trouble, and the
registry pulls their warnings
310
00:08:58,950 --> 00:08:59,669
into one column.
311
00:08:59,669 --> 00:09:00,830
You can click into.
312
00:09:00,830 --> 00:09:03,629
From there, an admin sees the
signals grouped by how serious
313
00:09:03,629 --> 00:09:05,950
they are, along with how many
times each one fired.
314
00:09:05,950 --> 00:09:08,590
When the list gets long, a list
stops helping, and that's where
315
00:09:08,590 --> 00:09:09,870
the agent map earns its place.
316
00:09:09,870 --> 00:09:11,090
Instead of rows of names, it
317
00:09:11,090 --> 00:09:13,029
draws agents as icons grouped by
318
00:09:13,029 --> 00:09:14,429
the platform they came from, so
319
00:09:14,429 --> 00:09:15,629
you can see the pattern at a
320
00:09:15,629 --> 00:09:15,909
glance.
321
00:09:15,909 --> 00:09:18,669
You can filter the map by
status, publisher, platform,
322
00:09:18,669 --> 00:09:19,789
channel, or usage.
323
00:09:19,789 --> 00:09:21,029
Drilling into a single agent
324
00:09:21,029 --> 00:09:22,230
shows its owner and how it's
325
00:09:22,230 --> 00:09:22,909
behaving.
326
00:09:22,909 --> 00:09:26,070
A newer preview view goes a step
further and shows one agent, the
327
00:09:26,070 --> 00:09:28,990
people who use it and the tools
it calls, and the tool lights up
328
00:09:28,990 --> 00:09:30,669
when its error rate climbs.
329
00:09:30,669 --> 00:09:33,149
The honest part is that none of
this is instant or complete.
330
00:09:33,149 --> 00:09:34,269
The risk numbers in the admin
331
00:09:34,269 --> 00:09:35,350
center can lag behind the
332
00:09:35,350 --> 00:09:36,710
security portals by up to an
333
00:09:36,710 --> 00:09:37,149
hour.
334
00:09:37,149 --> 00:09:40,190
The overview card shows only the
top five platforms, so the full
335
00:09:40,190 --> 00:09:41,830
picture lives in the registry.
336
00:09:41,830 --> 00:09:44,870
Draft agents are only visible
from Copilot Studio for now, and
337
00:09:44,870 --> 00:09:47,629
the map itself needs the higher
tier license, which means the
338
00:09:47,629 --> 00:09:50,149
view you get depends on what
your company bought.
339
00:09:50,149 --> 00:09:52,070
Common mistakes and honest
limits.
340
00:09:52,070 --> 00:09:55,070
Nobody gets this right on the
first try, and the mistakes tend
341
00:09:55,070 --> 00:09:56,110
to follow a pattern.
342
00:09:56,110 --> 00:09:57,509
The most common one is blocking
343
00:09:57,509 --> 00:09:58,470
agents before you have a
344
00:09:58,470 --> 00:09:59,990
registry, which is like firing
345
00:09:59,990 --> 00:10:01,230
people before you know who works
346
00:10:01,230 --> 00:10:01,629
for you.
347
00:10:01,629 --> 00:10:04,070
Admins block the loudest agent
they've heard about and never
348
00:10:04,070 --> 00:10:06,309
find the quiet ones doing damage
in the background.
349
00:10:06,309 --> 00:10:07,990
The fix is unglamorous and
effective.
350
00:10:07,990 --> 00:10:09,190
Turn the registry on.
351
00:10:09,190 --> 00:10:11,789
Let it fill up and only then
start making decisions.
352
00:10:11,789 --> 00:10:14,389
The next trap is ignoring
ownerless agents until the
353
00:10:14,389 --> 00:10:15,669
number is frightening.
354
00:10:15,669 --> 00:10:18,250
Every departure adds to that
count, and an agent left behind
355
00:10:18,250 --> 00:10:20,230
keeps its access to whatever
data it was given.
356
00:10:20,230 --> 00:10:22,350
That is a risk that grows in the
dark.
357
00:10:22,350 --> 00:10:25,350
Another common slip is assuming
delete means gone.
358
00:10:25,350 --> 00:10:28,029
Delete actually opens a thirty
day window where the agent stays
359
00:10:28,029 --> 00:10:30,509
recoverable and stays recorded
in the audit log.
360
00:10:30,509 --> 00:10:32,009
There's also the duplicate row
361
00:10:32,009 --> 00:10:33,230
where an admin deletes one
362
00:10:33,230 --> 00:10:34,350
entry, thinking it's a glitch
363
00:10:34,350 --> 00:10:35,590
and is surprised the agent never
364
00:10:35,590 --> 00:10:35,909
left.
365
00:10:35,909 --> 00:10:39,350
One more is reading early usage
numbers as the whole truth data
366
00:10:39,350 --> 00:10:41,950
for outside agents only starts
counting the day the license
367
00:10:41,950 --> 00:10:44,669
switches on, so the first weeks
always look thin.
368
00:10:44,669 --> 00:10:46,870
Then there are the limits
Microsoft states plainly, and
369
00:10:46,870 --> 00:10:47,669
they're worth repeating.
370
00:10:47,669 --> 00:10:50,309
Without the polish, not every
agent appears automatically.
371
00:10:50,309 --> 00:10:52,990
Anything built outside
Microsoft's channels without a
372
00:10:52,990 --> 00:10:56,570
Microsoft agent identity needs
extra steps or a registry sink
373
00:10:56,570 --> 00:10:57,509
to show up.
374
00:10:57,509 --> 00:10:59,090
Admin actions can quietly fail
375
00:10:59,090 --> 00:11:00,230
on agents behind a power
376
00:11:00,230 --> 00:11:01,870
platform firewall in active
377
00:11:01,870 --> 00:11:03,110
enforcement mode because the
378
00:11:03,110 --> 00:11:04,409
request arrives from the wrong
379
00:11:04,409 --> 00:11:05,149
address.
380
00:11:05,149 --> 00:11:06,870
An AI administrator can monitor
381
00:11:06,870 --> 00:11:08,230
plenty, but can't change every
382
00:11:08,230 --> 00:11:09,610
identity setting, since some of
383
00:11:09,610 --> 00:11:10,710
that needs a more privileged
384
00:11:10,710 --> 00:11:11,149
role.
385
00:11:11,149 --> 00:11:12,309
Draft agents from several
386
00:11:12,309 --> 00:11:13,909
platforms still aren't visible,
387
00:11:13,909 --> 00:11:15,269
and several of the best views,
388
00:11:15,269 --> 00:11:16,509
including the risk column and
389
00:11:16,509 --> 00:11:18,129
the map, need the higher tier
390
00:11:18,129 --> 00:11:18,830
license.
391
00:11:18,830 --> 00:11:21,190
None of that makes the tool
weak, and it makes it honest.
392
00:11:21,190 --> 00:11:22,389
Honesty is what you want from
393
00:11:22,389 --> 00:11:23,509
something whose job is keeping
394
00:11:23,509 --> 00:11:24,750
an eye on software that can act
395
00:11:24,750 --> 00:11:25,389
without you.
396
00:11:25,389 --> 00:11:26,509
The point of listing the limits
397
00:11:26,509 --> 00:11:27,710
is so you don't expect a magic
398
00:11:27,710 --> 00:11:28,389
switch.
399
00:11:28,389 --> 00:11:31,269
What you get is a control room
and not a babysitter, and a
400
00:11:31,269 --> 00:11:34,149
control room only helps if
someone is actually in it.
401
00:11:34,149 --> 00:11:36,470
How it fits with Microsoft three
hundred sixty five and Azure.
402
00:11:36,470 --> 00:11:37,549
The admin center is the front
403
00:11:37,549 --> 00:11:38,529
door, but the muscle behind
404
00:11:38,529 --> 00:11:39,769
agent three hundred sixty five
405
00:11:39,769 --> 00:11:40,950
comes from tools that people in
406
00:11:40,950 --> 00:11:42,029
the Microsoft world already
407
00:11:42,029 --> 00:11:42,509
know.
408
00:11:42,509 --> 00:11:43,769
Microsoft Entra gives every
409
00:11:43,769 --> 00:11:45,190
agent an identity, so an agent
410
00:11:45,190 --> 00:11:46,389
has permissions the same way an
411
00:11:46,389 --> 00:11:47,269
employee does.
412
00:11:47,269 --> 00:11:48,629
Microsoft Defender watches for
413
00:11:48,629 --> 00:11:49,789
threats and attacks, and
414
00:11:49,789 --> 00:11:51,190
Microsoft Purview looks after
415
00:11:51,190 --> 00:11:52,750
the data an agent touches so it
416
00:11:52,750 --> 00:11:53,830
doesn't overshare.
417
00:11:53,830 --> 00:11:54,429
Microsoft.
418
00:11:54,429 --> 00:11:56,950
Intune handles the devices some
agents run on.
419
00:11:56,950 --> 00:11:58,269
None of these are new products,
420
00:11:58,269 --> 00:11:59,309
and that's the whole design,
421
00:11:59,309 --> 00:12:00,649
because agent three sixty five
422
00:12:00,649 --> 00:12:01,990
simply extends controls you
423
00:12:01,990 --> 00:12:03,350
already trust to a new kind of
424
00:12:03,350 --> 00:12:04,590
worker.
425
00:12:04,590 --> 00:12:07,350
Azure enters the picture in a
specific and satisfying way.
426
00:12:07,350 --> 00:12:10,190
Agents built with Microsoft
Foundry Run on Azure, and an
427
00:12:10,190 --> 00:12:13,029
admin can start or stop one
right from the admin center,
428
00:12:13,029 --> 00:12:13,909
starting at provisions.
429
00:12:13,909 --> 00:12:15,190
The underlying compute and
430
00:12:15,190 --> 00:12:16,309
stopping it releases that
431
00:12:16,309 --> 00:12:16,710
compute.
432
00:12:16,710 --> 00:12:19,269
It's a small detail with a real
consequence, because the control
433
00:12:19,269 --> 00:12:21,029
room reaches all the way down
into the cloud.
434
00:12:21,029 --> 00:12:22,629
Resources and agent depends on.
435
00:12:22,629 --> 00:12:24,669
There's also a bridge to the
wider world.
436
00:12:24,669 --> 00:12:26,429
A registry sync feature still in
437
00:12:26,429 --> 00:12:28,090
preview can connect agent three
438
00:12:28,090 --> 00:12:29,429
sixty five to outside platforms
439
00:12:29,429 --> 00:12:30,789
like Amazon Bedrock and Google
440
00:12:30,789 --> 00:12:31,429
Cloud.
441
00:12:31,429 --> 00:12:33,909
Agents built there then show up
in the same list.
442
00:12:33,909 --> 00:12:35,389
Microsoft has lined up partner
443
00:12:35,389 --> 00:12:36,470
agents from companies like
444
00:12:36,470 --> 00:12:38,470
spark, Zendesk, and N810 that
445
00:12:38,470 --> 00:12:39,710
plug straight into the control
446
00:12:39,710 --> 00:12:39,990
room.
447
00:12:39,990 --> 00:12:42,750
That matters because most
companies won't run everything
448
00:12:42,750 --> 00:12:44,470
inside one vendor's walls.
449
00:12:44,470 --> 00:12:47,149
Then there's the money, because
that always anchors the story.
450
00:12:47,149 --> 00:12:50,070
Agent three sixty five costs
fifteen dollars per user per
451
00:12:50,070 --> 00:12:52,830
month on its own, or it comes
included in Microsoft three
452
00:12:52,830 --> 00:12:57,029
hundred sixty five E7 and it
works best alongside E5.
453
00:12:57,029 --> 00:12:58,389
A single licensed user is enough
454
00:12:58,389 --> 00:12:59,470
to switch it on for the whole
455
00:12:59,470 --> 00:13:00,149
tenant.
456
00:13:00,149 --> 00:13:01,350
So why should someone who never
457
00:13:01,350 --> 00:13:02,710
opens the admin center care at
458
00:13:02,710 --> 00:13:03,070
all?
459
00:13:03,070 --> 00:13:04,429
The answer is that this page
460
00:13:04,429 --> 00:13:05,909
decides which agents you're
461
00:13:05,909 --> 00:13:07,590
allowed to use at work, and that
462
00:13:07,590 --> 00:13:08,830
decision quietly shapes your
463
00:13:08,830 --> 00:13:09,149
day.
464
00:13:09,149 --> 00:13:11,909
It shapes everything from the
replies you draft to the tickets
465
00:13:11,909 --> 00:13:13,470
you never have to read.
466
00:13:13,470 --> 00:13:15,149
A quick recap and a question for
you.
467
00:13:15,149 --> 00:13:16,629
So here's where we've landed.
468
00:13:16,629 --> 00:13:18,149
AI agents do real work now and
469
00:13:18,149 --> 00:13:19,710
they multiply faster than anyone
470
00:13:19,710 --> 00:13:20,549
can track.
471
00:13:20,549 --> 00:13:22,070
Agent three sixty five gives a
472
00:13:22,070 --> 00:13:23,350
company one place to keep those
473
00:13:23,350 --> 00:13:24,870
agents visible, approved and
474
00:13:24,870 --> 00:13:25,509
accountable.
475
00:13:25,509 --> 00:13:26,710
It won't build a single agent
476
00:13:26,710 --> 00:13:27,789
for you, and it won't close
477
00:13:27,789 --> 00:13:28,629
every gap.
478
00:13:28,629 --> 00:13:29,990
What it does is turn a scattered
479
00:13:29,990 --> 00:13:31,750
mess into one list you can
480
00:13:31,750 --> 00:13:32,350
actually manage.
481
00:13:32,350 --> 00:13:33,990
Which brings me to my question
for you.
482
00:13:33,990 --> 00:13:37,029
If you had to hand one task to
an agent tomorrow, what would
483
00:13:37,029 --> 00:13:39,470
you trust it to do without
checking on it first?
484
00:13:39,470 --> 00:13:42,210
I would really like to hear your
answer, because that choice says
485
00:13:42,210 --> 00:13:44,710
a lot about how comfortable
we've become with software that
486
00:13:44,710 --> 00:13:46,429
works while we look away.
487
00:13:46,429 --> 00:13:47,750
If this made the topic feel less
488
00:13:47,750 --> 00:13:50,250
intimidating, subscribe to M365
489
00:13:50,250 --> 00:13:51,789
FM to master the tools and the
490
00:13:51,789 --> 00:13:53,669
mindset shaping the future of
491
00:13:53,669 --> 00:13:54,269
work.
