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

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

3
00:00:06,320 --> 00:00:08,839
Why being in the cloud is not
the same as being backed up.

4
00:00:08,839 --> 00:00:10,119
Most people assume Microsoft

5
00:00:10,119 --> 00:00:11,359
already backs up their email,

6
00:00:11,359 --> 00:00:12,439
and that assumption is where the

7
00:00:12,439 --> 00:00:13,400
trouble starts.

8
00:00:13,400 --> 00:00:16,600
Your files sit on Microsoft's
servers so they feel safe, but a

9
00:00:16,600 --> 00:00:19,199
server staying online is a
different job from handing you a

10
00:00:19,199 --> 00:00:20,559
clean copy of last week.

11
00:00:20,559 --> 00:00:24,120
Welcome to the M365 FM podcast,
where we explore the people,

12
00:00:24,120 --> 00:00:26,440
ideas and technologies shaping
the future of work.

13
00:00:26,440 --> 00:00:27,399
Today we're talking about

14
00:00:27,399 --> 00:00:28,640
Microsoft three hundred sixty

15
00:00:28,640 --> 00:00:30,280
five backup, the paid layer

16
00:00:30,280 --> 00:00:32,039
Microsoft built for exactly that

17
00:00:32,039 --> 00:00:32,439
job.

18
00:00:32,439 --> 00:00:35,719
It covers three things costs by
the gigabyte and leaves one gap

19
00:00:35,719 --> 00:00:37,240
that surprises almost everyone.

20
00:00:37,240 --> 00:00:39,840
By the end, you will know what
it protects, what it costs, and

21
00:00:39,840 --> 00:00:40,719
where it stops.

22
00:00:40,719 --> 00:00:42,920
There's a piece of this that
trips up even careful teams.

23
00:00:42,920 --> 00:00:44,200
When you open outlook or

24
00:00:44,200 --> 00:00:45,439
OneDrive, you're looking at a

25
00:00:45,439 --> 00:00:45,759
service.

26
00:00:45,759 --> 00:00:49,600
Microsoft works hard to keep
online and that work is real.

27
00:00:49,600 --> 00:00:52,600
Microsoft runs the servers,
copies your data across

28
00:00:52,600 --> 00:00:55,399
buildings and regions, and swaps
in a healthy copy.

29
00:00:55,399 --> 00:00:56,859
When hardware fails, none of

30
00:00:56,859 --> 00:00:58,039
that hands you a clean copy of

31
00:00:58,039 --> 00:00:59,390
your data from an earlier point

32
00:00:59,390 --> 00:01:00,030
in time.

33
00:01:00,030 --> 00:01:03,350
Microsoft's own position on this
hasn't changed, and it's simple

34
00:01:03,350 --> 00:01:06,150
enough to say plainly Microsoft
keeps the platform running, and

35
00:01:06,150 --> 00:01:08,590
you stay responsible for your
data and for the recovery

36
00:01:08,590 --> 00:01:10,150
decisions your business needs.

37
00:01:10,150 --> 00:01:11,310
Those are two different jobs,

38
00:01:11,310 --> 00:01:12,349
and only one of them happens

39
00:01:12,349 --> 00:01:13,230
automatically.

40
00:01:13,230 --> 00:01:14,829
The way to picture it is simple.

41
00:01:14,829 --> 00:01:15,870
A live service is like a

42
00:01:15,870 --> 00:01:17,090
building that stays open every

43
00:01:17,090 --> 00:01:18,469
day with the lights on and the

44
00:01:18,469 --> 00:01:19,510
doors unlocked.

45
00:01:19,510 --> 00:01:22,230
A backup is a photograph of that
building from last Tuesday, kept

46
00:01:22,230 --> 00:01:24,750
somewhere safe in case the
original changes for the worse.

47
00:01:24,750 --> 00:01:26,069
Microsoft is very good at

48
00:01:26,069 --> 00:01:27,430
keeping the building open and

49
00:01:27,430 --> 00:01:27,709
keeping.

50
00:01:27,709 --> 00:01:29,989
The photograph has always been
the customer's job.

51
00:01:29,989 --> 00:01:32,670
Unless you pay for a tool that
does it for you.

52
00:01:32,670 --> 00:01:35,109
Available and recoverable are
not the same word.

53
00:01:35,109 --> 00:01:36,549
A service can be up and running,

54
00:01:36,549 --> 00:01:37,950
while a file you deleted three

55
00:01:37,950 --> 00:01:39,670
months ago is simply gone, or

56
00:01:39,670 --> 00:01:40,989
while an attacker has quietly

57
00:01:40,989 --> 00:01:42,189
changed the version you are

58
00:01:42,189 --> 00:01:43,549
counting on.

59
00:01:43,549 --> 00:01:44,750
Your recycle bin looks like a

60
00:01:44,750 --> 00:01:46,109
safety net, but it has a clock

61
00:01:46,109 --> 00:01:46,510
attached.

62
00:01:46,510 --> 00:01:48,750
And when the clock runs out, the
file doesn't come back.

63
00:01:48,750 --> 00:01:51,430
So the honest question isn't
whether Microsoft keeps your

64
00:01:51,430 --> 00:01:53,230
email online because it does.

65
00:01:53,230 --> 00:01:54,430
The question is what happens on

66
00:01:54,430 --> 00:01:55,590
the day you need yesterday's

67
00:01:55,590 --> 00:01:56,349
version back?

68
00:01:56,349 --> 00:01:58,810
And that's where a real backup
earns its place.

69
00:01:58,810 --> 00:02:01,609
What Microsoft three hundred
sixty five backup actually is

70
00:02:01,609 --> 00:02:03,989
Microsoft three hundred sixty
five backup is a paid service

