WEBVTT

1
00:00:00.080 --> 00:00:02.680
<v Speaker 1>Welcome back to the deep dive. Today we are tackling

2
00:00:02.680 --> 00:00:06.360
<v Speaker 1>something huge, a really foundational look at Microsoft three sixty

3
00:00:06.400 --> 00:00:10.880
<v Speaker 1>five and look, if you still think M three sixty

4
00:00:10.880 --> 00:00:13.759
<v Speaker 1>five is just Word and Excel while you're missing some

5
00:00:13.919 --> 00:00:16.559
<v Speaker 1>massive shifts and how businesses compute today.

6
00:00:16.359 --> 00:00:19.079
<v Speaker 2>That's exactly right. M three sixty five isn't just a

7
00:00:19.079 --> 00:00:22.079
<v Speaker 2>software bundle. It's really how cloud computing works in the

8
00:00:22.199 --> 00:00:24.839
<v Speaker 2>enterprise world. Our goal today is to break down the

9
00:00:24.879 --> 00:00:30.000
<v Speaker 2>key ideas cloud structure, flexibility, and crucially modern security, so

10
00:00:30.039 --> 00:00:32.240
<v Speaker 2>you get the practical knowledge behind the whole platform.

11
00:00:32.280 --> 00:00:34.759
<v Speaker 1>Okay, let's start at the beginning, the big economic change.

12
00:00:34.840 --> 00:00:37.640
<v Speaker 1>So cloud computing, we usually define it as getting to

13
00:00:37.679 --> 00:00:40.479
<v Speaker 1>your resources, storing your data all over the internet. It's

14
00:00:40.479 --> 00:00:42.960
<v Speaker 1>delivered on demand, pay as you go pricing, and the

15
00:00:43.039 --> 00:00:46.159
<v Speaker 1>key thing here it flips it spending from capex buying

16
00:00:46.159 --> 00:00:49.000
<v Speaker 1>big servers to opex operational expenditure. Right.

17
00:00:49.000 --> 00:00:50.679
<v Speaker 2>And what's really interesting is that the money side is

18
00:00:50.719 --> 00:00:54.200
<v Speaker 2>also the strategy side. You're shifting it away from, you know,

19
00:00:54.240 --> 00:00:56.159
<v Speaker 2>making big bets on hardware you hope.

20
00:00:56.039 --> 00:00:58.000
<v Speaker 1>Last five years, yeah before a huge.

21
00:00:57.799 --> 00:01:02.679
<v Speaker 2>Upgrade cost exactly two, a more dynamic subscription approach. It

22
00:01:02.719 --> 00:01:06.280
<v Speaker 2>gets rid of those huge initial costs. No building data centers,

23
00:01:06.400 --> 00:01:09.480
<v Speaker 2>buying racks of servers, worrying about power and cooling two

24
00:01:09.519 --> 00:01:11.799
<v Speaker 2>and a four debit. You just pay for what you

25
00:01:11.840 --> 00:01:14.120
<v Speaker 2>actually use and you get flexibility instantly.

26
00:01:14.200 --> 00:01:18.000
<v Speaker 1>And that flexibility it depends on what three core engineering ideas.

27
00:01:18.040 --> 00:01:20.599
<v Speaker 1>We should probably clarify those quickly because they really are

28
00:01:20.640 --> 00:01:23.319
<v Speaker 1>the foundation for M three sixty five working reliably.

29
00:01:23.519 --> 00:01:28.359
<v Speaker 2>Yeah, good idea. So first is high availability or HA. Basically,

30
00:01:28.400 --> 00:01:30.879
<v Speaker 2>if one server goes down, another one just takes over immediately,

31
00:01:31.000 --> 00:01:32.079
<v Speaker 2>no downtime for the user.

32
00:01:32.200 --> 00:01:32.480
<v Speaker 1>Okay.

33
00:01:32.519 --> 00:01:36.400
<v Speaker 2>Then there's elasticity. That's the system's ability to automatically add

34
00:01:36.480 --> 00:01:40.480
<v Speaker 2>or remove resources like processing, power or storage to perfectly

35
00:01:40.519 --> 00:01:43.000
<v Speaker 2>match what's needed. Right. Then, say you acquire a company

36
00:01:43.040 --> 00:01:45.400
<v Speaker 2>and suddenly need ten thousand more teams users.

37
00:01:45.200 --> 00:01:47.439
<v Speaker 1>You get them straight away, You get it instantly.

38
00:01:47.719 --> 00:01:50.799
<v Speaker 2>And third is agility, right, agility, which is just the

39
00:01:50.840 --> 00:01:54.079
<v Speaker 2>ability to adapt quickly, deploy new apps or services fast.

40
00:01:54.239 --> 00:01:56.280
<v Speaker 2>Need a new test environment, you can spin it up

41
00:01:56.319 --> 00:01:58.519
<v Speaker 2>in minutes, not week for months like the old days.

