1
00:00:00,040 --> 00:00:03,520
Welcome to the M365 FM podcast
where we explore the people,

2
00:00:03,520 --> 00:00:06,280
ideas and technologies shaping
the future of work.

3
00:00:06,280 --> 00:00:06,879
Microsoft three.

4
00:00:06,879 --> 00:00:07,679
Sixty five lighthouse.

5
00:00:07,679 --> 00:00:08,519
The free tool.

6
00:00:08,519 --> 00:00:10,439
Almost nobody talks about
Microsoft three.

7
00:00:10,439 --> 00:00:13,099
Sixty five lighthouse is free,
and almost nobody outside the IT

8
00:00:13,099 --> 00:00:14,439
world talks about it.

9
00:00:14,439 --> 00:00:17,800
It's one screen that lets a
single IT provider look after

10
00:00:17,800 --> 00:00:20,320
Microsoft three hundred sixty
five for dozens of small

11
00:00:20,320 --> 00:00:21,920
businesses at the same time.

12
00:00:21,920 --> 00:00:23,920
That sounds like a small
convenience until you see how

13
00:00:23,920 --> 00:00:26,719
many companies depend on those
providers to stay secure.

14
00:00:26,719 --> 00:00:30,399
Welcome to the M365 FM podcast,
where we explore the people,

15
00:00:30,399 --> 00:00:33,119
ideas, and technologies shaping
the future of work.

16
00:00:33,119 --> 00:00:36,479
By the end of this, you'll know
what lighthouse really does, who

17
00:00:36,479 --> 00:00:39,600
it's built for, and the hard
limits it runs into.

18
00:00:39,600 --> 00:00:40,600
What Microsoft three.

19
00:00:40,600 --> 00:00:42,439
Sixty five lighthouse actually
is.

20
00:00:42,439 --> 00:00:43,960
Start with the word tenant

21
00:00:43,960 --> 00:00:45,240
because everything else hangs on

22
00:00:45,240 --> 00:00:45,520
it.

23
00:00:45,520 --> 00:00:46,840
A tenant is one company's own

24
00:00:46,840 --> 00:00:48,159
private slice of Microsoft three

25
00:00:48,159 --> 00:00:49,359
hundred sixty five with its own

26
00:00:49,359 --> 00:00:51,439
users, mailboxes, files, and

27
00:00:51,439 --> 00:00:52,119
settings.

28
00:00:52,119 --> 00:00:54,679
When you sign in to your work,
email your insider tenant.

29
00:00:54,679 --> 00:00:56,840
Even if nobody ever used that
word around you.

30
00:00:56,840 --> 00:00:58,439
For most of us, Microsoft three

31
00:00:58,439 --> 00:01:00,079
hundred sixty five means exactly

32
00:01:00,079 --> 00:01:01,700
one tenant, the one we sign into

33
00:01:01,700 --> 00:01:02,770
every morning.

34
00:01:02,770 --> 00:01:04,849
An IT provider lives inside
many.

35
00:01:04,849 --> 00:01:07,090
Because dozens of small
businesses hire them to run

36
00:01:07,090 --> 00:01:09,129
Microsoft three hundred sixty
five on their behalf.

37
00:01:09,129 --> 00:01:10,170
Microsoft three hundred sixty

38
00:01:10,170 --> 00:01:11,209
five lighthouse is the screen

39
00:01:11,209 --> 00:01:12,609
that shows all of those tenants

40
00:01:12,609 --> 00:01:13,409
together.

41
00:01:13,409 --> 00:01:14,810
Instead of opening fifty admin

42
00:01:14,810 --> 00:01:16,409
centers in fifty browser tabs,

43
00:01:16,409 --> 00:01:18,170
the provider opens one portal

44
00:01:18,170 --> 00:01:19,609
and sees every customer side by

45
00:01:19,609 --> 00:01:19,849
side.

46
00:01:19,849 --> 00:01:22,730
That's the whole idea, and it's
worth saying plainly because the

47
00:01:22,730 --> 00:01:25,090
name makes it sound more
mysterious than it is.

48
00:01:25,090 --> 00:01:27,530
Lighthouse isn't a place for
deep configuration work.

49
00:01:27,530 --> 00:01:29,930
It works more like a control
room than a workshop, because

50
00:01:29,930 --> 00:01:32,250
the job here is spotting
problems and pushing standard

51
00:01:32,250 --> 00:01:35,209
fixes, not rebuilding one
company set up from scratch.

52
00:01:35,209 --> 00:01:37,890
The portal gathers the signals a
provider actually needs.

53
00:01:37,890 --> 00:01:40,969
It shows tenant health, risky
sign ins, device compliance

54
00:01:40,969 --> 00:01:44,650
threats, service incidents, and
alerts all pulled into one view.

55
00:01:44,650 --> 00:01:45,969
Microsoft describes this as

56
00:01:45,969 --> 00:01:47,489
proactive account management,

57
00:01:47,489 --> 00:01:49,090
simplified onboarding, device

58
00:01:49,090 --> 00:01:50,609
protection, and multi-tenant

59
00:01:50,609 --> 00:01:52,329
visibility, which is a mouthful,

60
00:01:52,329 --> 00:01:53,450
but the plain version is that

61
00:01:53,450 --> 00:01:55,170
you stop checking every customer

62
00:01:55,170 --> 00:01:56,689
by hand and it doesn't cost

63
00:01:56,689 --> 00:01:57,609
anything extra.

64
00:01:57,609 --> 00:01:59,129
Microsoft states plainly that