71
00:02:03,989 --> 00:02:05,650
Microsoft built and runs itself.

72
00:02:05,650 --> 00:02:06,890
It makes copies of your data at

73
00:02:06,890 --> 00:02:08,370
points in time, then lets you

74
00:02:08,370 --> 00:02:09,610
roll that data back to one of

75
00:02:09,610 --> 00:02:10,930
those points when something goes

76
00:02:10,930 --> 00:02:11,370
wrong.

77
00:02:11,370 --> 00:02:14,449
It isn't a third party tool
bolted onto your account, and it

78
00:02:14,449 --> 00:02:17,250
isn't a setting you flip once
and forget it exists, because

79
00:02:17,250 --> 00:02:20,810
Microsoft's own recovery tools,
useful as they are, were never

80
00:02:20,810 --> 00:02:24,009
built to roll back an entire
site or an entire mailbox after

81
00:02:24,009 --> 00:02:25,169
a serious incident.

82
00:02:25,169 --> 00:02:26,569
Backup fills that one job, and

83
00:02:26,569 --> 00:02:27,650
it does it without copying your

84
00:02:27,650 --> 00:02:28,849
data outside Microsoft's own

85
00:02:28,849 --> 00:02:29,210
boundary.

86
00:02:29,210 --> 00:02:30,370
It protects three things, and

87
00:02:30,370 --> 00:02:31,289
the list is shorter than you

88
00:02:31,289 --> 00:02:32,210
might expect.

89
00:02:32,210 --> 00:02:33,569
The first is SharePoint sites,

90
00:02:33,569 --> 00:02:34,610
which is where most team

91
00:02:34,610 --> 00:02:35,930
documents and shared libraries

92
00:02:35,930 --> 00:02:36,449
live.

93
00:02:36,449 --> 00:02:37,810
The second is OneDrive accounts,

94
00:02:37,810 --> 00:02:39,210
which is each person's own file

95
00:02:39,210 --> 00:02:39,849
space.

96
00:02:39,849 --> 00:02:41,530
The third is Exchange Mailboxes,

97
00:02:41,530 --> 00:02:43,169
which covers email, calendar,

98
00:02:43,169 --> 00:02:44,750
contacts, and tasks for

99
00:02:44,750 --> 00:02:45,449
mailboxes.

100
00:02:45,449 --> 00:02:48,289
It supports both user mailboxes
and shared mailboxes, and it

101
00:02:48,289 --> 00:02:50,849
doesn't support room mailboxes
or group mailboxes.

102
00:02:50,849 --> 00:02:53,210
Two words will carry through the
rest of this episode, so they

103
00:02:53,210 --> 00:02:54,650
need a quick definition.

104
00:02:54,650 --> 00:02:56,599
A workload is one of those three
areas.

105
00:02:56,599 --> 00:02:59,240
So SharePoint is a workload and
so is exchange.

106
00:02:59,240 --> 00:03:01,159
A restore point is a saved
moment in time.

107
00:03:01,159 --> 00:03:03,120
You can return to a bit like a
bookmark.

108
00:03:03,120 --> 00:03:05,080
You can jump back to when a page
goes wrong.

109
00:03:05,080 --> 00:03:06,520
There's one more shape to this.

110
00:03:06,520 --> 00:03:07,599
You can run this straight from

111
00:03:07,599 --> 00:03:08,520
the Microsoft three hundred

112
00:03:08,520 --> 00:03:10,400
sixty five Admin Center, or you

113
00:03:10,400 --> 00:03:12,240
can use a partner application

114
00:03:12,240 --> 00:03:13,719
built on the same Microsoft

115
00:03:13,719 --> 00:03:15,199
backup platform.

116
00:03:15,199 --> 00:03:17,879
Either way, you pay by the
gigabyte rather than by the

117
00:03:17,879 --> 00:03:21,080
person, and that billing choice
sets up the next surprise

118
00:03:21,080 --> 00:03:22,639
recycle bins version.

119
00:03:22,639 --> 00:03:25,120
History and real backup are
three different things.

120
00:03:25,120 --> 00:03:27,680
Before you spend anything, it
helps to know what you already

121
00:03:27,680 --> 00:03:30,199
get for free, because plenty of
people pay for backup without

122
00:03:30,199 --> 00:03:33,199
understanding why the free
options weren't enough.

123
00:03:33,199 --> 00:03:34,699
SharePoint and OneDrive give you

124
00:03:34,699 --> 00:03:36,280
version history so you can pull

125
00:03:36,280 --> 00:03:37,560
up an older copy of a single

126
00:03:37,560 --> 00:03:38,199
file.

127
00:03:38,199 --> 00:03:39,539
They also give you two recycle

128
00:03:39,539 --> 00:03:41,120
bins, and the second one holds

129
00:03:41,120 --> 00:03:42,879
deleted content for about ninety

130
00:03:42,879 --> 00:03:43,360
three days.

131
00:03:43,360 --> 00:03:44,639
There's a files restore feature

132
00:03:44,639 --> 00:03:46,000
too, which can roll a library

133
00:03:46,000 --> 00:03:47,080
back to a point within the last

134
00:03:47,080 --> 00:03:47,919
thirty days.

135
00:03:47,919 --> 00:03:49,520
Exchange keeps deleted items for

136
00:03:49,520 --> 00:03:51,400
fourteen days by default, and an

137
00:03:51,400 --> 00:03:52,520
administrator can stretch that

138
00:03:52,520 --> 00:03:53,939
to thirty for an ordinary

139
00:03:53,939 --> 00:03:54,219
mistake.

140
00:03:54,219 --> 00:03:55,419
That's genuinely enough.