42
00:01:58.920 --> 00:02:01.200
<v Speaker 2>These three things are one. M three sixty five can

43
00:02:01.239 --> 00:02:03.159
<v Speaker 2>operate on a massive global scale.

44
00:02:03.280 --> 00:02:06.120
<v Speaker 1>So once we get the scale and the flexibility of

45
00:02:06.159 --> 00:02:09.360
<v Speaker 1>the cloud. Where does M three sixty five actually fit in?

46
00:02:09.520 --> 00:02:12.319
<v Speaker 1>The sources talk about a cloud service stack kind of

47
00:02:12.319 --> 00:02:14.879
<v Speaker 1>like layers, right, four main categories exactly.

48
00:02:14.919 --> 00:02:16.919
<v Speaker 2>It's helpful to think of it as layers built on

49
00:02:16.960 --> 00:02:19.919
<v Speaker 2>top of each other. It's all about who manages what,

50
00:02:20.120 --> 00:02:23.520
<v Speaker 2>the provider or you, the customer. At the very bottom,

51
00:02:23.560 --> 00:02:26.719
<v Speaker 2>you've got infrastructure as a service IAS. This is the

52
00:02:26.719 --> 00:02:31.680
<v Speaker 2>basic building blocks virtual machines, networks, storage. The provider secures

53
00:02:31.719 --> 00:02:34.960
<v Speaker 2>the physical stuff, but you manage the OS, the apps,

54
00:02:35.240 --> 00:02:35.680
<v Speaker 2>the data.

55
00:02:35.759 --> 00:02:38.000
<v Speaker 1>Okay. Then moving up a level, platform is.

56
00:02:37.960 --> 00:02:42.199
<v Speaker 2>A service boss. This gives developers an environment to build

57
00:02:42.240 --> 00:02:45.520
<v Speaker 2>and test applications without worrying about the underlying servers or

58
00:02:45.560 --> 00:02:48.240
<v Speaker 2>operating systems. The cloud provider takes care of all that

59
00:02:48.280 --> 00:02:49.680
<v Speaker 2>infrastructure management underneath.

60
00:02:49.759 --> 00:02:52.080
<v Speaker 1>And then at the top where M three sixty five

61
00:02:52.120 --> 00:02:54.319
<v Speaker 1>mostly operates, software is a service.

62
00:02:54.039 --> 00:02:57.919
<v Speaker 2>Sauce sauce yep. This is where the provider hosts and

63
00:02:58.000 --> 00:03:01.240
<v Speaker 2>maintains well pretty much everything, the app implication itself, the

64
00:03:01.240 --> 00:03:04.039
<v Speaker 2>infrastructure it runs on, all the updates, the security patches.

65
00:03:04.439 --> 00:03:06.960
<v Speaker 2>You the user, just access the software over the internet.

66
00:03:06.960 --> 00:03:08.719
<v Speaker 2>That's the main model for M three sixty five.

67
00:03:09.000 --> 00:03:11.479
<v Speaker 1>So If Sauce is the main delivery model, how does

68
00:03:11.520 --> 00:03:14.719
<v Speaker 1>Microsoft actually bundle all this capability up so businesses can

69
00:03:15.120 --> 00:03:16.039
<v Speaker 1>buy it and use it.

70
00:03:16.280 --> 00:03:19.039
<v Speaker 2>Well, that's basically what Microsoft three sixty five is. It's

71
00:03:19.039 --> 00:03:23.240
<v Speaker 2>a unified cloud subscription service. It bundles together the office

72
00:03:23.240 --> 00:03:27.360
<v Speaker 2>apps we know, but also newer things like Teams, includes Windows,

73
00:03:27.400 --> 00:03:31.280
<v Speaker 2>the operating system, and a whole sophisticated security layer. It's

74
00:03:31.280 --> 00:03:34.879
<v Speaker 2>all designed to boost productivity, make collaboration easier, and keep

75
00:03:34.879 --> 00:03:37.479
<v Speaker 2>things secure across all sorts of devices for any size

76
00:03:37.520 --> 00:03:38.120
<v Speaker 2>of organization.

77
00:03:38.639 --> 00:03:41.400
<v Speaker 1>And they have different subscription types for those different sizes.

78
00:03:41.400 --> 00:03:44.199
<v Speaker 2>Absolutely, they slice the market pretty logically. You got M

79
00:03:44.240 --> 00:03:46.919
<v Speaker 2>three sixty five Home for individuals and families, M three

80
00:03:46.960 --> 00:03:50.680
<v Speaker 2>sixty five Education for schools, M three sixty five for business,

81
00:03:50.680 --> 00:03:53.919
<v Speaker 2>which usually aims at smaller companies saved to three hundred people,

82
00:03:54.240 --> 00:03:56.639
<v Speaker 2>and then M three sixty five Enterprise. That's for the