65
00:01:59,129 --> 00:02:00,709
there are no additional costs to

66
00:02:00,709 --> 00:02:01,849
use lighthouse for managing

67
00:02:01,849 --> 00:02:02,969
Microsoft three hundred sixty

68
00:02:02,969 --> 00:02:04,069
five services and connected

69
00:02:04,069 --> 00:02:06,090
devices, so this isn't a premium

70
00:02:06,090 --> 00:02:07,269
add on waiting at the end of a

71
00:02:07,269 --> 00:02:08,110
sales call.

72
00:02:08,110 --> 00:02:11,430
What makes it matter in practice
is the word across.

73
00:02:11,430 --> 00:02:12,750
One provider might look after a

74
00:02:12,750 --> 00:02:14,150
dentist, a law firm, a small

75
00:02:14,150 --> 00:02:15,449
manufacturer, and a chain of

76
00:02:15,449 --> 00:02:16,789
coffee shops, and each one has a

77
00:02:16,789 --> 00:02:17,830
separate tenant with its own

78
00:02:17,830 --> 00:02:18,629
problems.

79
00:02:18,629 --> 00:02:21,270
Lighthouse turns that scattered
pile into something closer to a

80
00:02:21,270 --> 00:02:23,909
fleet, where the provider sees
the whole group at once and

81
00:02:23,909 --> 00:02:26,430
deals with the same issue
everywhere it appears.

82
00:02:26,430 --> 00:02:28,789
There's also a newer sales
facing side to the portal.

83
00:02:28,789 --> 00:02:31,870
Microsoft has added areas that
use machine learning to point a

84
00:02:31,870 --> 00:02:34,150
partner to what customers who
might benefit from more

85
00:02:34,150 --> 00:02:37,509
services, including suggestions
around copilot adoption.

86
00:02:37,509 --> 00:02:38,710
That side is aimed at account

87
00:02:38,710 --> 00:02:39,550
managers rather than

88
00:02:39,550 --> 00:02:40,990
technicians, and that's part of

89
00:02:40,990 --> 00:02:42,150
why people call lighthouse a

90
00:02:42,150 --> 00:02:43,229
business tool as much as a

91
00:02:43,229 --> 00:02:44,189
security tool.

92
00:02:44,189 --> 00:02:46,509
It also brings up the question
of who this is actually built

93
00:02:46,509 --> 00:02:49,069
for, which is where we go next.

94
00:02:49,069 --> 00:02:49,909
Who Microsoft three.

95
00:02:49,909 --> 00:02:51,990
Sixty five lighthouse is really
built for.

96
00:02:51,990 --> 00:02:53,069
Here's the part that surprises

97
00:02:53,069 --> 00:02:54,069
people, and it's worth being

98
00:02:54,069 --> 00:02:54,629
blunt about.

99
00:02:54,629 --> 00:02:57,750
Lighthouse is not built for a
single company's own IT team.

100
00:02:57,750 --> 00:02:58,750
It's built for partners in

101
00:02:58,750 --> 00:03:00,030
Microsoft's Cloud Solution

102
00:03:00,030 --> 00:03:01,710
Provider program, which includes

103
00:03:01,710 --> 00:03:02,949
direct build partners and

104
00:03:02,949 --> 00:03:04,439
indirect resellers.

105
00:03:04,439 --> 00:03:05,879
In plain language, those are the

106
00:03:05,879 --> 00:03:07,280
companies that sell and manage

107
00:03:07,280 --> 00:03:08,460
Microsoft three hundred sixty

108
00:03:08,460 --> 00:03:08,800
five.

109
00:03:08,800 --> 00:03:10,360
For other businesses, if you've

110
00:03:10,360 --> 00:03:11,439
ever worked somewhere small

111
00:03:11,439 --> 00:03:12,819
enough that the boss says to

112
00:03:12,819 --> 00:03:14,560
call the IT guy, that I.T. guy

113
00:03:14,560 --> 00:03:15,560
is very often one of these

114
00:03:15,560 --> 00:03:16,039
partners.

115
00:03:16,039 --> 00:03:17,159
Lighthouse is the tool working

116
00:03:17,159 --> 00:03:18,479
behind the curtain for that kind

117
00:03:18,479 --> 00:03:19,599
of job.

118
00:03:19,599 --> 00:03:22,479
One detail clears up a common
worry the customer businesses

119
00:03:22,479 --> 00:03:25,080
don't need to join the Cloud
Solution Provider program.

120
00:03:25,080 --> 00:03:26,360
Only the partner does.

121
00:03:26,360 --> 00:03:29,039
A dentist office that hires an
IT provider doesn't have to sign

122
00:03:29,039 --> 00:03:32,000
up for anything special, because
the whole relationship lives on

123
00:03:32,000 --> 00:03:33,120
the provider's side.

124
00:03:33,120 --> 00:03:34,560
It helps to picture the scale.

125
00:03:34,560 --> 00:03:36,319
A small managed service provider

126
00:03:36,319 --> 00:03:37,419
might look after twenty

127
00:03:37,419 --> 00:03:38,919
customers, while a larger one

128
00:03:38,919 --> 00:03:40,560
could handle several hundred at

129
00:03:40,560 --> 00:03:40,919
twenty.

130
00:03:40,919 --> 00:03:42,039
You can almost get away with

131
00:03:42,039 --> 00:03:43,520
memory and a spreadsheet at

132
00:03:43,520 --> 00:03:45,039
several hundred you can't, and