141
00:03:55,419 --> 00:03:56,460
Someone deletes the wrong

142
00:03:56,460 --> 00:03:57,419
spreadsheet on a Tuesday

143
00:03:57,419 --> 00:03:58,979
afternoon and you pull it out of

144
00:03:58,979 --> 00:04:00,419
the recycle bin in about five

145
00:04:00,419 --> 00:04:01,020
minutes.

146
00:04:01,020 --> 00:04:02,620
Nobody needs a paid service for
that.

147
00:04:02,620 --> 00:04:04,659
The trouble starts when the
damage is bigger than one.

148
00:04:04,659 --> 00:04:06,099
File picture ransomware that

149
00:04:06,099 --> 00:04:07,500
encrypts thousands of documents

150
00:04:07,500 --> 00:04:08,900
across dozens of sites in a

151
00:04:08,900 --> 00:04:09,740
single night.

152
00:04:09,740 --> 00:04:12,740
Now, the recovery job is a whole
site or a whole mailbox.

153
00:04:12,740 --> 00:04:13,900
And clicking through version

154
00:04:13,900 --> 00:04:15,060
history one item at a time

155
00:04:15,060 --> 00:04:15,979
doesn't scale.

156
00:04:15,979 --> 00:04:17,180
Version history can run out as

157
00:04:17,180 --> 00:04:18,459
well because administrators cap

158
00:04:18,459 --> 00:04:19,939
how many versions get kept, and

159
00:04:19,939 --> 00:04:21,600
every recycle bin has an expiry

160
00:04:21,600 --> 00:04:21,860
date.

161
00:04:21,860 --> 00:04:24,100
There's a smaller version of the
same problem to.

162
00:04:24,100 --> 00:04:24,540
A manager.

163
00:04:24,540 --> 00:04:26,980
Spends a week editing a policy
document, then realizes the

164
00:04:26,980 --> 00:04:29,259
version they wanted is six
revisions back and the version

165
00:04:29,259 --> 00:04:30,339
limit cut it off.

166
00:04:30,339 --> 00:04:31,660
Version history is built for the

167
00:04:31,660 --> 00:04:33,220
last few edits, not for the kind

168
00:04:33,220 --> 00:04:34,459
of memory a business sometimes

169
00:04:34,459 --> 00:04:34,779
needs.

170
00:04:34,779 --> 00:04:36,220
There's another confusion here.

171
00:04:36,220 --> 00:04:38,300
Retention and legal hold are not
backup.

172
00:04:38,300 --> 00:04:41,019
Retention keeps information
around because a policy or a law

173
00:04:41,019 --> 00:04:41,899
says you must.

174
00:04:41,899 --> 00:04:44,579
And legal hold is built to
export data for a case.

175
00:04:44,579 --> 00:04:46,660
Neither one is designed to
handle a broken site.

176
00:04:46,660 --> 00:04:47,100
Back to you.

177
00:04:47,100 --> 00:04:49,740
In a working state, even
disaster recovery is a different

178
00:04:49,740 --> 00:04:52,569
animal because it keeps your
data in its current state rather

179
00:04:52,569 --> 00:04:54,009
than an older, healthier one.

180
00:04:54,009 --> 00:04:55,089
The short way to hold it all

181
00:04:55,089 --> 00:04:56,689
together is that the free tools

182
00:04:56,689 --> 00:04:57,569
protect you from today's

183
00:04:57,569 --> 00:04:59,009
mistake, while backup protects

184
00:04:59,009 --> 00:05:00,250
you from a bad day that already

185
00:05:00,250 --> 00:05:00,769
spread.

186
00:05:00,769 --> 00:05:01,970
That leaves a real gap.

187
00:05:01,970 --> 00:05:03,730
And the next question is how far

188
00:05:03,730 --> 00:05:05,089
back a proper backup can take

189
00:05:05,089 --> 00:05:05,730
you.

190
00:05:05,730 --> 00:05:08,730
How far back it can take you,
and how fast you get data back.

191
00:05:08,730 --> 00:05:11,610
The first number to understand
is the recovery window, and it's

192
00:05:11,610 --> 00:05:12,449
the setting you choose.

193
00:05:12,449 --> 00:05:13,769
You can keep restore points for

194
00:05:13,769 --> 00:05:15,209
three months, six months, one

195
00:05:15,209 --> 00:05:16,970
year, or two years if you change

196
00:05:16,970 --> 00:05:17,490
nothing.

197
00:05:17,490 --> 00:05:19,490
Existing policies sit at one
year.

198
00:05:19,490 --> 00:05:22,310
So a site you protect today may
only be recoverable back to

199
00:05:22,310 --> 00:05:24,089
about this time next year.

200
00:05:24,089 --> 00:05:26,689
The second number is how often
those points get made.

201
00:05:26,689 --> 00:05:29,170
And this is the one people
misread for your SharePoint

202
00:05:29,170 --> 00:05:30,689
sites and OneDrive accounts.

203
00:05:30,689 --> 00:05:33,170
You get a point roughly every
ten minutes across the last two

204
00:05:33,170 --> 00:05:36,689
weeks, and then weekly snapshots
out to a year for exchange.

205
00:05:36,689 --> 00:05:37,970
Those points keep coming about

206
00:05:37,970 --> 00:05:39,449
every ten minutes for the entire

207
00:05:39,449 --> 00:05:39,889
year.

208
00:05:39,889 --> 00:05:41,329
Microsoft is not photographing

209
00:05:41,329 --> 00:05:42,649
your entire mailbox every ten

210
00:05:42,649 --> 00:05:43,889
minutes, and that distinction