83
00:03:56.639 --> 00:04:00.560
<v Speaker 2>big players who need the really robust security, compliance features,

84
00:04:01.000 --> 00:04:02.560
<v Speaker 2>advance threat prevention, that kind of thing.

85
00:04:02.759 --> 00:04:07.080
<v Speaker 1>Okay, let's shift focus to the user experience, productivity, collaboration,

86
00:04:07.319 --> 00:04:10.039
<v Speaker 1>managing work. It's not just about opening word anymore, is it.

87
00:04:10.039 --> 00:04:13.560
<v Speaker 1>It feels much more connected, almost AI driven totally.

88
00:04:13.439 --> 00:04:17.560
<v Speaker 2>The classic tools Word, Excel, PowerPoint. They're now packed with

89
00:04:17.639 --> 00:04:22.000
<v Speaker 2>AI features to help creativity. Think about Microsoft Editor checking

90
00:04:22.040 --> 00:04:26.480
<v Speaker 2>your grammar as you type, or presenter coach in PowerPoint

91
00:04:26.560 --> 00:04:29.839
<v Speaker 2>giving you feedback on your rehearsal. These aren't just static tools.

92
00:04:30.120 --> 00:04:32.480
<v Speaker 2>They have intelligence built in to help you work faster

93
00:04:32.560 --> 00:04:32.959
<v Speaker 2>and smarter.

94
00:04:33.240 --> 00:04:35.800
<v Speaker 1>Now, one thing that often comes up is organizing work.

95
00:04:36.319 --> 00:04:40.600
<v Speaker 1>Microsoft has several tools Project Planner to do even bookings.

96
00:04:41.199 --> 00:04:43.199
<v Speaker 1>Why so many? How do you know which one to use?

97
00:04:43.519 --> 00:04:46.240
<v Speaker 2>That's a really common and important question. It really is

98
00:04:46.240 --> 00:04:49.160
<v Speaker 2>about using the right tool for the right job. So

99
00:04:49.439 --> 00:04:52.839
<v Speaker 2>Microsoft Project that's your heavy hitter for complex projects, things

100
00:04:52.879 --> 00:04:57.040
<v Speaker 2>with dependencies, critical path scheduling, think big construction projects or

101
00:04:57.120 --> 00:04:58.160
<v Speaker 2>major product launches.

102
00:04:58.240 --> 00:04:59.839
<v Speaker 1>Okay, the really complex stuff.

103
00:05:00.000 --> 00:05:03.759
<v Speaker 2>That's right then Microsoft Planner. That's much more visual, collaborative,

104
00:05:04.040 --> 00:05:07.439
<v Speaker 2>think simple boards, dragging tasks around. It's great for smaller

105
00:05:07.439 --> 00:05:09.600
<v Speaker 2>team projects where you just need to see who's doing what.

106
00:05:09.800 --> 00:05:13.079
<v Speaker 1>And for just yourself keeping track of your own tasks.

107
00:05:13.360 --> 00:05:17.079
<v Speaker 2>That's Microsoft to do. It's your personal smart task list

108
00:05:17.439 --> 00:05:19.319
<v Speaker 2>and the nice thing is it syncs up with Outlook,

109
00:05:19.360 --> 00:05:22.360
<v Speaker 2>emails and tasks assigned to you in Planner. And lastly,

110
00:05:22.600 --> 00:05:26.480
<v Speaker 2>Microsoft Bookings is purely for scheduling appointments with people outside

111
00:05:26.519 --> 00:05:30.560
<v Speaker 2>your organization. It checks staff availability, integrates with Outlook calendars

112
00:05:30.560 --> 00:05:31.439
<v Speaker 2>to avoid clashes.

113
00:05:31.600 --> 00:05:34.160
<v Speaker 1>Makes sense, And the place where all this collaboration tends

114
00:05:34.160 --> 00:05:37.040
<v Speaker 1>to happen now is, of course, Microsoft Teams.

115
00:05:37.319 --> 00:05:42.240
<v Speaker 2>Teams is definitely the central hub. It pulls together chat, meetings, calls,

116
00:05:42.560 --> 00:05:45.000
<v Speaker 2>and file sharing and a key point. Those files you

117
00:05:45.079 --> 00:05:48.800
<v Speaker 2>share in Teams channels, they're actually stored securely in SharePoint

118
00:05:48.839 --> 00:05:50.839
<v Speaker 2>on the back end, so you get all the robust

119
00:05:50.920 --> 00:05:54.800
<v Speaker 2>version history and management capabilities of SharePoint behind the scenes

120
00:05:54.879 --> 00:05:55.399
<v Speaker 2>and looking.

121
00:05:55.240 --> 00:06:00.800
<v Speaker 1>At broader workplace challenges things like burnout, too many meetings information.

122
00:06:01.399 --> 00:06:05.399
<v Speaker 1>Microsoft has introduced this thing called the Employee Experience Platform VIVA.