133
00:03:45,039 --> 00:03:46,240
the tools built for a single

134
00:03:46,240 --> 00:03:47,520
tenant simply don't stretch that

135
00:03:47,520 --> 00:03:47,879
far.

136
00:03:47,879 --> 00:03:50,159
If that isn't you, then
lighthouse isn't the tool for

137
00:03:50,159 --> 00:03:51,680
your job, and that's fine.

138
00:03:51,680 --> 00:03:54,560
The standard admin center gives
you far more depth for a single

139
00:03:54,560 --> 00:03:57,000
tenant, and it's where you'd
spend your day anyway.

140
00:03:57,000 --> 00:03:58,280
Large organizations and big

141
00:03:58,280 --> 00:03:59,539
security teams have their own

142
00:03:59,539 --> 00:04:01,240
option to the multi-tenant tools

143
00:04:01,240 --> 00:04:01,520
inside.

144
00:04:01,520 --> 00:04:05,000
Microsoft Defender XDR are built
for enterprise scale security

145
00:04:05,000 --> 00:04:08,620
work where teams hunt threats
across many tenants at once.

146
00:04:08,620 --> 00:04:11,180
Lighthouse and those tools aim
at different people, and

147
00:04:11,180 --> 00:04:14,219
Microsoft's own comparison table
makes that split clear.

148
00:04:14,219 --> 00:04:15,340
This matters even if you never

149
00:04:15,340 --> 00:04:16,620
touch lighthouse, because it

150
00:04:16,620 --> 00:04:17,980
explains why the tool looks the

151
00:04:17,980 --> 00:04:19,459
way it does every design choice

152
00:04:19,459 --> 00:04:19,899
inside.

153
00:04:19,899 --> 00:04:22,939
It comes from one problem, which
is running the same job across

154
00:04:22,939 --> 00:04:25,740
one hundred small customers
without losing your mind.

155
00:04:25,740 --> 00:04:28,699
What a customer tenant needs
before lighthouse can see it,

156
00:04:28,699 --> 00:04:31,220
lighthouse can't see a customer
tenant on its own.

157
00:04:31,220 --> 00:04:33,339
The partner has to be given
access first, and the way that

158
00:04:33,339 --> 00:04:35,379
access works has changed a lot
over the years.

159
00:04:35,379 --> 00:04:36,540
The modern approach is called

160
00:04:36,540 --> 00:04:37,779
granular Delegated

161
00:04:37,779 --> 00:04:39,319
Administrative Privileges, or

162
00:04:39,319 --> 00:04:39,980
DAP.

163
00:04:39,980 --> 00:04:42,819
The name is heavy, but the idea
is simple the customer hands the

164
00:04:42,819 --> 00:04:45,579
partner a limited set of admin
permissions instead of the

165
00:04:45,579 --> 00:04:46,939
master keys to everything.

166
00:04:46,939 --> 00:04:48,339
Those permissions cover specific

167
00:04:48,339 --> 00:04:49,920
roles, and they carry an expiry

168
00:04:49,920 --> 00:04:51,660
date so access doesn't sit open

169
00:04:51,660 --> 00:04:52,180
forever.

170
00:04:52,180 --> 00:04:54,339
There's an older model called
Delegated Administrative

171
00:04:54,339 --> 00:04:57,500
Privileges, or DAP, which was
broader and blunter.

172
00:04:57,500 --> 00:05:01,060
If a tenant has both DAP wins
for technicians who sit in DAP

173
00:05:01,060 --> 00:05:04,019
enabled security groups, so the
tighter model takes priority.

174
00:05:04,019 --> 00:05:05,819
Once access is sorted, a tenant

175
00:05:05,819 --> 00:05:06,949
still has to clear three more

176
00:05:06,949 --> 00:05:07,629
bars.

177
00:05:07,629 --> 00:05:10,189
It needs at least one qualifying
subscription, such as Microsoft

178
00:05:10,189 --> 00:05:12,009
three hundred sixty five, office
three hundred sixty five,

179
00:05:12,009 --> 00:05:14,110
Exchange Online, windows three
hundred sixty five business, or

180
00:05:14,110 --> 00:05:15,949
Microsoft Defender for business.

181
00:05:15,949 --> 00:05:17,129
It needs no more than two

182
00:05:17,129 --> 00:05:18,550
thousand five hundred licensed

183
00:05:18,550 --> 00:05:19,149
users.

184
00:05:19,149 --> 00:05:21,430
It also has to sit in the same
region as the partner, which

185
00:05:21,430 --> 00:05:24,670
means the Americas, the European
Union or Asia, plus Australia.

186
00:05:24,670 --> 00:05:25,949
Those rules aren't random.

187
00:05:25,949 --> 00:05:27,230
The seat cap and the region rule

188
00:05:27,230 --> 00:05:28,470
keep the tool pointed at small

189
00:05:28,470 --> 00:05:30,110
and midsize customers, which is

190
00:05:30,110 --> 00:05:31,350
exactly who these partners

191
00:05:31,350 --> 00:05:31,949
serve.

192
00:05:31,949 --> 00:05:34,829
A giant enterprise tenant with
fifty thousand seats isn't the

193
00:05:34,829 --> 00:05:37,870
target here, and Microsoft sends
that audience somewhere else,

194
00:05:37,870 --> 00:05:40,269
miss any of the bars and the
tenant doesn't vanish.

195
00:05:40,269 --> 00:05:42,790
It drops into a limited
experience instead, where the