211
00:05:43,889 --> 00:05:44,370
matters.

212
00:05:44,370 --> 00:05:47,290
What happens is that changes get
saved as a new version inside

213
00:05:47,290 --> 00:05:50,470
that ten minute window, no
matter how many edits happen and

214
00:05:50,470 --> 00:05:52,149
deletions are always captured.

215
00:05:52,149 --> 00:05:53,310
The ten minute figure describes

216
00:05:53,310 --> 00:05:54,550
how much recent change you can

217
00:05:54,550 --> 00:05:55,149
recover.

218
00:05:55,149 --> 00:05:57,269
Not a fresh copy of everything
on a timer.

219
00:05:57,269 --> 00:05:59,430
Speed is the next thing people
get wrong.

220
00:05:59,430 --> 00:06:02,189
A single site smaller than about
a terabyte can come back in

221
00:06:02,189 --> 00:06:02,990
under twenty minutes.

222
00:06:02,990 --> 00:06:03,790
When you use one of the

223
00:06:03,790 --> 00:06:04,990
recommended Express Restore

224
00:06:04,990 --> 00:06:06,029
points.

225
00:06:06,029 --> 00:06:08,790
At larger scale, restores have
run at a median of about two

226
00:06:08,790 --> 00:06:09,949
terabytes an hour.

227
00:06:09,949 --> 00:06:11,110
Exchange restores move at

228
00:06:11,110 --> 00:06:12,209
roughly one hundred to five

229
00:06:12,209 --> 00:06:13,550
hundred items per mailbox per

230
00:06:13,550 --> 00:06:14,069
minute.

231
00:06:14,069 --> 00:06:15,589
To make that real, imagine a

232
00:06:15,589 --> 00:06:16,910
finance team loses a shared

233
00:06:16,910 --> 00:06:18,230
folder of contracts on a Friday

234
00:06:18,230 --> 00:06:19,389
morning with a recommended

235
00:06:19,389 --> 00:06:20,230
restore point.

236
00:06:20,230 --> 00:06:22,970
They can be back in business
before lunch, and the restore

237
00:06:22,970 --> 00:06:25,910
doesn't get slower just because
the folder is large.

238
00:06:25,910 --> 00:06:28,230
What slows things down is
restoring many sites at once,

239
00:06:28,230 --> 00:06:30,310
which is exactly what happens in
a big incident.

240
00:06:30,310 --> 00:06:33,029
Restore speed depends far more
on how many sites you're

241
00:06:33,029 --> 00:06:35,470
restoring and which restore
point you choose than on how

242
00:06:35,470 --> 00:06:36,709
much data you have.

243
00:06:36,709 --> 00:06:38,670
Restoring one huge site can be

244
00:06:38,670 --> 00:06:39,810
quicker than restoring fifty

245
00:06:39,810 --> 00:06:40,670
small ones, which is the

246
00:06:40,670 --> 00:06:41,910
opposite of the way it usually

247
00:06:41,910 --> 00:06:42,829
gets pictured.

248
00:06:42,829 --> 00:06:45,430
One last detail decides how a
restore feels.

249
00:06:45,430 --> 00:06:48,139
A full site restore rolls
everything back to the moment

250
00:06:48,139 --> 00:06:49,660
you picked and it overwrites.

251
00:06:49,660 --> 00:06:51,420
Anything changed since then?

252
00:06:51,420 --> 00:06:52,740
A file version restore moves a

253
00:06:52,740 --> 00:06:53,819
single file forward to that

254
00:06:53,819 --> 00:06:55,019
moment while keeping the older

255
00:06:55,019 --> 00:06:56,060
versions intact.

256
00:06:56,060 --> 00:06:57,459
Pick the wrong one and you can

257
00:06:57,459 --> 00:06:58,980
undo good work along with the

258
00:06:58,980 --> 00:06:59,980
bad.

259
00:06:59,980 --> 00:07:02,339
What it costs and how the
billing actually works.

260
00:07:02,339 --> 00:07:03,459
Now we get to the money.

261
00:07:03,459 --> 00:07:05,819
The list price is fifteen cents
per gigabyte per month of

262
00:07:05,819 --> 00:07:08,339
protected content, and restores
themselves are free.

263
00:07:08,339 --> 00:07:11,139
That sounds simple, and the
simplicity is real, but the way

264
00:07:11,139 --> 00:07:13,899
Microsoft counts a gigabyte is
where the real cost hides.

265
00:07:13,899 --> 00:07:16,540
You don't pay by the user and
you don't pay a flat license.

266
00:07:16,540 --> 00:07:18,860
You pay through an Azure
subscription on a pay as you go

267
00:07:18,860 --> 00:07:20,980
basis, which means the bill
moves with your data.

268
00:07:20,980 --> 00:07:22,259
If you've never touched Azure,

269
00:07:22,259 --> 00:07:23,860
that's fine because the setup

270
00:07:23,860 --> 00:07:24,819
walks you through linking a

271
00:07:24,819 --> 00:07:26,100
subscription, and the backup

272
00:07:26,100 --> 00:07:27,060
service is the thing you're

273
00:07:27,060 --> 00:07:27,620
buying.

274
00:07:27,620 --> 00:07:29,660
The important part is that
you're charged for more than the

275
00:07:29,660 --> 00:07:30,779
files you can see.

276
00:07:30,779 --> 00:07:33,399
The bill includes the first
recycle bin, the second recycle

277
00:07:33,399 --> 00:07:36,540
bin, and any online archives
attached to your mailboxes.

278
00:07:36,540 --> 00:07:39,579
Microsoft's own example makes it
concrete protect a one gigabyte

279
00:07:39,579 --> 00:07:42,360
site that has half a gigabyte
sitting in its second recycle