123
00:06:05.600 --> 00:06:08.399
<v Speaker 2>Yeah, Viva is Microsoft kind of acknowledging that just being

124
00:06:08.439 --> 00:06:11.399
<v Speaker 2>productive isn't enough. You need to empower people. It's built

125
00:06:11.439 --> 00:06:14.480
<v Speaker 2>as modules inside Teams. Viva Connections is like your company's

126
00:06:14.519 --> 00:06:18.839
<v Speaker 2>front door in team's personalized news resources company branding. Viva

127
00:06:18.879 --> 00:06:22.839
<v Speaker 2>Topics uses AI to automatically surface knowledge and find experts.

128
00:06:23.639 --> 00:06:26.439
<v Speaker 2>So if you see an unfamiliar acronym or project name,

129
00:06:26.839 --> 00:06:30.079
<v Speaker 2>Topics might pop up a little card explaining it right there.

130
00:06:30.079 --> 00:06:30.759
<v Speaker 2>In your workflow.

131
00:06:31.319 --> 00:06:33.720
<v Speaker 1>I think Viva Insights is probably the one getting the

132
00:06:33.759 --> 00:06:35.839
<v Speaker 1>most attention right now, maybe the most needed.

133
00:06:35.959 --> 00:06:41.040
<v Speaker 2>I'd agree. Insights gives you data driven but privacy protected recommendations.

134
00:06:41.519 --> 00:06:43.519
<v Speaker 2>It can help you see if you're constantly working late,

135
00:06:43.839 --> 00:06:45.839
<v Speaker 2>or if your calendar is just jammed with back to

136
00:06:45.839 --> 00:06:49.160
<v Speaker 2>back meetings. It's about using data to improve well being

137
00:06:49.439 --> 00:06:52.439
<v Speaker 2>and spot potential burnout. Definitely not about spying on people.

138
00:06:52.959 --> 00:06:55.800
<v Speaker 2>And finally, Viva Learning brings together all your company's training

139
00:06:55.839 --> 00:06:59.360
<v Speaker 2>resources and external libraries into one place in teams.

140
00:07:00.000 --> 00:07:03.920
<v Speaker 1>Okay, that naturally leads us into security. If productivity is

141
00:07:03.959 --> 00:07:06.319
<v Speaker 1>the engine, security has got to be the chassis, the

142
00:07:06.360 --> 00:07:09.160
<v Speaker 1>frame holding it all together. Let's start with the basic

143
00:07:09.199 --> 00:07:11.759
<v Speaker 1>goals the CIA triad.

144
00:07:11.600 --> 00:07:17.519
<v Speaker 2>Right, confidentiality, integrity, and availability. Confidentiality is about keeping secret

145
00:07:17.600 --> 00:07:22.199
<v Speaker 2>secret preventing unauthorized access to data. Integrity means making sure

146
00:07:22.240 --> 00:07:24.720
<v Speaker 2>the data is accurate and hasn't been messed with, and

147
00:07:24.800 --> 00:07:27.560
<v Speaker 2>availability is simply ensuring that people can access the data

148
00:07:27.600 --> 00:07:30.360
<v Speaker 2>when they need to. Almost every cyber attack is trying

149
00:07:30.399 --> 00:07:31.879
<v Speaker 2>to undermine one or more of those.

150
00:07:32.319 --> 00:07:34.800
<v Speaker 1>Now, when you move to M three sixty five, probably

151
00:07:34.920 --> 00:07:37.600
<v Speaker 1>the single most critical concept people need to get is

152
00:07:37.680 --> 00:07:41.600
<v Speaker 1>shared responsibility. Microsoft doesn't just take over all your security worries.

153
00:07:41.639 --> 00:07:44.560
<v Speaker 2>Absolutely vital remember that service deck because mfree sixty five

154
00:07:44.600 --> 00:07:47.720
<v Speaker 2>is mostly SaaS Microsoft handles the security of the cloud,

155
00:07:47.920 --> 00:07:51.439
<v Speaker 2>the physical buildings, the hardware, the network controls, but the customer,

156
00:07:52.279 --> 00:07:54.839
<v Speaker 2>you are still responsible for security in the cloud. That

157
00:07:54.879 --> 00:07:59.360
<v Speaker 2>means your data, your endpoints, laptop's phones, and critically managing

158
00:07:59.399 --> 00:08:02.279
<v Speaker 2>who has exis identity and access management.

159
00:08:01.879 --> 00:08:03.920
<v Speaker 1>And to protect the parts you're responsible for. M three

160
00:08:03.959 --> 00:08:07.240
<v Speaker 1>sixty five uses a couple of key architectural ideas. First

161
00:08:07.279 --> 00:08:08.759
<v Speaker 1>one is defense in depth.

162
00:08:09.000 --> 00:08:11.079
<v Speaker 2>Yeah, think of it like layers of an onion or

163
00:08:11.079 --> 00:08:14.879
<v Speaker 2>a castle. You've got multiple layers of security controls physical