196
00:05:42,790 --> 00:05:46,310
partner can still handle setup,
search for users, view user

197
00:05:46,310 --> 00:05:48,670
details, tag the tenant, and
check service health.

198
00:05:48,670 --> 00:05:50,089
Everything richer like device

199
00:05:50,089 --> 00:05:51,589
views and risk reports stays

200
00:05:51,589 --> 00:05:52,509
locked until the tenant

201
00:05:52,509 --> 00:05:53,269
qualifies.

202
00:05:53,269 --> 00:05:54,709
Timing catches people out as
well.

203
00:05:54,709 --> 00:05:57,470
When a tenant does qualify, the
data won't appear instantly

204
00:05:57,470 --> 00:06:00,189
because Microsoft says a
customer tenant's data can take

205
00:06:00,189 --> 00:06:01,949
up to forty eight hours to load.

206
00:06:01,949 --> 00:06:03,790
A new partner shouldn't panic on
day one.

207
00:06:03,790 --> 00:06:05,709
There's one more piece that's
easy to forget.

208
00:06:05,709 --> 00:06:07,069
Access alone isn't enough for

209
00:06:07,069 --> 00:06:08,310
some features, because device

210
00:06:08,310 --> 00:06:09,730
views depend on devices being

211
00:06:09,730 --> 00:06:11,209
enrolled in Intune, and risk

212
00:06:11,209 --> 00:06:12,329
views depend on the right

213
00:06:12,329 --> 00:06:13,290
identity license.

214
00:06:13,290 --> 00:06:15,889
That's where many beginners get
confused, and it becomes one of

215
00:06:15,889 --> 00:06:18,889
the real limits later, so keep
it in your back pocket.

216
00:06:18,889 --> 00:06:21,610
How baselines keep every
customer on the same standard.

217
00:06:21,610 --> 00:06:23,050
If lighthouse had only one idea

218
00:06:23,050 --> 00:06:24,290
worth learning, it would be the

219
00:06:24,290 --> 00:06:24,930
baseline.

220
00:06:24,930 --> 00:06:26,610
A baseline is a standard set of

221
00:06:26,610 --> 00:06:28,410
security and compliance settings

222
00:06:28,410 --> 00:06:29,790
that a partner pushes out to

223
00:06:29,790 --> 00:06:31,490
every customer at once, so each

224
00:06:31,490 --> 00:06:32,930
tenant starts from the same safe

225
00:06:32,930 --> 00:06:33,449
place.

226
00:06:33,449 --> 00:06:36,250
Microsoft ships a default
baseline aimed at small and

227
00:06:36,250 --> 00:06:40,089
midsize businesses, and it sorts
the tasks into six areas

228
00:06:40,089 --> 00:06:42,649
identity protection keeps
account safe email and apps

229
00:06:42,649 --> 00:06:45,490
protection locks down mail and
the productivity apps endpoint.

230
00:06:45,490 --> 00:06:46,850
Enrollment gets devices into

231
00:06:46,850 --> 00:06:48,050
management, and endpoint

232
00:06:48,050 --> 00:06:49,389
protection adds the security

233
00:06:49,389 --> 00:06:49,769
standards.

234
00:06:49,769 --> 00:06:52,649
On top of that, data protection
stops sensitive information from

235
00:06:52,649 --> 00:06:54,290
leaking and end user experience.

236
00:06:54,290 --> 00:06:56,529
Handles training and branding
across customers.

237
00:06:56,529 --> 00:06:59,129
The point of the default
baseline is that it's a starting

238
00:06:59,129 --> 00:07:00,730
point, not a final answer.

239
00:07:00,730 --> 00:07:04,529
Microsoft tunes it for small and
midsize businesses, so it avoids

240
00:07:04,529 --> 00:07:08,009
settings that would overwhelm a
ten person company, and it stays

241
00:07:08,009 --> 00:07:11,500
focused on the protections that
actually matter at that size.

242
00:07:11,500 --> 00:07:15,100
One deployment task inside that
list makes the idea concrete.

243
00:07:15,100 --> 00:07:17,620
A single task requires
multifactor authentication for

244
00:07:17,620 --> 00:07:20,120
administrators, so a stolen
password alone isn't enough to

245
00:07:20,120 --> 00:07:21,899
take over a customer's tenant.

246
00:07:21,899 --> 00:07:23,379
Another task enrolls windows

247
00:07:23,379 --> 00:07:25,180
devices into Intune and applies

248
00:07:25,180 --> 00:07:26,939
a compliance policy, so a device

249
00:07:26,939 --> 00:07:28,139
that drifts out of line gets

250
00:07:28,139 --> 00:07:28,819
flagged.

251
00:07:28,819 --> 00:07:31,420
The partner doesn't hand-build
those settings in every tenant

252
00:07:31,420 --> 00:07:34,139
because the baseline applies
them across the whole group.

253
00:07:34,139 --> 00:07:36,300
Baselines also look at what's
already there.

254
00:07:36,300 --> 00:07:39,019
Lighthouse scans a tenant
compares what it finds against

255
00:07:39,019 --> 00:07:42,500
the recommended setup and marks
each task as compliant, not

256
00:07:42,500 --> 00:07:44,300
compliant, or not licensed.

257
00:07:44,300 --> 00:07:46,459
That last label is useful
because it tells the partner

258
00:07:46,459 --> 00:07:49,139
that a customer simply doesn't
own the license a task needs,

259
00:07:49,139 --> 00:07:52,220
which turns a technical problem
into a business conversation.