280
00:07:42,360 --> 00:07:44,990
bin, and add a one gigabyte
mailbox with a one gigabyte

281
00:07:44,990 --> 00:07:47,300
online archive, and you're
billed for three and a half

282
00:07:47,300 --> 00:07:48,839
gigabytes instead of two.

283
00:07:48,839 --> 00:07:51,480
There's another catch, and it
shows up before the bill does.

284
00:07:51,480 --> 00:07:52,860
Once content is protected, you

285
00:07:52,860 --> 00:07:54,120
keep paying for the retained

286
00:07:54,120 --> 00:07:55,439
copy until the recovery window

287
00:07:55,439 --> 00:07:56,240
runs out.

288
00:07:56,240 --> 00:07:57,600
Delete half a site and the next

289
00:07:57,600 --> 00:07:58,720
bill stays about the same,

290
00:07:58,720 --> 00:07:59,759
because the backup is still

291
00:07:59,759 --> 00:08:01,160
holding the deleted material for

292
00:08:01,160 --> 00:08:01,800
a year.

293
00:08:01,800 --> 00:08:04,519
The bill follows your history
rather than your current size.

294
00:08:04,519 --> 00:08:06,199
Put a number on it for a small
team.

295
00:08:06,199 --> 00:08:09,000
Protect two hundred gigabytes
across your sites and mailboxes,

296
00:08:09,000 --> 00:08:11,639
and the list price works out to
about thirty dollars a month.

297
00:08:11,639 --> 00:08:12,920
The figure moves up or down with

298
00:08:12,920 --> 00:08:14,480
the size of what you protect,

299
00:08:14,480 --> 00:08:15,600
and it includes the deleted

300
00:08:15,600 --> 00:08:17,420
material sitting in your recycle

301
00:08:17,420 --> 00:08:17,959
bins.

302
00:08:17,959 --> 00:08:21,360
So the total you see in a File
Explorer isn't always the total

303
00:08:21,360 --> 00:08:22,519
you pay for.

304
00:08:22,519 --> 00:08:23,959
One piece of good news is that

305
00:08:23,959 --> 00:08:25,339
changing how often restore

306
00:08:25,339 --> 00:08:26,680
points are made doesn't

307
00:08:26,680 --> 00:08:28,279
meaningfully change the cost, so

308
00:08:28,279 --> 00:08:29,439
there's no reason to protect

309
00:08:29,439 --> 00:08:30,839
your data less often to save

310
00:08:30,839 --> 00:08:31,360
money.

311
00:08:31,360 --> 00:08:34,240
Microsoft also publishes a
pricing calculator and usage

312
00:08:34,240 --> 00:08:36,919
reports, which lets you estimate
the bill from real numbers

313
00:08:36,919 --> 00:08:37,879
instead of a guess.

314
00:08:37,879 --> 00:08:40,559
Once you know the price, the
only question left is whether

315
00:08:40,559 --> 00:08:42,894
you're paying for the right
things, and that's where the

316
00:08:42,894 --> 00:08:44,710
coverage list comes in.

317
00:08:44,710 --> 00:08:46,190
The three things it protects and

318
00:08:46,190 --> 00:08:47,789
the one big thing it doesn't

319
00:08:47,789 --> 00:08:48,029
buy.

320
00:08:48,029 --> 00:08:50,110
Now the coverage list should
feel familiar.

321
00:08:50,110 --> 00:08:51,190
Microsoft three hundred sixty

322
00:08:51,190 --> 00:08:52,669
five backup protects SharePoint

323
00:08:52,669 --> 00:08:54,029
sites, OneDrive accounts, and

324
00:08:54,029 --> 00:08:54,990
exchange mailboxes.

325
00:08:54,990 --> 00:08:56,269
And that's the entire list.

326
00:08:56,269 --> 00:08:58,470
Everything else in Microsoft
three hundred sixty five sits

327
00:08:58,470 --> 00:09:02,029
outside it, and the biggest name
on that list is teams, teams,

328
00:09:02,029 --> 00:09:04,669
chats, channel posts, and
replies are not backed up.

329
00:09:04,669 --> 00:09:05,870
This is the misconception that

330
00:09:05,870 --> 00:09:07,649
catches people hardest because

331
00:09:07,649 --> 00:09:08,990
teams feels like the center of

332
00:09:08,990 --> 00:09:10,269
work, and the assumption that

333
00:09:10,269 --> 00:09:12,149
it's protected comes almost for

334
00:09:12,149 --> 00:09:12,509
free.

335
00:09:12,509 --> 00:09:14,950
It isn't protected, and that gap
is easy to miss.

336
00:09:14,950 --> 00:09:16,990
The cost of that gap goes beyond
annoyance.

337
00:09:16,990 --> 00:09:18,389
Teams conversations often hold

338
00:09:18,389 --> 00:09:19,870
the reasoning behind a decision,

339
00:09:19,870 --> 00:09:21,309
the approval, or the context for

340
00:09:21,309 --> 00:09:22,710
a file, and those threads are

341
00:09:22,710 --> 00:09:24,110
exactly what backup cannot

342
00:09:24,110 --> 00:09:24,870
return.

343
00:09:24,870 --> 00:09:27,350
If a channel gets deleted by
mistake, you may get the

344
00:09:27,350 --> 00:09:30,269
documents back and still lose
the story of why they exist.

345
00:09:30,269 --> 00:09:32,509
There's a small mercy here, so
get this part right.

346
00:09:32,509 --> 00:09:35,590
Teams files are a different
story from teams conversations.

347
00:09:35,590 --> 00:09:37,830
A file shared in a channel
usually lives in that team's