164
00:08:14.920 --> 00:08:18.480
<v Speaker 2>security at the data center, then network firewalls, then controls

165
00:08:18.480 --> 00:08:21.879
<v Speaker 2>on the servers, then application security, then finally protecting the

166
00:08:21.959 --> 00:08:25.639
<v Speaker 2>data itself. The idea is if one layer fails, the

167
00:08:25.680 --> 00:08:27.120
<v Speaker 2>next one might catch the threat.

168
00:08:27.240 --> 00:08:30.480
<v Speaker 1>And what's really shifted is the perimeter. With people working

169
00:08:30.560 --> 00:08:34.639
<v Speaker 1>from home using their own devices, bid the old idea

170
00:08:34.679 --> 00:08:37.679
<v Speaker 1>of a secure network boundary the firewall, it's just not

171
00:08:37.759 --> 00:08:38.440
<v Speaker 1>the main thing.

172
00:08:38.320 --> 00:08:42.120
<v Speaker 2>Anymore, exactly right. The perimeter is moved today. The primary

173
00:08:42.159 --> 00:08:45.759
<v Speaker 2>security perimeter is the identity of the user. Can you

174
00:08:45.840 --> 00:08:48.720
<v Speaker 2>reliably prove who the user is, what device they're using,

175
00:08:48.759 --> 00:08:51.320
<v Speaker 2>where they are. If you can verify those things, you

176
00:08:51.360 --> 00:08:53.919
<v Speaker 2>have a basis for granting access no matter if they're

177
00:08:53.919 --> 00:08:56.120
<v Speaker 2>inside or outside the old office network.

178
00:08:55.840 --> 00:08:58.519
<v Speaker 1>Which leads us straight to the core security philosophy underpinning

179
00:08:58.559 --> 00:09:01.600
<v Speaker 1>M three sixty five zero row trust. What's the main

180
00:09:01.639 --> 00:09:02.320
<v Speaker 1>idea there?

181
00:09:02.480 --> 00:09:05.919
<v Speaker 2>The mantra is simple, never trust, Always verify, or maybe

182
00:09:05.960 --> 00:09:09.039
<v Speaker 2>trust no one. Verify everything. Even if someone is already

183
00:09:09.080 --> 00:09:11.639
<v Speaker 2>logged into the network. You don't automatically trust them, you

184
00:09:11.720 --> 00:09:15.559
<v Speaker 2>constantly verify. Zero trust is built on three main principles.

185
00:09:15.799 --> 00:09:17.320
<v Speaker 1>Okay, let's quickly touch on those.

186
00:09:17.360 --> 00:09:21.559
<v Speaker 2>First, verify explicitly, always authenticate and authorize based on all

187
00:09:21.559 --> 00:09:26.600
<v Speaker 2>available data points user identity, location, device, health, the service

188
00:09:26.639 --> 00:09:30.159
<v Speaker 2>they're trying to reach, data classification, and so on. Second, Second,

189
00:09:30.480 --> 00:09:34.679
<v Speaker 2>use least privileged access. Get people only the minimum permissions

190
00:09:34.679 --> 00:09:36.519
<v Speaker 2>they need to do their job and only for the

191
00:09:36.559 --> 00:09:40.000
<v Speaker 2>time they need it. Think just in time JIT access

192
00:09:40.240 --> 00:09:44.840
<v Speaker 2>or just enough administration JEA. And Third, third, assume breach.

193
00:09:45.120 --> 00:09:48.159
<v Speaker 2>Don't assume your network is secure. Design your security assuming

194
00:09:48.200 --> 00:09:51.440
<v Speaker 2>attackers are already inside or will get inside. This means

195
00:09:51.440 --> 00:09:55.679
<v Speaker 2>segmenting networks, encrypting data, using analytics to spot anomalies quickly,

196
00:09:55.879 --> 00:09:57.120
<v Speaker 2>and being ready to respond.

197
00:09:57.279 --> 00:09:59.600
<v Speaker 1>But doesn't all that verification slow things down? How do

198
00:09:59.600 --> 00:10:01.960
<v Speaker 1>you make it or trust practical without frustrating users?

199
00:10:02.279 --> 00:10:05.639
<v Speaker 2>Ah, that's where automation is key, specifically through something called

200
00:10:05.720 --> 00:10:10.720
<v Speaker 2>conditional access policies. These were essentially if then rules. If

201
00:10:10.720 --> 00:10:15.200
<v Speaker 2>a user meets certain conditions like known device, secure location,

202
00:10:15.759 --> 00:10:19.039
<v Speaker 2>then grant access, but if they try to access sensitive

203
00:10:19.120 --> 00:10:22.679
<v Speaker 2>data from say an unknown network on an unmanaged device,

204
00:10:23.279 --> 00:10:27.799
<v Speaker 2>then block access or require multi factor authentication. It automates