260
00:07:52,220 --> 00:07:54,860
One word of caution about the
word compliance here.

261
00:07:54,860 --> 00:07:57,379
It means the tenant matches the
recommended setting, not that

262
00:07:57,379 --> 00:07:58,860
anyone passed a legal audit.

263
00:07:58,860 --> 00:08:00,620
It's a matching check, not a
certificate.

264
00:08:00,620 --> 00:08:02,740
Partners aren't stuck with
Microsoft's version either.

265
00:08:02,740 --> 00:08:05,579
They can clone the default tasks
and build a custom baseline,

266
00:08:05,579 --> 00:08:08,759
which is how a provider makes
every new customer look the same

267
00:08:08,759 --> 00:08:09,819
on day one.

268
00:08:09,819 --> 00:08:12,839
That consistency is the real
payoff because the provider

269
00:08:12,839 --> 00:08:15,639
defines the standard once
instead of remembering how they

270
00:08:15,639 --> 00:08:17,480
set up the last forty tenants.

271
00:08:17,480 --> 00:08:18,959
That consistency also sets up

272
00:08:18,959 --> 00:08:19,920
the honest part of this

273
00:08:19,920 --> 00:08:21,720
conversation, since a tool built

274
00:08:21,720 --> 00:08:23,480
for breadth always runs into a

275
00:08:23,480 --> 00:08:24,560
ceiling somewhere.

276
00:08:24,560 --> 00:08:26,839
A baseline isn't a set and
forget switch either.

277
00:08:26,839 --> 00:08:29,360
Microsoft's own update notes
show that when a baseline task

278
00:08:29,360 --> 00:08:31,879
changes, tenants can flip to
non-compliant until the partner

279
00:08:31,879 --> 00:08:34,120
redeploys and partners regularly
hit permission snags.

280
00:08:34,120 --> 00:08:36,840
When a deployment fails, the
tool does the pushing, but a

281
00:08:36,840 --> 00:08:38,600
person still owns the result.

282
00:08:38,600 --> 00:08:40,960
What a normal week with
lighthouse actually looks like.

283
00:08:40,960 --> 00:08:43,000
Features are abstract until you
see them in motion.

284
00:08:43,000 --> 00:08:45,240
So here's a plain walk through a
normal stretch of work.

285
00:08:45,240 --> 00:08:46,559
It starts with a new customer.

286
00:08:46,559 --> 00:08:48,120
The provider Onboards the
tenant.

287
00:08:48,120 --> 00:08:49,840
The delegated access is in
place.

288
00:08:49,840 --> 00:08:52,759
The default baseline runs and
the tenant appears in the shared

289
00:08:52,759 --> 00:08:54,519
list alongside everyone else.

290
00:08:54,519 --> 00:08:57,080
From that point on, the provider
isn't visiting a new website.

291
00:08:57,080 --> 00:08:59,440
Every time the customer's name
comes up, the customer is just

292
00:08:59,440 --> 00:09:00,840
another row in one place.

293
00:09:00,840 --> 00:09:04,120
The morning routine is where the
value lands fastest.

294
00:09:04,120 --> 00:09:06,679
The provider opens the alerts
page and sees what needs

295
00:09:06,679 --> 00:09:09,720
attention across every customer
at once, instead of clicking

296
00:09:09,720 --> 00:09:11,610
through each tenant to find out.

297
00:09:11,610 --> 00:09:12,970
Alerts usually appear within

298
00:09:12,970 --> 00:09:14,090
minutes of whatever triggered

299
00:09:14,090 --> 00:09:15,730
them, and a dismissed alert

300
00:09:15,730 --> 00:09:16,970
stays quiet for thirty days

301
00:09:16,970 --> 00:09:18,269
unless something new happens on

302
00:09:18,269 --> 00:09:19,210
that account.

303
00:09:19,210 --> 00:09:20,490
From there, the provider works

304
00:09:20,490 --> 00:09:21,769
through the signals, the user's

305
00:09:21,769 --> 00:09:23,450
area surfaces, accounts flagged

306
00:09:23,450 --> 00:09:24,690
for risky behavior, and the

307
00:09:24,690 --> 00:09:26,090
partner can act on several at

308
00:09:26,090 --> 00:09:27,649
once rather than one customer at

309
00:09:27,649 --> 00:09:28,289
a time.

310
00:09:28,289 --> 00:09:30,929
The device compliance view shows
which devices across all tenants

311
00:09:30,929 --> 00:09:33,769
are healthy, which ones have
slipped out of policy, and which

312
00:09:33,769 --> 00:09:34,490
settings get missed.

313
00:09:34,490 --> 00:09:38,049
Most often, small jobs get
easier to like resetting a

314
00:09:38,049 --> 00:09:40,450
password or turning on
multifactor authentication for

315
00:09:40,450 --> 00:09:42,129
many tenants from one screen.

316
00:09:42,129 --> 00:09:45,009
There's a rhythm to it that a
single tenant never gives you.

317
00:09:45,009 --> 00:09:46,169
A problem that appears in one

318
00:09:46,169 --> 00:09:47,450
customer usually appears in

319
00:09:47,450 --> 00:09:48,730
three others, and because

320
00:09:48,730 --> 00:09:50,090
they're all visible in the same

321
00:09:50,090 --> 00:09:51,690
place, the provider catches the

322
00:09:51,690 --> 00:09:52,970
pattern early instead of

323
00:09:52,970 --> 00:09:54,389
discovering it four separate