348
00:09:37,830 --> 00:09:40,470
SharePoint site, and a file
shared in a chat usually lives

349
00:09:40,470 --> 00:09:41,860
in the sender's OneDrive.

350
00:09:41,860 --> 00:09:43,179
If those underlying places are

351
00:09:43,179 --> 00:09:44,580
protected, the files can come

352
00:09:44,580 --> 00:09:45,139
back.

353
00:09:45,139 --> 00:09:47,860
What can't come back is the
conversation itself, meaning the

354
00:09:47,860 --> 00:09:50,179
messages, the replies, and the
thread around the file.

355
00:09:50,179 --> 00:09:51,379
You can recover the document and

356
00:09:51,379 --> 00:09:52,539
still lose the discussion about

357
00:09:52,539 --> 00:09:52,860
it.

358
00:09:52,860 --> 00:09:54,299
Restoring individual files and

359
00:09:54,299 --> 00:09:55,379
folders is now generally

360
00:09:55,379 --> 00:09:56,620
available for SharePoint and

361
00:09:56,620 --> 00:09:57,779
OneDrive, which matters a lot

362
00:09:57,779 --> 00:09:58,379
for beginners.

363
00:09:58,379 --> 00:10:01,519
You can browse a saved point,
pick the exact files you need,

364
00:10:01,519 --> 00:10:03,899
and put them back in place or
into a new folder.

365
00:10:03,899 --> 00:10:05,820
There are limits to know, and
they're honest ones.

366
00:10:05,820 --> 00:10:08,100
Files in document libraries that
use information rights

367
00:10:08,100 --> 00:10:10,899
management can't be restored
this way, and neither can files

368
00:10:10,899 --> 00:10:11,860
in locked sites.

369
00:10:11,860 --> 00:10:13,659
Exchange is similar but has its
own ceiling.

370
00:10:13,659 --> 00:10:16,700
You can search a mailbox and
restore selected items, but each

371
00:10:16,700 --> 00:10:19,259
restore is capped at one
thousand items, so a broad

372
00:10:19,259 --> 00:10:21,500
search has to be narrowed before
you run it.

373
00:10:21,500 --> 00:10:22,740
That's less a flaw than a nudge.

374
00:10:22,740 --> 00:10:24,379
To be precise, teams is the

375
00:10:24,379 --> 00:10:25,980
loudest gap, but it isn't the

376
00:10:25,980 --> 00:10:27,500
only one, and the rest of the

377
00:10:27,500 --> 00:10:28,580
gaps live somewhere less

378
00:10:28,580 --> 00:10:30,100
obvious.

379
00:10:30,100 --> 00:10:33,179
The other blind spots, identity
settings, and other apps.

380
00:10:33,179 --> 00:10:33,980
Backup protects your

381
00:10:33,980 --> 00:10:35,120
collaboration data, and it

382
00:10:35,120 --> 00:10:36,220
leaves the controls around that

383
00:10:36,220 --> 00:10:37,019
data alone.

384
00:10:37,019 --> 00:10:39,559
Think about the settings that
decide who can sign in, what

385
00:10:39,559 --> 00:10:42,519
they can reach and how mail gets
routed, conditional access

386
00:10:42,519 --> 00:10:45,440
policies, administrator roles,
mail forwarding rules,

387
00:10:45,440 --> 00:10:48,320
connectors, and tenant wide
settings are not part of a data

388
00:10:48,320 --> 00:10:51,720
restore that matters in a
specific and uncomfortable way.

389
00:10:51,720 --> 00:10:53,120
An attacker who gets in often

390
00:10:53,120 --> 00:10:54,519
changes the rules before taking

391
00:10:54,519 --> 00:10:56,240
anything by adding a forwarding

392
00:10:56,240 --> 00:10:57,720
rule, weakening a sign in

393
00:10:57,720 --> 00:10:59,200
policy, or creating a hidden

394
00:10:59,200 --> 00:11:00,879
administrator account.

395
00:11:00,879 --> 00:11:03,000
Restoring your files doesn't
undo any of that.

396
00:11:03,000 --> 00:11:04,440
Those changes need their own
plan.

397
00:11:04,440 --> 00:11:05,559
Usually a mix of exports,

398
00:11:05,559 --> 00:11:06,840
documentation, and a rebuild

399
00:11:06,840 --> 00:11:07,399
checklist.

400
00:11:07,399 --> 00:11:10,279
Identity is its own separate
service, and this is where a lot

401
00:11:10,279 --> 00:11:11,879
of people assume too much.

402
00:11:11,879 --> 00:11:13,399
Microsoft Entra Backup handles

403
00:11:13,399 --> 00:11:14,919
identity objects like users and

404
00:11:14,919 --> 00:11:15,480
groups.

405
00:11:15,480 --> 00:11:18,080
It's a different product with
its own licensing, and it's

406
00:11:18,080 --> 00:11:21,360
still in preview with a short
window of about seven days.

407
00:11:21,360 --> 00:11:24,039
Microsoft three hundred sixty
five backup doesn't recover your

408
00:11:24,039 --> 00:11:26,679
logins, your roles, or your
access rules, and no amount of

409
00:11:26,679 --> 00:11:28,360
data restore will rebuild them.

410
00:11:28,360 --> 00:11:31,440
Identity recovery is a solvable
problem, and Microsoft is

411
00:11:31,440 --> 00:11:32,279
building it out.

412
00:11:32,279 --> 00:11:34,639
The catch is that it's a
separate piece you have to plan

413
00:11:34,639 --> 00:11:36,799
for, rather than something you
inherit for free.

414
00:11:36,799 --> 00:11:38,710
Other applications sit outside
the scope.