205
00:10:27.799 --> 00:10:30.600
<v Speaker 2>the verification, making it seamless when things are normal, but

206
00:10:30.679 --> 00:10:32.240
<v Speaker 2>stepping in when risk increases.

207
00:10:32.399 --> 00:10:36.000
<v Speaker 1>Got it, And to actually implement all this protection, Microsoft

208
00:10:36.000 --> 00:10:39.399
<v Speaker 1>has an integrated suite called Microsoft three sixty five Defender.

209
00:10:39.559 --> 00:10:42.120
<v Speaker 2>Yeah, Defender isn't just one product, It's a suite design

210
00:10:42.200 --> 00:10:45.919
<v Speaker 2>to work together, coordinating how threats are detected, prevented, investigated

211
00:10:45.960 --> 00:10:48.919
<v Speaker 2>and responded to across your whole environment. You've got Defender

212
00:10:48.960 --> 00:10:51.440
<v Speaker 2>Forry Identity, which looks at your active directory signals for

213
00:10:51.480 --> 00:10:54.519
<v Speaker 2>signs of compromised accounts or insider threats. Okay, Defender for

214
00:10:54.519 --> 00:10:57.159
<v Speaker 2>Office three sixty five protects against threats coming through email

215
00:10:57.320 --> 00:11:00.360
<v Speaker 2>like phishing or malicious links shared in teams or shared point.

216
00:11:00.559 --> 00:11:04.799
<v Speaker 2>Defender for endpoint lives on your device's laptops servers, providing antivirus,

217
00:11:04.840 --> 00:11:07.200
<v Speaker 2>threat detection and automated investigation.

218
00:11:07.320 --> 00:11:10.240
<v Speaker 1>Right there, and it goes beyond just the Microsoft stuff,

219
00:11:10.279 --> 00:11:10.679
<v Speaker 1>doesn't it?

220
00:11:10.799 --> 00:11:14.120
<v Speaker 2>Yes? Critically. Defender for cloud apps is what's known as

221
00:11:14.120 --> 00:11:18.159
<v Speaker 2>a CASB, a cloud access security broker. It gives you

222
00:11:18.279 --> 00:11:22.360
<v Speaker 2>visibility and control over all the cloud apps your organization uses,

223
00:11:22.600 --> 00:11:26.159
<v Speaker 2>whether they're from Microsoft or other providers like Salesforce or Box.

224
00:11:26.519 --> 00:11:29.600
<v Speaker 2>It helps manage risk across your entire sauce landscape.

225
00:11:29.720 --> 00:11:32.639
<v Speaker 1>And just quickly, let's define the two core identity terms,

226
00:11:32.799 --> 00:11:34.679
<v Speaker 1>authentication and authorization.

227
00:11:34.840 --> 00:11:39.720
<v Speaker 2>Sure authentication author is proving who you are, usually user

228
00:11:39.799 --> 00:11:43.799
<v Speaker 2>name and password, but ideally more authorization auth Z is

229
00:11:43.840 --> 00:11:46.039
<v Speaker 2>figuring out what you're allowed to do. Once you've proven

230
00:11:46.080 --> 00:11:48.799
<v Speaker 2>who you are, what files you can see, what actions

231
00:11:48.799 --> 00:11:52.360
<v Speaker 2>you can take. And for strong authentication, multi factor authentication

232
00:11:52.519 --> 00:11:55.559
<v Speaker 2>MFA is essential. Something you know password, something you have

233
00:11:55.639 --> 00:11:59.240
<v Speaker 2>phone apps, security key, or something you are fingerprint face

234
00:11:59.240 --> 00:12:00.200
<v Speaker 2>scam okay.

235
00:12:00.200 --> 00:12:04.720
<v Speaker 1>Final section management operations compliance managing all the devices connecting

236
00:12:04.759 --> 00:12:08.279
<v Speaker 1>to m through sixty five, Windows, Macios, Android, personal devices.

237
00:12:08.279 --> 00:12:09.320
<v Speaker 1>That sounds like a headache.

238
00:12:09.399 --> 00:12:12.840
<v Speaker 2>It definitely can be without the right tools. That's where

239
00:12:12.879 --> 00:12:16.639
<v Speaker 2>Microsoft Endpoint Manager or MEM comes in. It's a unified

240
00:12:16.679 --> 00:12:20.960
<v Speaker 2>platform to manage all these different endpoints within MEM for

241
00:12:21.039 --> 00:12:25.320
<v Speaker 2>managing mobile devices, specifically MDM, you generally have two main

242
00:12:25.360 --> 00:12:28.919
<v Speaker 2>options built into M three sixty five. There's Basic Mobility

243
00:12:28.919 --> 00:12:30.480
<v Speaker 2>and Security, which offers.

244
00:12:30.159 --> 00:12:32.320
<v Speaker 1>Core controls and more powerful option.