324
00:09:54,389 --> 00:09:56,009
times.

325
00:09:56,009 --> 00:09:57,570
Service health rounds out the
picture.

326
00:09:57,570 --> 00:09:58,809
Lighthouse rolls out Microsoft

327
00:09:58,809 --> 00:09:59,570
three hundred sixty five

328
00:09:59,570 --> 00:10:00,929
incidents and advisories across

329
00:10:00,929 --> 00:10:02,649
customers so the provider knows

330
00:10:02,649 --> 00:10:03,769
which customers a service

331
00:10:03,769 --> 00:10:05,090
problem touches before the phone

332
00:10:05,090 --> 00:10:05,809
rings.

333
00:10:05,809 --> 00:10:07,330
Reporting closes the loop.

334
00:10:07,330 --> 00:10:08,370
A partner can generate a

335
00:10:08,370 --> 00:10:09,769
customer report that summarizes

336
00:10:09,769 --> 00:10:11,029
the security posture and the

337
00:10:11,029 --> 00:10:12,549
work done in lighthouse, which

338
00:10:12,549 --> 00:10:13,950
is exactly what you'd hand over

339
00:10:13,950 --> 00:10:15,110
in a monthly or quarterly

340
00:10:15,110 --> 00:10:16,070
review.

341
00:10:16,070 --> 00:10:18,870
Newer areas go further, using
machine learning to suggest

342
00:10:18,870 --> 00:10:20,909
where a partner could help a
customer next, and to track

343
00:10:20,909 --> 00:10:23,269
subscription renewals before
they sneak up.

344
00:10:23,269 --> 00:10:24,429
The overall effect is that the

345
00:10:24,429 --> 00:10:25,529
provider spends less time

346
00:10:25,529 --> 00:10:27,230
hunting for work and more time

347
00:10:27,230 --> 00:10:27,909
doing it.

348
00:10:27,909 --> 00:10:30,149
Instead of asking which customer
has a problem this morning, the

349
00:10:30,149 --> 00:10:32,549
portal answers that question
before the coffee is finished.

350
00:10:32,549 --> 00:10:35,269
None of this makes the tool
unlimited, and the ceiling is

351
00:10:35,269 --> 00:10:38,549
worth understanding before you
get too excited.

352
00:10:38,549 --> 00:10:41,190
Common mistakes and the honest
limits of lighthouse.

353
00:10:41,190 --> 00:10:42,490
An honest explanation has to

354
00:10:42,490 --> 00:10:44,029
slow down here, because the same

355
00:10:44,029 --> 00:10:45,110
design that makes lighthouse

356
00:10:45,110 --> 00:10:46,429
useful also creates its

357
00:10:46,429 --> 00:10:47,269
ceilings.

358
00:10:47,269 --> 00:10:49,750
The tool trades depth for
breadth, and that trade shows up

359
00:10:49,750 --> 00:10:51,070
in specific places.

360
00:10:51,070 --> 00:10:52,029
Start with what it isn't.

361
00:10:52,029 --> 00:10:54,830
Lighthouse is not a security
operations center because it

362
00:10:54,830 --> 00:10:57,470
surfaces security signals but
isn't built for the deep.

363
00:10:57,470 --> 00:10:57,669
Our.

364
00:10:57,669 --> 00:11:00,350
By our threat hunting, a full
security team does.

365
00:11:00,350 --> 00:11:03,070
If your job is chasing a clever
attacker through logs, this

366
00:11:03,070 --> 00:11:04,429
isn't the room you do it in.

367
00:11:04,429 --> 00:11:05,629
It also doesn't replace the

368
00:11:05,629 --> 00:11:07,309
tenant admin center for deep

369
00:11:07,309 --> 00:11:08,149
configuration work.

370
00:11:08,149 --> 00:11:09,350
The partner still drops into the

371
00:11:09,350 --> 00:11:10,830
individual customer's own admin

372
00:11:10,830 --> 00:11:11,389
center.

373
00:11:11,389 --> 00:11:12,629
Lighthouse is the view across

374
00:11:12,629 --> 00:11:14,000
the fleet, not the workbench for

375
00:11:14,000 --> 00:11:14,840
one machine.

376
00:11:14,840 --> 00:11:15,879
Then there's the human side.

377
00:11:15,879 --> 00:11:19,120
Lighthouse is a tool for the IT
team that manages the tenants,

378
00:11:19,120 --> 00:11:21,399
and it isn't something you hand
to end users.

379
00:11:21,399 --> 00:11:23,320
It will never show up in their
daily work.

380
00:11:23,320 --> 00:11:24,960
The hard ceiling comes next.

381
00:11:24,960 --> 00:11:28,559
A customer tenant qualifies only
up to two thousand five hundred

382
00:11:28,559 --> 00:11:31,960
seats, and only if it sits in
the same region as the partner.

383
00:11:31,960 --> 00:11:33,399
Cross either line, and that

384
00:11:33,399 --> 00:11:34,799
tenant falls back to the limited

385
00:11:34,799 --> 00:11:36,039
view where most of the useful

386
00:11:36,039 --> 00:11:37,240
parts disappear.

387
00:11:37,240 --> 00:11:38,200
Lighthouse also leans on

388
00:11:38,200 --> 00:11:39,580
Microsoft's other services to do

389
00:11:39,580 --> 00:11:40,360
its job.

390
00:11:40,360 --> 00:11:41,639
Device views need devices

391
00:11:41,639 --> 00:11:42,759
enrolled in Intune with