415
00:11:38,710 --> 00:11:41,750
Two planar forms Power Platform,

416
00:11:41,750 --> 00:11:43,309
Loop and Viva aren't

417
00:11:43,309 --> 00:11:44,549
automatically protected by the

418
00:11:44,549 --> 00:11:45,909
service, even though they may

419
00:11:45,909 --> 00:11:46,429
hold work.

420
00:11:46,429 --> 00:11:48,230
Your team depends on if a planar

421
00:11:48,230 --> 00:11:49,830
board or a power automate flow

422
00:11:49,830 --> 00:11:50,710
disappears.

423
00:11:50,710 --> 00:11:52,309
Backup won't hand it back.

424
00:11:52,309 --> 00:11:53,490
None of this is a reason to

425
00:11:53,490 --> 00:11:54,950
panic, and it isn't a knock on

426
00:11:54,950 --> 00:11:55,590
the product.

427
00:11:55,590 --> 00:11:56,830
It's a map of how your data is

428
00:11:56,830 --> 00:11:58,230
protected and knowing which

429
00:11:58,230 --> 00:11:59,549
layer covers what is the whole

430
00:11:59,549 --> 00:11:59,870
skill.

431
00:11:59,870 --> 00:12:01,389
That's a skill you have now.

432
00:12:01,389 --> 00:12:04,230
How you turn it on and the
mistakes that trip people up.

433
00:12:04,230 --> 00:12:06,909
Setting this up takes less time
than you might expect, and it

434
00:12:06,909 --> 00:12:07,870
follows two steps.

435
00:12:07,870 --> 00:12:08,990
First, you link an Azure

436
00:12:08,990 --> 00:12:10,350
subscription for pay as you go

437
00:12:10,350 --> 00:12:10,950
billing.

438
00:12:10,950 --> 00:12:12,110
Then you create backup policies

439
00:12:12,110 --> 00:12:13,190
that choose which sites,

440
00:12:13,190 --> 00:12:14,350
accounts, and mailboxes get

441
00:12:14,350 --> 00:12:15,029
protected.

442
00:12:15,029 --> 00:12:17,750
You don't need to be a global
administrator to run it.

443
00:12:17,750 --> 00:12:20,909
A SharePoint administrator can
set it up, and Microsoft added a

444
00:12:20,909 --> 00:12:23,269
dedicated Microsoft three
hundred sixty five backup

445
00:12:23,269 --> 00:12:26,149
administrator role, which lets
you hand out exactly the access

446
00:12:26,149 --> 00:12:26,870
this job needs.

447
00:12:26,870 --> 00:12:29,389
Instead of something far more
powerful, you'll need owner or

448
00:12:29,389 --> 00:12:31,549
contributor rights on that Azure
subscription, so check that

449
00:12:31,549 --> 00:12:32,470
before you start.

450
00:12:32,470 --> 00:12:33,950
You can protect everything, or

451
00:12:33,950 --> 00:12:35,279
you can protect only the things

452
00:12:35,279 --> 00:12:36,009
that matter.

453
00:12:36,009 --> 00:12:38,850
Protecting selectively keeps the
bill down, but it creates a

454
00:12:38,850 --> 00:12:42,009
slower risk because new sites
and mailboxes keep appearing and

455
00:12:42,009 --> 00:12:43,690
can slip outside your policy.

456
00:12:43,690 --> 00:12:46,090
If you go selective, someone has
to watch the edges.

457
00:12:46,090 --> 00:12:48,009
There's a trade off hiding in
that choice.

458
00:12:48,009 --> 00:12:49,470
Broad protection is easier to

459
00:12:49,470 --> 00:12:50,690
forecast and harder to get

460
00:12:50,690 --> 00:12:51,850
wrong, while selective

461
00:12:51,850 --> 00:12:53,289
protection saves money only if

462
00:12:53,289 --> 00:12:54,490
your list of important things

463
00:12:54,490 --> 00:12:55,649
stays accurate.

464
00:12:55,649 --> 00:12:59,009
New projects, new teams, and new
mailboxes all create fresh gaps,

465
00:12:59,009 --> 00:13:00,809
and those gaps need an owner?

466
00:13:00,809 --> 00:13:03,250
Turn on the admin email alerts
and do it on day one.

467
00:13:03,250 --> 00:13:05,929
The events that should worry
you, like pausing a policy or

468
00:13:05,929 --> 00:13:08,830
starting the offboarding of your
backups are exactly the events

469
00:13:08,830 --> 00:13:10,690
nobody notices in real time.

470
00:13:10,690 --> 00:13:13,889
The alert turns a silent mistake
into a message in an inbox.

471
00:13:13,889 --> 00:13:15,690
A few mistakes show up again and
again.

472
00:13:15,690 --> 00:13:18,690
People assume the service is on
by default, and it isn't.

473
00:13:18,690 --> 00:13:21,850
People expect hybrid exchange
mailboxes to be protected, and

474
00:13:21,850 --> 00:13:25,049
only mailboxes fully hosted in
exchange online can be.

475
00:13:25,049 --> 00:13:26,330
People assume every SharePoint

476
00:13:26,330 --> 00:13:27,889
site is supported and a handful

477
00:13:27,889 --> 00:13:29,529
of older or special templates

478
00:13:29,529 --> 00:13:30,210
aren't.

479
00:13:30,210 --> 00:13:31,330
Some people turn off pay as you

480
00:13:31,330 --> 00:13:32,570
go without realizing that

481
00:13:32,570 --> 00:13:34,019
turning it off starts the off

482
00:13:34,019 --> 00:13:35,000
boarding process for their

483
00:13:35,000 --> 00:13:35,399
backups.