245
00:12:32.240 --> 00:12:35.000
<v Speaker 2>And then there's Microsoft in Tune that's really the gold standard.

246
00:12:35.080 --> 00:12:38.039
<v Speaker 2>It gives you much more granular control over both the

247
00:12:38.120 --> 00:12:41.759
<v Speaker 2>devices MDM and the applications on them, which is called

248
00:12:41.799 --> 00:12:44.200
<v Speaker 2>Mobile Application Management or MDM.

249
00:12:44.240 --> 00:12:47.440
<v Speaker 1>And these management policies they tie back into zero trust

250
00:12:47.440 --> 00:12:51.360
<v Speaker 1>and conditional access right checking if a device is compliant exactly.

251
00:12:51.639 --> 00:12:54.559
<v Speaker 2>Organizations set up policies through in tune, things like requiring

252
00:12:54.600 --> 00:12:57.399
<v Speaker 2>device encryption, setting password rules, making sure the OS is

253
00:12:57.440 --> 00:12:59.879
<v Speaker 2>up to date. Then conditional access policies can check that

254
00:13:00.000 --> 00:13:03.639
<v Speaker 2>device compliance status before granting access. If your phone doesn't

255
00:13:03.679 --> 00:13:05.799
<v Speaker 2>meet the security requirements, it might not be allowed to

256
00:13:05.840 --> 00:13:07.440
<v Speaker 2>access company email for example.

257
00:13:07.559 --> 00:13:10.120
<v Speaker 1>Okay, and what about keeping everything up to date? We

258
00:13:10.200 --> 00:13:13.039
<v Speaker 1>hear about Windows as a Service wass.

259
00:13:12.799 --> 00:13:15.759
<v Speaker 2>WES basically means Windows isn't a product you buy once

260
00:13:15.840 --> 00:13:19.039
<v Speaker 2>and used for years. It's a service that's continually updated.

261
00:13:19.399 --> 00:13:22.000
<v Speaker 2>You get big feature updates, usually twice a year, that

262
00:13:22.080 --> 00:13:25.120
<v Speaker 2>add new capabilities, and then you get smaller, monthly quality

263
00:13:25.159 --> 00:13:28.679
<v Speaker 2>updates that are mostly about security patches and reliability fixes.

264
00:13:29.279 --> 00:13:33.159
<v Speaker 2>The Microsoft three sixty five apps, Word, Excel, et cetera

265
00:13:33.399 --> 00:13:37.120
<v Speaker 2>are also updated frequently, often monthly, using a technology called

266
00:13:37.159 --> 00:13:40.320
<v Speaker 2>click to run that makes updates pretty seamless. It's an

267
00:13:40.320 --> 00:13:41.639
<v Speaker 2>evergreen approach.

268
00:13:41.759 --> 00:13:45.240
<v Speaker 1>So constant change. And for the IT admins managing all this,

269
00:13:45.360 --> 00:13:48.000
<v Speaker 1>their main control panel is the Microsoft three sixty five

270
00:13:48.080 --> 00:13:48.759
<v Speaker 1>Admin Center.

271
00:13:48.879 --> 00:13:53.279
<v Speaker 2>That's the central place yes for managing user accounts, licenses, subscriptions, billing.

272
00:13:53.840 --> 00:13:56.559
<v Speaker 2>It's also where they can access various reports, including things

273
00:13:56.600 --> 00:13:59.080
<v Speaker 2>like activity reports showing how people are using the tools,

274
00:13:59.320 --> 00:14:01.480
<v Speaker 2>or linking out to things like Viva Insights for those

275
00:14:01.480 --> 00:14:03.360
<v Speaker 2>deeper productivity and well being metrics.

276
00:14:03.600 --> 00:14:08.159
<v Speaker 1>Last piece, compliance and trust. How does Microsoft help organizations

277
00:14:08.159 --> 00:14:12.360
<v Speaker 1>with their own due diligence, proving they meet regulations managing privacy.

278
00:14:11.919 --> 00:14:13.600
<v Speaker 2>Well, The first place to look is the Service Trust

279
00:14:13.679 --> 00:14:17.279
<v Speaker 2>Portal or STP. That's Microsoft's public site where they share

280
00:14:17.320 --> 00:14:21.639
<v Speaker 2>all their own compliance certifications, audit reports, and detailed information

281
00:14:21.720 --> 00:14:25.559
<v Speaker 2>about their security and privacy practices. It helps you understand

282
00:14:25.639 --> 00:14:28.759
<v Speaker 2>Microsoft side of the shared responsibility model.

283
00:14:28.519 --> 00:14:30.840
<v Speaker 1>And for the customer side of compliance, things like where

284
00:14:30.879 --> 00:14:31.759
<v Speaker 1>data is stored.

285
00:14:32.120 --> 00:14:36.200
<v Speaker 2>Key issues there are data sovereignty and data residency, knowing

286
00:14:36.279 --> 00:14:39.080
<v Speaker 2>physically where your data is stored because different countries have