392
00:11:42,759 --> 00:11:44,419
compliance policies assigned

393
00:11:44,419 --> 00:11:46,000
risk and password views need a

394
00:11:46,000 --> 00:11:47,320
license that includes Microsoft

395
00:11:47,320 --> 00:11:49,279
Entry ID, premium, P1 or higher,

396
00:11:49,279 --> 00:11:50,480
which comes with Microsoft three

397
00:11:50,480 --> 00:11:51,480
hundred sixty five Business

398
00:11:51,480 --> 00:11:52,639
Premium and Microsoft three

399
00:11:52,639 --> 00:11:54,279
hundred sixty five E3 threat

400
00:11:54,279 --> 00:11:55,639
views need devices enrolled and

401
00:11:55,639 --> 00:11:56,840
running Microsoft Defender

402
00:11:56,840 --> 00:11:57,799
Antivirus.

403
00:11:57,799 --> 00:12:00,120
If the customer owns less,
lighthouse can show less.

404
00:12:00,120 --> 00:12:01,559
Timing is the last big one.

405
00:12:01,559 --> 00:12:03,899
Data can take up to forty eight
hours to appear after

406
00:12:03,899 --> 00:12:06,840
onboarding, and anything changed
outside lighthouse isn't picked

407
00:12:06,840 --> 00:12:10,440
up until the next scheduled scan
or a manual detection run.

408
00:12:10,440 --> 00:12:12,840
The picture is accurate, but it
isn't always instant.

409
00:12:12,840 --> 00:12:15,580
There's a quieter side effect
worth knowing, Two lighthouse

410
00:12:15,580 --> 00:12:17,820
pulls its information through
Microsoft Graph APIs.

411
00:12:17,820 --> 00:12:20,139
So if a customer happens to use
Microsoft Sentinel for

412
00:12:20,139 --> 00:12:22,899
monitoring, that API activity
can show up as an incident

413
00:12:22,899 --> 00:12:24,259
unless it gets filtered out.

414
00:12:24,259 --> 00:12:25,419
It isn't a flaw, but it does

415
00:12:25,419 --> 00:12:26,460
surprise you the first time you

416
00:12:26,460 --> 00:12:26,820
see it.

417
00:12:26,820 --> 00:12:27,960
The mistakes beginners make

418
00:12:27,960 --> 00:12:28,980
usually come from the same

419
00:12:28,980 --> 00:12:29,740
route.

420
00:12:29,740 --> 00:12:32,580
One is assuming that free means
effortless when the tool

421
00:12:32,580 --> 00:12:35,139
automates the push, but still
leaves the decisions, the

422
00:12:35,139 --> 00:12:37,340
exclusions, and the follow
through with the partner.

423
00:12:37,340 --> 00:12:38,779
Another is assuming a customer

424
00:12:38,779 --> 00:12:40,080
has to buy something special to

425
00:12:40,080 --> 00:12:41,539
appear in lighthouse when the

426
00:12:41,539 --> 00:12:42,940
gate is the customer's existing

427
00:12:42,940 --> 00:12:44,820
license and size, not an extra

428
00:12:44,820 --> 00:12:45,740
lighthouse fee.

429
00:12:45,740 --> 00:12:48,059
The trade itself is deliberate,
and it isn't a flaw.

430
00:12:48,059 --> 00:12:49,059
If you manage three small

431
00:12:49,059 --> 00:12:50,500
tenants, lighthouse will feel

432
00:12:50,500 --> 00:12:51,860
like overkill if you manage

433
00:12:51,860 --> 00:12:52,379
eighty.

434
00:12:52,379 --> 00:12:53,279
The alternative is eighty

435
00:12:53,279 --> 00:12:54,460
browser tabs and a lot of missed

436
00:12:54,460 --> 00:12:55,860
problems, and the breadth wins

437
00:12:55,860 --> 00:12:57,279
where lighthouse fits next to

438
00:12:57,279 --> 00:12:58,740
Azure Lighthouse and the Admin

439
00:12:58,740 --> 00:12:59,340
Center.

440
00:12:59,340 --> 00:13:00,299
There are two things named

441
00:13:00,299 --> 00:13:01,419
lighthouse in the Microsoft

442
00:13:01,419 --> 00:13:02,659
world, and mixing them up is

443
00:13:02,659 --> 00:13:03,980
easy, so let's separate them

444
00:13:03,980 --> 00:13:04,659
cleanly.

445
00:13:04,659 --> 00:13:07,539
Azure lighthouse is a different
product with a similar name.

446
00:13:07,539 --> 00:13:10,899
It's about managing Azure cloud
resources across customers, and

447
00:13:10,899 --> 00:13:12,139
it lives inside Azure.

448
00:13:12,139 --> 00:13:14,019
Microsoft three hundred sixty
five lighthouse is about

449
00:13:14,019 --> 00:13:16,350
Microsoft three hundred sixty
five tenants, which is the

450
00:13:16,350 --> 00:13:17,549
productivity side of things.

451
00:13:17,549 --> 00:13:20,350
Your mail, your files, your
teams and your devices.

452
00:13:20,350 --> 00:13:23,029
The names rhyme, but the jobs
don't overlap much.

453
00:13:23,029 --> 00:13:24,789
That split mirrors the wider
Microsoft three.

454
00:13:24,789 --> 00:13:27,070
Sixty five and Azure
relationship Microsoft three.

455
00:13:27,070 --> 00:13:28,669
Sixty five is where people work
every day.