484
00:13:35,399 --> 00:13:36,639
That offboarding isn't instant,

485
00:13:36,639 --> 00:13:37,720
which is the one bit of comfort

486
00:13:37,720 --> 00:13:37,919
here.

487
00:13:37,919 --> 00:13:39,039
There's a ninety day grace

488
00:13:39,039 --> 00:13:40,720
period to recover backups after

489
00:13:40,720 --> 00:13:41,759
you switch it off, and

490
00:13:41,759 --> 00:13:43,240
shortening that to seven days

491
00:13:43,240 --> 00:13:44,759
requires a second administrator

492
00:13:44,759 --> 00:13:45,720
to approve.

493
00:13:45,720 --> 00:13:47,799
There's also a testing limit
that surprises teams.

494
00:13:47,799 --> 00:13:50,600
You can run a restore purely to
test it about twice a month per

495
00:13:50,600 --> 00:13:53,740
protected item, so test on
purpose rather than by accident

496
00:13:53,740 --> 00:13:56,159
when you actually need it and
when you don't.

497
00:13:56,159 --> 00:13:57,360
The clearest case for paying is

498
00:13:57,360 --> 00:13:58,639
ransomware, where an attack

499
00:13:58,639 --> 00:13:59,720
encrypts whole sites and

500
00:13:59,720 --> 00:14:01,399
mailboxes in one sweep, and you

501
00:14:01,399 --> 00:14:02,840
need a clean rollback to before

502
00:14:02,840 --> 00:14:03,679
the damage.

503
00:14:03,679 --> 00:14:06,340
A close second is a large
accidental deletion where

504
00:14:06,340 --> 00:14:08,519
thousands of files vanish at
once, and picking through a

505
00:14:08,519 --> 00:14:09,919
recycle bin is hopeless.

506
00:14:09,919 --> 00:14:11,480
Another is a person leaving when

507
00:14:11,480 --> 00:14:12,919
their mailbox or OneDrive still

508
00:14:12,919 --> 00:14:14,320
has to be recoverable long after

509
00:14:14,320 --> 00:14:15,200
they're gone.

510
00:14:15,200 --> 00:14:18,320
A regulated site that needs a
longer memory than a recycle bin

511
00:14:18,320 --> 00:14:20,000
can offer rounds out the list.

512
00:14:20,000 --> 00:14:21,159
Skipping it can make sense in

513
00:14:21,159 --> 00:14:22,639
narrower cases if your data is

514
00:14:22,639 --> 00:14:23,039
small.

515
00:14:23,039 --> 00:14:25,659
If mistakes get caught the same
day, and if the free recycle

516
00:14:25,659 --> 00:14:28,879
bins and version history already
cover your worst realistic case,

517
00:14:28,879 --> 00:14:31,860
then a paid layer may be more
comfort than necessity.

518
00:14:31,860 --> 00:14:33,860
The deciding factor isn't really
the price.

519
00:14:33,860 --> 00:14:34,700
It's two numbers.

520
00:14:34,700 --> 00:14:36,379
People rarely write down how

521
00:14:36,379 --> 00:14:38,059
much data you can afford to lose

522
00:14:38,059 --> 00:14:39,419
and how long you can afford to

523
00:14:39,419 --> 00:14:39,940
be down.

524
00:14:39,940 --> 00:14:42,659
Answer those honestly, and the
choice tends to make itself.

525
00:14:42,659 --> 00:14:45,860
Most organizations end up using
a mix, and that isn't a failure.

526
00:14:45,860 --> 00:14:48,740
The free tools handle small
mistakes, backup handles the big

527
00:14:48,740 --> 00:14:51,659
rollback and retention handles
the legal reasons each one

528
00:14:51,659 --> 00:14:52,980
covers a job the others can't.

529
00:14:52,980 --> 00:14:54,980
That honesty is the whole point
of this episode.

530
00:14:54,980 --> 00:14:56,100
None of it is about fear.

531
00:14:56,100 --> 00:14:58,820
It's about knowing which layers
of protection you actually have.

532
00:14:58,820 --> 00:15:01,100
So you aren't counting on one
that was never there.

533
00:15:01,100 --> 00:15:03,299
Here's the short version of
everything we covered.

534
00:15:03,299 --> 00:15:05,940
Your data in the cloud isn't
automatically backed up.

535
00:15:05,940 --> 00:15:07,220
Microsoft three hundred sixty

536
00:15:07,220 --> 00:15:08,899
five backup adds a real recovery

537
00:15:08,899 --> 00:15:10,779
layer for SharePoint, OneDrive,

538
00:15:10,779 --> 00:15:12,299
and exchange restores from

539
00:15:12,299 --> 00:15:13,720
points in time, builds by the

540
00:15:13,720 --> 00:15:14,960
gigabyte, and still leaves

541
00:15:14,960 --> 00:15:16,340
teams, conversations, identity,

542
00:15:16,340 --> 00:15:17,620
and other apps out of the

543
00:15:17,620 --> 00:15:18,299
picture.

544
00:15:18,299 --> 00:15:19,820
So I'll leave you with one
question.

545
00:15:19,820 --> 00:15:21,000
If your recycle bin emptied

546
00:15:21,000 --> 00:15:21,980
tonight, which file of yours

547
00:15:21,980 --> 00:15:23,059
would you not be able to get

548
00:15:23,059 --> 00:15:24,500
back if this made the topic feel

549
00:15:24,500 --> 00:15:25,419
less intimidating?

550
00:15:25,419 --> 00:15:28,860
Subscribe to M365 FM to master
the tools and the mindset

551
00:15:28,860 --> 00:15:30,539
shaping the future of work.