287
00:14:39.120 --> 00:14:42.840
<v Speaker 2>different laws governing data privacy and access. M three sixty

288
00:14:42.919 --> 00:14:46.519
<v Speaker 2>five offers options control data residency for core services in

289
00:14:46.559 --> 00:14:48.000
<v Speaker 2>specific regions.

290
00:14:47.799 --> 00:14:51.679
<v Speaker 1>And dealing with individual privacy requests like under GDPR. That

291
00:14:51.799 --> 00:14:53.279
<v Speaker 1>must be a big task.

292
00:14:53.039 --> 00:14:56.080
<v Speaker 2>Now it is, and that's where Microsoft Priva fits in.

293
00:14:56.279 --> 00:14:58.879
<v Speaker 2>It's a newer set of tools designed to help organizations

294
00:14:58.919 --> 00:15:02.440
<v Speaker 2>manage privacy risks more automatically. You could help discover where

295
00:15:02.480 --> 00:15:06.679
<v Speaker 2>personal data resides, manage consent, and automate fulfilling data subject

296
00:15:06.720 --> 00:15:09.639
<v Speaker 2>requests like request for access or deletion, which could be

297
00:15:09.679 --> 00:15:10.840
<v Speaker 2>a huge manual effort.

298
00:15:10.840 --> 00:15:13.720
<v Speaker 1>Otherwise, Okay, let's try and wrap this huge deep dive

299
00:15:13.799 --> 00:15:17.519
<v Speaker 1>up Microsoft three sixty five. Yea clearly way more than

300
00:15:17.600 --> 00:15:21.679
<v Speaker 1>just apps. It's this massive integrated platform changing how companies

301
00:15:21.720 --> 00:15:25.919
<v Speaker 1>budget for it, that CAPEX to OPEC shift and fundamentally

302
00:15:26.000 --> 00:15:28.600
<v Speaker 1>changing how they need to think about security absolutely.

303
00:15:28.960 --> 00:15:30.960
<v Speaker 2>If there are two big takeaways for you, the listener,

304
00:15:31.000 --> 00:15:34.399
<v Speaker 2>it's probably these. First, identity is the new control plane,

305
00:15:34.440 --> 00:15:37.480
<v Speaker 2>the new perimeter, so embracing a zero trust mindset isn't

306
00:15:37.480 --> 00:15:41.080
<v Speaker 2>really optional anymore. And second, you absolutely have to understand

307
00:15:41.120 --> 00:15:44.480
<v Speaker 2>and own your part of the shared responsibility model. Microsoft

308
00:15:44.480 --> 00:15:46.679
<v Speaker 2>provides powerful tools, but if you don't configure them correctly,

309
00:15:46.799 --> 00:15:51.080
<v Speaker 2>manage identities, properly, apply the right policies, the security responsibility

310
00:15:51.080 --> 00:15:53.240
<v Speaker 2>and the potential fallout lands squarely on you.

311
00:15:53.320 --> 00:15:54.840
<v Speaker 1>All right, So here's the final thought we want to

312
00:15:54.879 --> 00:15:57.440
<v Speaker 1>leave you with. M three sixty five is described as

313
00:15:57.440 --> 00:16:01.960
<v Speaker 1>an evergreen product. It's constantly changing, always improving, rolling out

314
00:16:02.000 --> 00:16:05.679
<v Speaker 1>new features, sometimes in private preview, then public preview, then

315
00:16:05.720 --> 00:16:10.399
<v Speaker 1>finally general availability. So, given this constant stream of updates

316
00:16:10.399 --> 00:16:14.080
<v Speaker 1>and new tools, what's the single most important organizational process

317
00:16:14.080 --> 00:16:17.039
<v Speaker 1>you should focus on getting right? First? Think about what

318
00:16:17.120 --> 00:16:19.559
<v Speaker 1>you need to make sure your teams can actually use

319
00:16:19.600 --> 00:16:23.200
<v Speaker 1>these new features safely and effectively without just getting overwhelmed

320
00:16:23.200 --> 00:16:24.000
<v Speaker 1>by the pace of change.

321
00:16:24.039 --> 00:16:27.000
<v Speaker 2>It's a good question to ponder because if your people

322
00:16:27.039 --> 00:16:31.159
<v Speaker 2>can't learn about and adopt the new capabilities securely, well,

323
00:16:31.200 --> 00:16:33.360
<v Speaker 2>then you're not really getting the full value out of

324
00:16:33.360 --> 00:16:36.320
<v Speaker 2>the platform, are you. It points towards needing a solid

325
00:16:36.360 --> 00:16:39.279
<v Speaker 2>process for continuous learning and change management.

326
00:16:39.480 --> 00:16:41.559
<v Speaker 1>Definitely something to think about. We'll catch you next time

327
00:16:41.759 --> 00:16:42.519
<v Speaker 1>on the Deep Dive