456
00:13:28,669 --> 00:13:30,590
Azure is the cloud
infrastructure underneath a lot

457
00:13:30,590 --> 00:13:31,750
of modern software.

458
00:13:31,750 --> 00:13:33,509
Lighthouse lives on the
Microsoft three.

459
00:13:33,509 --> 00:13:35,269
Sixty five side, and it leans on

460
00:13:35,269 --> 00:13:36,590
identity and device services

461
00:13:36,590 --> 00:13:38,110
that sit nearby, which is why

462
00:13:38,110 --> 00:13:39,429
those license requirements keep

463
00:13:39,429 --> 00:13:41,070
mattering against the Tenant

464
00:13:41,070 --> 00:13:41,669
Admin center.

465
00:13:41,669 --> 00:13:43,309
The difference is direction.

466
00:13:43,309 --> 00:13:46,230
The admin center is where you go
deep on one tenant.

467
00:13:46,230 --> 00:13:48,710
Lighthouse is where you look
wide across all of them.

468
00:13:48,710 --> 00:13:51,110
One is a deep dive and the other
is a wide view.

469
00:13:51,110 --> 00:13:52,710
And a provider uses both on the

470
00:13:52,710 --> 00:13:53,870
same day against the

471
00:13:53,870 --> 00:13:55,269
multi-tenant tools in defender

472
00:13:55,269 --> 00:13:55,710
XDR.

473
00:13:55,710 --> 00:13:56,870
The difference is audience.

474
00:13:56,870 --> 00:13:58,149
Those tools are built for large

475
00:13:58,149 --> 00:13:59,429
organizations and security

476
00:13:59,429 --> 00:14:01,309
operations teams with unlimited

477
00:14:01,309 --> 00:14:02,649
seats and a cap of fifty

478
00:14:02,649 --> 00:14:03,350
tenants.

479
00:14:03,350 --> 00:14:05,710
Lighthouse is built for partners
serving small and midsize

480
00:14:05,710 --> 00:14:08,610
customers with unlimited tenants
and a cap of two thousand five

481
00:14:08,610 --> 00:14:09,950
hundred seats per tenant.

482
00:14:09,950 --> 00:14:12,710
It's the same idea of managing
many tenants, but aimed at the

483
00:14:12,710 --> 00:14:13,830
opposite end of the market.

484
00:14:13,830 --> 00:14:15,070
One more practical note ties

485
00:14:15,070 --> 00:14:16,820
this together because lighthouse

486
00:14:16,820 --> 00:14:18,570
leans on Intune and entry ID, a

487
00:14:18,570 --> 00:14:19,889
provider who already uses those

488
00:14:19,889 --> 00:14:21,450
services gets more out of it,

489
00:14:21,450 --> 00:14:22,950
and a customer who owns less

490
00:14:22,950 --> 00:14:24,009
sees less.

491
00:14:24,009 --> 00:14:25,570
The tool reflects the stack
underneath it.

492
00:14:25,570 --> 00:14:27,850
If you want one line to
remember, try this one.

493
00:14:27,850 --> 00:14:29,250
Lighthouse is the front desk for

494
00:14:29,250 --> 00:14:30,809
a fleet of small tenants, not

495
00:14:30,809 --> 00:14:32,049
the machine shop for one large

496
00:14:32,049 --> 00:14:32,809
one.

497
00:14:32,809 --> 00:14:34,730
The recap and one question for
you.

498
00:14:34,730 --> 00:14:36,409
So the short version goes like
this.

499
00:14:36,409 --> 00:14:38,830
Microsoft three hundred sixty
five lighthouse is a free

500
00:14:38,830 --> 00:14:42,250
control room that lets one IT
provider manage Microsoft three

501
00:14:42,250 --> 00:14:44,889
hundred sixty five for many
small businesses at once.

502
00:14:44,889 --> 00:14:46,490
It standardizes security with

503
00:14:46,490 --> 00:14:48,490
baselines, pulls risky accounts,

504
00:14:48,490 --> 00:14:50,009
unhealthy devices and service

505
00:14:50,009 --> 00:14:51,649
problems into one place, and

506
00:14:51,649 --> 00:14:53,129
saves a mountain of repetitive

507
00:14:53,129 --> 00:14:53,889
clicking.

508
00:14:53,889 --> 00:14:55,370
It also has real limits because

509
00:14:55,370 --> 00:14:56,610
it's built for breadth across

510
00:14:56,610 --> 00:14:58,370
many small tenants, with a two

511
00:14:58,370 --> 00:15:00,029
thousand five hundred seat cap,

512
00:15:00,029 --> 00:15:01,809
a region rule and a reliance on

513
00:15:01,809 --> 00:15:03,649
Intune and entry ID to power its

514
00:15:03,649 --> 00:15:04,610
best features.

515
00:15:04,610 --> 00:15:05,929
So let me put the question to
you.

516
00:15:05,929 --> 00:15:07,350
If your company hired an outside

517
00:15:07,350 --> 00:15:09,309
IT provider tomorrow, would you

518
00:15:09,309 --> 00:15:10,690
know how they keep your tenants

519
00:15:10,690 --> 00:15:11,970
safe, or would you have no idea

520
00:15:11,970 --> 00:15:13,370
if this made the topic feel less

521
00:15:13,370 --> 00:15:14,129
intimidating?

522
00:15:14,129 --> 00:15:17,570
Subscribe to M365 FM to master
the tools and the mindset

523
00:15:17,570 --> 00:15:19,129
shaping the future of work.
