WEBVTT

1
00:00:00.160 --> 00:00:03.640
<v Speaker 1>Welcome to another deep dive. Today. We're going deep into

2
00:00:03.759 --> 00:00:07.240
<v Speaker 1>Azure management. That's fun it is. We're going to be

3
00:00:07.240 --> 00:00:11.640
<v Speaker 1>pulling insights from inside Azure Management by Pete Zerger, Kevin Green,

4
00:00:12.000 --> 00:00:17.440
<v Speaker 1>and Bert Walters. It's basically like your guide to navigating

5
00:00:17.480 --> 00:00:20.519
<v Speaker 1>Microsoft's cloud platforms. So if you're looking to like step

6
00:00:20.600 --> 00:00:22.519
<v Speaker 1>up your Azure game, you're in the right place.

7
00:00:24.199 --> 00:00:27.879
<v Speaker 2>You know. It's about more than just like knowing the tech, right,

8
00:00:27.920 --> 00:00:30.719
<v Speaker 2>It's got to be a framework for success in the cloud,

9
00:00:31.000 --> 00:00:31.879
<v Speaker 2>solid foundation.

10
00:00:32.079 --> 00:00:35.679
<v Speaker 1>Yeah, okay, So let's talk about governance and Azure. Okay,

11
00:00:35.719 --> 00:00:37.600
<v Speaker 1>I get that it's important, but like, what are we

12
00:00:37.640 --> 00:00:39.479
<v Speaker 1>really talking about here. It's not like we're setting up

13
00:00:39.479 --> 00:00:40.359
<v Speaker 1>a government.

14
00:00:40.359 --> 00:00:42.320
<v Speaker 2>Well not quite think of it. More like, you know,

15
00:00:43.159 --> 00:00:45.560
<v Speaker 2>establishing the rules of the road, right, Okay, For your

16
00:00:45.600 --> 00:00:51.679
<v Speaker 2>Azure environment, it's all about control and consistency across your subscriptions.

17
00:00:51.799 --> 00:00:53.200
<v Speaker 2>And that's where management groups come in.

18
00:00:53.320 --> 00:00:53.679
<v Speaker 1>Okay.

19
00:00:53.880 --> 00:00:56.520
<v Speaker 2>They're like the organizational folders of Azure. So let's say

20
00:00:56.679 --> 00:01:00.079
<v Speaker 2>you're a large organization, right, You've got multiple departments, Yeah,

21
00:01:00.200 --> 00:01:04.040
<v Speaker 2>them have their own Azure subscription. Management groups help you

22
00:01:04.079 --> 00:01:06.040
<v Speaker 2>bring order to the chaos, right.

23
00:01:05.879 --> 00:01:10.840
<v Speaker 1>So you can manage permissions and policies across all those

24
00:01:10.879 --> 00:01:13.480
<v Speaker 1>subscriptions from like a central point one hundred percent. That

25
00:01:13.519 --> 00:01:16.719
<v Speaker 1>makes sense, But how do you actually enforce those policies?

26
00:01:17.040 --> 00:01:20.280
<v Speaker 1>But stopping someone from just like ignoring the rules.

27
00:01:20.120 --> 00:01:22.480
<v Speaker 2>That's where ad your policy comes into play. Okay, it's

28
00:01:22.519 --> 00:01:25.959
<v Speaker 2>like having a virtual enforcer, right, making sure everyone's playing

29
00:01:26.000 --> 00:01:27.359
<v Speaker 2>by the rules that you define.

30
00:01:27.480 --> 00:01:30.599
<v Speaker 1>So it's not just about setting policies, it's about making

31
00:01:30.640 --> 00:01:35.680
<v Speaker 1>them stick. Yeah, okay, I'm intrigued. Tell me more about

32
00:01:35.719 --> 00:01:37.040
<v Speaker 1>how this enforcer works.

33
00:01:37.319 --> 00:01:41.680
<v Speaker 2>So ag your policy uses a variety of effects to

34
00:01:41.920 --> 00:01:47.000
<v Speaker 2>enforce compliance. Right. It can straight up deny non compliant resources,

35
00:01:48.359 --> 00:01:51.719
<v Speaker 2>essentially preventing, oh wow, them from even being created in

36
00:01:51.799 --> 00:01:55.879
<v Speaker 2>the first place. Or it can audit actions, keeping a

37
00:01:55.879 --> 00:01:57.879
<v Speaker 2>watchful eye and everything that's happening.

38
00:01:57.680 --> 00:02:00.760
<v Speaker 1>Logging any violations, right, so you can go back and review.

39
00:02:00.920 --> 00:02:03.920
<v Speaker 2>That's a good safety net, knowing that somebody's watching exactly.

40
00:02:04.079 --> 00:02:06.760
<v Speaker 2>You'll have a record of any policy preaches, what other

41
00:02:06.799 --> 00:02:08.000
<v Speaker 2>policy effects are.

42
00:02:07.879 --> 00:02:12.759
<v Speaker 1>There, so there's a pend or modify which automatically add okay,

43
00:02:12.919 --> 00:02:15.759
<v Speaker 1>or change resource configurations to align with your policies.

44
00:02:15.960 --> 00:02:17.039
<v Speaker 2>It's like an auto correct.

45
00:02:17.120 --> 00:02:19.759
<v Speaker 1>It's like an autocorrect for your Azure environment or your

46
00:02:19.759 --> 00:02:22.039
<v Speaker 1>Azure environment, making sure everything stays in line.

47
00:02:22.199 --> 00:02:22.680
<v Speaker 2>I like it.

48
00:02:22.719 --> 00:02:27.199
<v Speaker 1>And then there's deploy if note exists, which automatically deploys

49
00:02:27.240 --> 00:02:31.280
<v Speaker 1>resources if they're missing. Right, So guarantees consistency across your environment.

50
00:02:31.280 --> 00:02:34.560
<v Speaker 2>It's like a self healing system exactly. I remember the

51
00:02:34.560 --> 00:02:38.759
<v Speaker 2>authors of Inside Azure Management use this real world example

52
00:02:39.159 --> 00:02:43.840
<v Speaker 2>about preventing the creation of public facing storage accounts. That

53
00:02:43.919 --> 00:02:45.759
<v Speaker 2>seems like a crucial security measure.

54
00:02:45.840 --> 00:02:48.560
<v Speaker 1>It is. Think about it. You wouldn't leave your front

55
00:02:48.560 --> 00:02:51.719
<v Speaker 1>door wide open, right right, So same principle applies to

56
00:02:51.759 --> 00:02:55.560
<v Speaker 1>your cloud resources. You don't want sensitive data.

57
00:02:55.000 --> 00:02:57.400
<v Speaker 2>Exposed to the world, right as your policy gives you

58
00:02:57.439 --> 00:03:00.240
<v Speaker 2>that granular control to lock things down.

59
00:03:00.159 --> 00:03:04.159
<v Speaker 1>Makes perfect sense. So we've covered management groups and Azure policy.

60
00:03:04.960 --> 00:03:09.080
<v Speaker 1>What other tools can help us like lay this solid

61
00:03:09.120 --> 00:03:10.120
<v Speaker 1>governance foundation.

62
00:03:11.280 --> 00:03:15.599
<v Speaker 2>So for those who value consistency and automation, Azure blueprints

63
00:03:15.599 --> 00:03:20.039
<v Speaker 2>are a game changer. Okay, imagine them as prepackaged blueprints

64
00:03:20.080 --> 00:03:24.639
<v Speaker 2>for your Azure environments, right, Okay, So the combine policy definitions,

65
00:03:25.199 --> 00:03:30.599
<v Speaker 2>role based access control settings, and even ARM templates, allowing

66
00:03:30.639 --> 00:03:33.439
<v Speaker 2>you to deploy standardized environments with ease.

67
00:03:33.879 --> 00:03:36.719
<v Speaker 1>Okay, So I could create a blueprint for my development environment,

68
00:03:36.759 --> 00:03:41.520
<v Speaker 1>for example, and deploy it repeatedly, ensuring consistency across projects

69
00:03:41.599 --> 00:03:43.599
<v Speaker 1>one hundred percent. That would save a ton of time

70
00:03:43.599 --> 00:03:44.520
<v Speaker 1>and headaches exactly.

71
00:03:44.680 --> 00:03:48.479
<v Speaker 2>Yeah, blueprints help you maintain control and avoid configuration drift,

72
00:03:48.800 --> 00:03:51.479
<v Speaker 2>making sure your Azure environment stays in tiptop shape.

73
00:03:51.560 --> 00:03:54.319
<v Speaker 1>So we've laid a solid foundation with a governance, but

74
00:03:54.400 --> 00:03:56.840
<v Speaker 1>now we need visibility. Right, how do we know what's

75
00:03:56.879 --> 00:03:59.520
<v Speaker 1>going on in our environment? Are things running smoothly?

76
00:04:00.080 --> 00:04:03.199
<v Speaker 2>You need insights and that's where Azure monitor comes in.

77
00:04:03.240 --> 00:04:08.280
<v Speaker 2>It's your one stop shop for collecting and analyzing telemetry

78
00:04:08.400 --> 00:04:11.639
<v Speaker 2>data from your entire Azure environment. Think of it as

79
00:04:11.639 --> 00:04:15.719
<v Speaker 2>the central nervous system of your cloud infrastructure.

80
00:04:16.079 --> 00:04:19.279
<v Speaker 1>So it's like constantly collecting data about what's happening in Azure.

81
00:04:19.399 --> 00:04:21.720
<v Speaker 1>Exactly what kind of data are we talking about here?

82
00:04:21.759 --> 00:04:25.639
<v Speaker 2>So two main types, metrics and logs. Metrics are those

83
00:04:25.759 --> 00:04:29.279
<v Speaker 2>numerical data points. They give you a snapshot of your

84
00:04:29.360 --> 00:04:35.560
<v Speaker 2>resource performance, CPU usage, network traffic, disc io, things like that.

85
00:04:35.639 --> 00:04:37.120
<v Speaker 1>Okay, So like the vital sign.

86
00:04:36.959 --> 00:04:38.920
<v Speaker 2>It's like the vital signs of your Azure environment. Yeah,

87
00:04:38.959 --> 00:04:40.360
<v Speaker 2>giving you that real time pulse check.

88
00:04:40.560 --> 00:04:42.920
<v Speaker 1>Okay. So metrics tell us how things are performing.

89
00:04:43.240 --> 00:04:46.639
<v Speaker 2>Yep, what about logs? So logs provide a much deeper

90
00:04:46.720 --> 00:04:50.279
<v Speaker 2>level of detail. They record specific events and activities that

91
00:04:50.319 --> 00:04:54.959
<v Speaker 2>occur within your resources. So think user logins, API calls,

92
00:04:55.279 --> 00:04:59.000
<v Speaker 2>changes to configurations, all those behind the scenes events that

93
00:04:59.079 --> 00:05:01.879
<v Speaker 2>can help you trouble shoot issues and understand got it,

94
00:05:01.920 --> 00:05:03.519
<v Speaker 2>what's happening at a granular level.

95
00:05:03.560 --> 00:05:08.279
<v Speaker 1>Okay, So metrics give us the overview. Logs provide the like.

96
00:05:08.279 --> 00:05:09.319
<v Speaker 2>The granular details.

97
00:05:09.360 --> 00:05:13.519
<v Speaker 1>Granular details. But how does Azure monitor collect all this data?

98
00:05:13.600 --> 00:05:14.839
<v Speaker 1>Does it magically appear?

99
00:05:15.120 --> 00:05:16.800
<v Speaker 2>Not magic, but pretty close?

100
00:05:16.920 --> 00:05:17.319
<v Speaker 1>Okay?

101
00:05:17.439 --> 00:05:20.000
<v Speaker 2>So there are a few ways for virtual machines. We

102
00:05:20.040 --> 00:05:24.480
<v Speaker 2>have the Microsoft Monitoring Agent or MMA, which you can

103
00:05:24.480 --> 00:05:28.879
<v Speaker 2>install to collect logs in metrics directly from the operating systems.

104
00:05:29.199 --> 00:05:32.279
<v Speaker 2>And then there are Azure Diagnostic settings which allow you

105
00:05:32.360 --> 00:05:36.800
<v Speaker 2>to configure resources to send their logs in metrics directly

106
00:05:36.800 --> 00:05:37.639
<v Speaker 2>to Azure Monitor.

107
00:05:37.839 --> 00:05:40.839
<v Speaker 1>So we can set up these like diagnostic typelines to

108
00:05:41.000 --> 00:05:45.040
<v Speaker 1>stream data directly into Azure monitors. Sounds efficient? Is there

109
00:05:45.040 --> 00:05:47.959
<v Speaker 1>anything else we should know? Let me think about how

110
00:05:48.000 --> 00:05:49.040
<v Speaker 1>this data is collected.

111
00:05:49.279 --> 00:05:52.759
<v Speaker 2>One important tip from inside Azure management is to consider

112
00:05:54.759 --> 00:05:59.519
<v Speaker 2>archiving your activity logs to a log analytics workspace if

113
00:05:59.560 --> 00:06:03.800
<v Speaker 2>you need to retain them beyond the default ninety days. Okay, So,

114
00:06:03.920 --> 00:06:07.399
<v Speaker 2>activity logs track every action taken in your Azure subscriptions,

115
00:06:07.839 --> 00:06:13.120
<v Speaker 2>creating resources, deleting resources, changing configurations. Basically a complete audit

116
00:06:13.120 --> 00:06:14.399
<v Speaker 2>trail of everything that happens.

117
00:06:14.480 --> 00:06:18.120
<v Speaker 1>That's a gold mine of information for auditing and compliance.

118
00:06:18.279 --> 00:06:23.279
<v Speaker 1>Oh yeah, and for troubleshooting those who did what scenarios exactly.

119
00:06:23.360 --> 00:06:25.199
<v Speaker 1>So we're collecting all this data, but how do we

120
00:06:25.240 --> 00:06:25.959
<v Speaker 1>make sense of it?

121
00:06:26.240 --> 00:06:26.399
<v Speaker 2>Right?

122
00:06:26.439 --> 00:06:28.800
<v Speaker 1>I'm imagining a giant haystack of data.

123
00:06:28.879 --> 00:06:30.680
<v Speaker 2>That's where log analytics comes into play.

124
00:06:30.759 --> 00:06:31.000
<v Speaker 1>Okay.

125
00:06:31.160 --> 00:06:34.680
<v Speaker 2>It's a powerful tool within as your monitor that allows

126
00:06:34.720 --> 00:06:38.759
<v Speaker 2>you to analyze your data using the Cousto Query language

127
00:06:39.040 --> 00:06:43.319
<v Speaker 2>or KQL. It's surprisingly intuitive, even if you're not a

128
00:06:43.319 --> 00:06:44.439
<v Speaker 2>seasoned data scientist.

129
00:06:44.519 --> 00:06:47.959
<v Speaker 1>EQL sounds powerful, but is it user friendly? I'm not

130
00:06:48.000 --> 00:06:49.040
<v Speaker 1>exactly a coding Liz.

131
00:06:49.079 --> 00:06:52.120
<v Speaker 2>Don't worry. KQL is designed to be accessible. It uses

132
00:06:52.120 --> 00:06:54.720
<v Speaker 2>a simple command line interface, and there are tons of

133
00:06:54.759 --> 00:06:57.319
<v Speaker 2>resources available to help you learn the ropes. You can

134
00:06:57.399 --> 00:07:01.839
<v Speaker 2>query your logs, find specific events, identify patterns, and even

135
00:07:02.199 --> 00:07:06.720
<v Speaker 2>create custom dashboards to visualize your data in meaningful ways.

136
00:07:07.000 --> 00:07:10.000
<v Speaker 1>So we can go beyond just looking at raw data

137
00:07:10.079 --> 00:07:14.600
<v Speaker 1>exactly and actually extract insights and intelligence from it one percent.

138
00:07:14.800 --> 00:07:17.480
<v Speaker 1>Pretty cool. What are some of the key insights we

139
00:07:17.519 --> 00:07:19.319
<v Speaker 1>can glean from all this data?

140
00:07:19.399 --> 00:07:22.120
<v Speaker 2>So as your monitor provides a bunch of different views

141
00:07:22.120 --> 00:07:25.040
<v Speaker 2>and insights, okay to help you understand what's happening in

142
00:07:25.079 --> 00:07:30.199
<v Speaker 2>your environment. Service Health gives you a global view of

143
00:07:30.319 --> 00:07:33.319
<v Speaker 2>the health of Azure services, so you know if there

144
00:07:33.319 --> 00:07:38.439
<v Speaker 2>are any widespread issues or planned maintenance activities that might

145
00:07:38.480 --> 00:07:39.600
<v Speaker 2>affect your resources.

146
00:07:39.680 --> 00:07:42.839
<v Speaker 1>That's crucial information, especially if you're relying on Azure for

147
00:07:42.920 --> 00:07:46.439
<v Speaker 1>like critical business operations. No one wants to be caught

148
00:07:46.439 --> 00:07:49.480
<v Speaker 1>off guard by an unexpected outage exactly.

149
00:07:50.160 --> 00:07:52.319
<v Speaker 2>And then there are workbooks which allow you to create

150
00:07:52.439 --> 00:07:57.040
<v Speaker 2>interactive reports with data pulled from various sources. So think

151
00:07:57.079 --> 00:08:00.360
<v Speaker 2>of them as customizable dashboards where you can visual your

152
00:08:00.439 --> 00:08:02.439
<v Speaker 2>data in a way that makes sense to you. You

153
00:08:02.480 --> 00:08:06.199
<v Speaker 2>want to track CPU usage across all your virtual machines

154
00:08:06.439 --> 00:08:10.279
<v Speaker 2>in a single chart, no problem, Wow, need to see

155
00:08:10.279 --> 00:08:14.439
<v Speaker 2>how your application performance correlates with network traffic?

156
00:08:14.639 --> 00:08:14.959
<v Speaker 1>Okay?

157
00:08:15.199 --> 00:08:16.680
<v Speaker 2>Workbooks to the rescue.

158
00:08:17.040 --> 00:08:19.680
<v Speaker 1>Okay, So workbooks sound like they offer a lot of

159
00:08:19.720 --> 00:08:24.920
<v Speaker 1>flexibility for tailoring the view to your specific needs. Are

160
00:08:24.959 --> 00:08:28.040
<v Speaker 1>there any other like pre built insights that as your

161
00:08:28.079 --> 00:08:29.000
<v Speaker 1>monitor provides.

162
00:08:30.000 --> 00:08:33.559
<v Speaker 2>If you're running web applications, application insights is your best friend.

163
00:08:34.279 --> 00:08:38.360
<v Speaker 2>It's designed specifically for monitoring the performance and user experience

164
00:08:38.399 --> 00:08:41.720
<v Speaker 2>of your web apps. You can track response times, error rates,

165
00:08:42.360 --> 00:08:46.519
<v Speaker 2>user behavior, and even dive into code level diagnostics. Wow,

166
00:08:46.600 --> 00:08:47.559
<v Speaker 2>to pinpoint issues.

167
00:08:47.679 --> 00:08:50.320
<v Speaker 1>So we can see not just how our apps are

168
00:08:50.360 --> 00:08:54.039
<v Speaker 1>performing like from a technical standpoint, but also how users

169
00:08:54.080 --> 00:08:57.840
<v Speaker 1>are experiencing them exactly. That's valuable information. It is for

170
00:08:57.960 --> 00:09:00.000
<v Speaker 1>optimizing user satisfaction absolutely.

171
00:09:00.279 --> 00:09:03.320
<v Speaker 2>And if you need in depth insights into your virtual machines,

172
00:09:03.639 --> 00:09:07.399
<v Speaker 2>virtual Machine Insights is the tool for you. It provides

173
00:09:07.480 --> 00:09:15.000
<v Speaker 2>granular visibility into VM performance, health dependencies, and even security posture. Wow,

174
00:09:15.240 --> 00:09:17.720
<v Speaker 2>it's like having X ray vision into your virtual machines.

175
00:09:17.840 --> 00:09:21.799
<v Speaker 2>It's like allowing you to diagnose issues and ensure optimal performance.

176
00:09:22.200 --> 00:09:25.360
<v Speaker 1>This is shaping up to be quite the powerhouse it is.

177
00:09:25.360 --> 00:09:29.480
<v Speaker 1>You have covered governance monitoring. What else is there to

178
00:09:29.600 --> 00:09:32.240
<v Speaker 1>explore in this Azure management universe?

179
00:09:32.519 --> 00:09:34.600
<v Speaker 2>Well, since you brought it up, let's talk about one

180
00:09:34.639 --> 00:09:36.679
<v Speaker 2>of my favorite topics, automation.

181
00:09:37.759 --> 00:09:39.000
<v Speaker 1>I knew you were going to say.

182
00:09:38.799 --> 00:09:39.679
<v Speaker 2>That you know you.

183
00:09:40.639 --> 00:09:43.600
<v Speaker 1>So we all have those repetitive tasks that eat up

184
00:09:43.600 --> 00:09:46.600
<v Speaker 1>our time. Oh yeah, and as your automation is here

185
00:09:46.600 --> 00:09:50.759
<v Speaker 1>to save the day, right, automating those everyday chores, freeing

186
00:09:50.919 --> 00:09:54.240
<v Speaker 1>us up to focus on more strategic work. Yeah okay,

187
00:09:54.240 --> 00:09:58.679
<v Speaker 1>but be honest, yeah, how much coding is involved here?

188
00:09:58.720 --> 00:10:01.000
<v Speaker 1>I'm more of a click and drag kind of person.

189
00:10:01.120 --> 00:10:04.600
<v Speaker 2>Don't worry, as your automation caters to all skill levels. Right. Okay,

190
00:10:04.759 --> 00:10:07.799
<v Speaker 2>you can leverage the power of PowerShell or Python scripting

191
00:10:07.840 --> 00:10:10.679
<v Speaker 2>if you're comfortable with code. Yeah, but for those who

192
00:10:10.759 --> 00:10:14.799
<v Speaker 2>prefer a visual approach, there are graphical run books. Okay,

193
00:10:14.879 --> 00:10:17.000
<v Speaker 2>so think of them as like drag and drop workflows

194
00:10:17.399 --> 00:10:21.480
<v Speaker 2>where you visually connect activities and define logic without writing

195
00:10:21.480 --> 00:10:22.679
<v Speaker 2>a single line of code.

196
00:10:22.759 --> 00:10:25.480
<v Speaker 1>That sounds much more my space, right. What are some

197
00:10:25.559 --> 00:10:28.919
<v Speaker 1>examples of tasks we can automate with these run books?

198
00:10:29.639 --> 00:10:34.519
<v Speaker 2>The possibilities are endless. You can automate server patching, software deployments,

199
00:10:35.080 --> 00:10:39.360
<v Speaker 2>database backups, user provisioning, so much more. It's like having

200
00:10:39.759 --> 00:10:43.279
<v Speaker 2>a virtual IT assistant who never sleeps, never takes a vacation.

201
00:10:43.519 --> 00:10:45.960
<v Speaker 1>Okay, I'm sold, right. What if we have a mix

202
00:10:46.240 --> 00:10:49.840
<v Speaker 1>of cloud and on prem resources. Right can as your

203
00:10:49.879 --> 00:10:53.120
<v Speaker 1>automation handle those like hybrid scenario?

204
00:10:53.240 --> 00:10:57.120
<v Speaker 2>Absolutely, as your automation extends its reach beyond the cloud

205
00:10:57.399 --> 00:11:00.440
<v Speaker 2>okay with hybrid workers right, Okay, These ages and act

206
00:11:00.480 --> 00:11:05.039
<v Speaker 2>as bridges between Azure automation and your on premises environments,

207
00:11:05.240 --> 00:11:08.519
<v Speaker 2>allowing you to manage and automate tasks on those servers. Okay,

208
00:11:08.720 --> 00:11:10.720
<v Speaker 2>they haven't yet made the jump to the cloud, so.

209
00:11:10.639 --> 00:11:14.960
<v Speaker 1>We can have a single automation platform that spans our

210
00:11:15.159 --> 00:11:19.519
<v Speaker 1>entire like it landscape one percent. That's pretty powerful is

211
00:11:19.879 --> 00:11:22.840
<v Speaker 1>and if you want to trigger automations from external systems

212
00:11:22.919 --> 00:11:26.440
<v Speaker 1>or applications, webhooks come into play, right Yeah. They provide

213
00:11:26.440 --> 00:11:30.399
<v Speaker 1>a way for those external systems to communicate with Azure automation,

214
00:11:30.600 --> 00:11:35.720
<v Speaker 1>kicking off run books whenever a specific event occurs. That

215
00:11:35.799 --> 00:11:39.759
<v Speaker 1>opens up even more automation possibilities. Oh yeah, we could

216
00:11:39.840 --> 00:11:43.360
<v Speaker 1>trigger a run book to provision new resources based on

217
00:11:43.440 --> 00:11:45.200
<v Speaker 1>an event in our monitoring system.

218
00:11:45.919 --> 00:11:47.240
<v Speaker 2>It's a really powerful feature.

219
00:11:47.360 --> 00:11:53.519
<v Speaker 1>This is getting exciting. We've covered governance, monitoring, automation. What

220
00:11:53.559 --> 00:11:56.159
<v Speaker 1>else is crucial for successful Azure management?

221
00:11:56.200 --> 00:11:59.279
<v Speaker 2>Security? Can't forget out security. It's the foundation upon which

222
00:11:59.279 --> 00:12:01.960
<v Speaker 2>everything else is built, right, and that's where Azure Security

223
00:12:02.000 --> 00:12:04.960
<v Speaker 2>Center or AASC takes center stage.

224
00:12:05.320 --> 00:12:09.080
<v Speaker 1>Right ASC we mentioned it earlier, but let's dive deeper.

225
00:12:09.639 --> 00:12:12.639
<v Speaker 1>What kind of security superpowers does it bring to the table?

226
00:12:13.000 --> 00:12:16.360
<v Speaker 2>Well, first and foremost, it provides a secure score, which

227
00:12:16.399 --> 00:12:18.679
<v Speaker 2>is a rating based on industry best practices.

228
00:12:18.759 --> 00:12:18.960
<v Speaker 1>Right.

229
00:12:19.480 --> 00:12:23.759
<v Speaker 2>It gives you an overall assessment of your security posture. Okay,

230
00:12:23.799 --> 00:12:26.240
<v Speaker 2>it's like a security report card. I like it for

231
00:12:26.320 --> 00:12:31.039
<v Speaker 2>your Azure environment, right, highlighting areas where you're excelling, right,

232
00:12:31.159 --> 00:12:32.120
<v Speaker 2>and where you need to improve.

233
00:12:32.360 --> 00:12:36.000
<v Speaker 1>So it helps us identify potential vulnerabilities exactly. Does it

234
00:12:36.080 --> 00:12:39.039
<v Speaker 1>just like point out problems or does it offer solutions

235
00:12:39.039 --> 00:12:39.480
<v Speaker 1>as well?

236
00:12:39.639 --> 00:12:43.399
<v Speaker 2>It doesn't just identify issues, okay. It also provides actionable

237
00:12:43.440 --> 00:12:46.360
<v Speaker 2>recommendations on how to strengthen your security. Think of it

238
00:12:46.360 --> 00:12:51.039
<v Speaker 2>as your personal security consultant, providing tailored advice on how

239
00:12:51.039 --> 00:12:53.240
<v Speaker 2>to protect your resources and mitigate risks.

240
00:12:53.480 --> 00:12:57.320
<v Speaker 1>It's like having a security expert on call, exactly, guiding

241
00:12:57.399 --> 00:13:01.080
<v Speaker 1>us through the process of securing our Azure environment. Yep, Okay,

242
00:13:01.080 --> 00:13:03.559
<v Speaker 1>I'm liking this more and more. What are some examples

243
00:13:03.840 --> 00:13:05.600
<v Speaker 1>of the recommendations it might provide?

244
00:13:05.720 --> 00:13:11.120
<v Speaker 2>So it could recommend enabling just in time, or get

245
00:13:12.000 --> 00:13:16.000
<v Speaker 2>VM access to limit exposure, only opening network ports when needed,

246
00:13:16.080 --> 00:13:20.799
<v Speaker 2>right okay. Or it might suggest implementing adaptive application control

247
00:13:21.320 --> 00:13:26.279
<v Speaker 2>to whitelist approved applications, preventing unauthorized software from running on

248
00:13:26.279 --> 00:13:26.919
<v Speaker 2>your servers.

249
00:13:27.120 --> 00:13:30.799
<v Speaker 1>Okay, So those sound like effective measures to tighten up security.

250
00:13:31.120 --> 00:13:34.240
<v Speaker 1>Oh yeah, what about those pesky cyber threats that are

251
00:13:34.279 --> 00:13:37.600
<v Speaker 1>constantly evolving? How does AC help us stay ahead of

252
00:13:37.639 --> 00:13:38.000
<v Speaker 1>the curve?

253
00:13:38.320 --> 00:13:42.600
<v Speaker 2>So? Threat protection in ASE uses real time detection okay,

254
00:13:42.840 --> 00:13:47.320
<v Speaker 2>and analysis to identify and respond to potential threats. It's

255
00:13:47.360 --> 00:13:51.759
<v Speaker 2>like having a security guard constantly patrolling your environment, watching

256
00:13:51.759 --> 00:13:55.639
<v Speaker 2>for suspicious activity and sounding the alarm if anything malicious

257
00:13:55.679 --> 00:13:56.279
<v Speaker 2>is detected.

258
00:13:56.360 --> 00:13:59.279
<v Speaker 1>So we have multiple layers of security in place, secure

259
00:13:59.320 --> 00:14:03.919
<v Speaker 1>score for overall assessment, recommendations for like proactive improvements, and

260
00:14:04.000 --> 00:14:06.919
<v Speaker 1>threat protection for real time defense exactly.

261
00:14:07.360 --> 00:14:11.639
<v Speaker 2>And as we explore more specific Azure management scenarios, we'll

262
00:14:11.679 --> 00:14:15.240
<v Speaker 2>see how ASE plays a crucial role in enjoying that

263
00:14:15.279 --> 00:14:19.639
<v Speaker 2>your cloud environment is not just powerful and efficient, but

264
00:14:19.759 --> 00:14:21.080
<v Speaker 2>also secure and protect it.

265
00:14:21.279 --> 00:14:24.480
<v Speaker 1>This has been an incredible overview of Azure management so far.

266
00:14:24.679 --> 00:14:25.639
<v Speaker 2>It has been we've.

267
00:14:25.440 --> 00:14:31.320
<v Speaker 1>Covered governance, monitoring, automations, security, we have what else is

268
00:14:31.320 --> 00:14:32.080
<v Speaker 1>there to explore?

269
00:14:32.159 --> 00:14:34.360
<v Speaker 2>Oh, there's so much more. Okay, we haven't even touched

270
00:14:34.399 --> 00:14:38.559
<v Speaker 2>on disaster recovery, Yeah, cost management or migration Okay, but

271
00:14:38.600 --> 00:14:41.440
<v Speaker 2>those are topics for another deep dive another day.

272
00:14:41.559 --> 00:14:44.639
<v Speaker 1>I can't wait. This is like uncovering a treasure trove

273
00:14:44.679 --> 00:14:48.000
<v Speaker 1>of knowledge about Azure management. But for now, let's take

274
00:14:48.000 --> 00:14:50.000
<v Speaker 1>a break and let all this information sink in.

275
00:14:50.240 --> 00:14:51.039
<v Speaker 2>Yeah, let's do that.

276
00:14:51.159 --> 00:14:54.519
<v Speaker 1>We'll be back soon to explore even more fascinating aspects.

277
00:14:54.559 --> 00:14:57.679
<v Speaker 1>That's good of this ever evolving cloud landscape.

278
00:14:57.799 --> 00:14:58.399
<v Speaker 2>I'm excited.

279
00:14:58.679 --> 00:15:01.919
<v Speaker 1>Welcome back to the deep dive. All right, we just

280
00:15:01.960 --> 00:15:04.960
<v Speaker 1>scratch the surface of Azure monitor. It's like having a

281
00:15:05.000 --> 00:15:08.159
<v Speaker 1>detective on the case sifting through all that telemetry data.

282
00:15:08.240 --> 00:15:12.559
<v Speaker 2>Absolutely, and the real detective work happens in Azure log analytics.

283
00:15:12.840 --> 00:15:16.240
<v Speaker 2>It gathers data from all those sources we discussed, agents,

284
00:15:16.360 --> 00:15:20.039
<v Speaker 2>diagnostic settings, and then it uses the Cousto Query language

285
00:15:20.360 --> 00:15:22.639
<v Speaker 2>or QL to analyze it KQL.

286
00:15:23.240 --> 00:15:26.000
<v Speaker 1>It sounds intimidating, but the book made it seem almost

287
00:15:26.080 --> 00:15:26.759
<v Speaker 1>user friendly.

288
00:15:26.960 --> 00:15:29.360
<v Speaker 2>Yeah. It's designed to be powerful but accessible.

289
00:15:29.600 --> 00:15:29.960
<v Speaker 1>Okay.

290
00:15:30.000 --> 00:15:32.720
<v Speaker 2>I imagine being able to ask complex questions about your

291
00:15:32.759 --> 00:15:36.399
<v Speaker 2>Azure environment. Yeah, and get instant answers. That's the beauty

292
00:15:36.440 --> 00:15:37.120
<v Speaker 2>of KQL.

293
00:15:37.159 --> 00:15:39.480
<v Speaker 1>Give me an example, Okay, sure, how can we use

294
00:15:39.600 --> 00:15:42.720
<v Speaker 1>KQL to gain insights from our Azure logs.

295
00:15:42.879 --> 00:15:45.360
<v Speaker 2>Let's say you want to track down a performance issue. Okay,

296
00:15:45.799 --> 00:15:49.039
<v Speaker 2>you could write a KQL query to analyze logs from

297
00:15:49.080 --> 00:15:54.960
<v Speaker 2>your web server, database, and application, correlating events to pinpoint

298
00:15:55.000 --> 00:15:58.000
<v Speaker 2>the root cause. Okay, it's like having a time machine.

299
00:15:58.120 --> 00:16:00.159
<v Speaker 2>I like it. That allows you to replay events and

300
00:16:00.200 --> 00:16:01.360
<v Speaker 2>see exactly what happened.

301
00:16:01.360 --> 00:16:05.320
<v Speaker 1>That would be incredibly helpful for troubleshooting those tricky issues

302
00:16:05.320 --> 00:16:08.200
<v Speaker 1>that span multiple comportments. Absolutely, and the authors of Insight

303
00:16:08.240 --> 00:16:12.200
<v Speaker 1>Asual Management also highlighted the importance of activity logs. How

304
00:16:12.200 --> 00:16:14.919
<v Speaker 1>do those fit into this data analysis puzzle?

305
00:16:15.159 --> 00:16:18.200
<v Speaker 2>So, activity logs are like your Azure audit trail. They

306
00:16:18.240 --> 00:16:23.360
<v Speaker 2>record every action taken in your subscriptions, creating resources, deleting resources,

307
00:16:23.399 --> 00:16:28.000
<v Speaker 2>changing configurations, everything. Analyzing these logs with KQL can be

308
00:16:28.279 --> 00:16:33.879
<v Speaker 2>crucial for security auditing, compliance investigations, and even understanding resource

309
00:16:34.000 --> 00:16:34.879
<v Speaker 2>usage patterns.

310
00:16:35.200 --> 00:16:38.000
<v Speaker 1>That's a gold mine of information. But I remember the

311
00:16:38.000 --> 00:16:41.679
<v Speaker 1>book mentioning that activity logs have a limited retention period

312
00:16:41.679 --> 00:16:42.320
<v Speaker 1>by default.

313
00:16:42.399 --> 00:16:44.799
<v Speaker 2>That's right, They're only kept for ninety days by default,

314
00:16:45.279 --> 00:16:48.000
<v Speaker 2>but here's a pro tip. You can archive them to

315
00:16:48.039 --> 00:16:50.759
<v Speaker 2>a log analytics workspace okay if you need to keep

316
00:16:50.759 --> 00:16:53.960
<v Speaker 2>them longer. It's like having a long term memory for

317
00:16:54.039 --> 00:16:55.159
<v Speaker 2>your Azure environment.

318
00:16:55.519 --> 00:16:59.840
<v Speaker 1>So we're collecting data from agents, capturing activity logs, and

319
00:17:00.159 --> 00:17:03.639
<v Speaker 1>analyzing it all with log analytics and KQL exactly. That's

320
00:17:03.679 --> 00:17:07.640
<v Speaker 1>a comprehensive monitoring setup. But what about Azure metrics? Where

321
00:17:07.640 --> 00:17:08.480
<v Speaker 1>do those fit in?

322
00:17:08.599 --> 00:17:11.200
<v Speaker 2>So metrics are those numerical data points that give you

323
00:17:11.240 --> 00:17:16.039
<v Speaker 2>a real time view of resource performance, things like CPU usage,

324
00:17:16.319 --> 00:17:20.559
<v Speaker 2>network traffic, disc performance. Okay. Think of them as the

325
00:17:20.680 --> 00:17:24.079
<v Speaker 2>vital signs of your Azure environment, right right. They're collected

326
00:17:24.119 --> 00:17:27.799
<v Speaker 2>at very short intervals, allowing you to detect anomalies and

327
00:17:27.880 --> 00:17:29.119
<v Speaker 2>trends as they happen.

328
00:17:29.480 --> 00:17:32.799
<v Speaker 1>Okay, So metrics are more about real time performance monitoring.

329
00:17:33.039 --> 00:17:33.319
<v Speaker 2>Yeah.

330
00:17:33.480 --> 00:17:35.640
<v Speaker 1>While logs provide a detailed record of.

331
00:17:35.559 --> 00:17:39.200
<v Speaker 2>Events, precisely, they work together to give you a holistic

332
00:17:39.279 --> 00:17:42.680
<v Speaker 2>view of your environment's health and behavior. And here's something

333
00:17:42.720 --> 00:17:45.799
<v Speaker 2>interesting about metrics. They can be retained for up to

334
00:17:45.880 --> 00:17:50.640
<v Speaker 2>ninety three days, giving you a historical perspective on performance trends.

335
00:17:50.799 --> 00:17:53.960
<v Speaker 1>Ninety three days of metrics data. That's a lot of

336
00:17:54.000 --> 00:17:56.960
<v Speaker 1>information to sift through. It is, Are there any pre

337
00:17:57.039 --> 00:18:00.680
<v Speaker 1>built tools within Azure Monitor that make this analysis us easier?

338
00:18:00.759 --> 00:18:04.200
<v Speaker 2>You bet. Az Your monitor offers several perspectives and insights

339
00:18:04.200 --> 00:18:08.279
<v Speaker 2>that simplify monitoring specific scenarios. One of the most valuable

340
00:18:08.720 --> 00:18:09.680
<v Speaker 2>is service.

341
00:18:09.319 --> 00:18:12.200
<v Speaker 1>Health Service Health. Right, It's like that big status bold

342
00:18:12.240 --> 00:18:14.720
<v Speaker 1>It is that tells us if Azure itself is having

343
00:18:14.720 --> 00:18:18.519
<v Speaker 1>any issues, especially helpful during those rare outages.

344
00:18:19.039 --> 00:18:22.599
<v Speaker 2>Exactly. It provides a global view of Azure Service Health,

345
00:18:22.880 --> 00:18:25.680
<v Speaker 2>so you can quickly see if there are any widespread

346
00:18:25.680 --> 00:18:29.880
<v Speaker 2>problems or plan maintenance activities that might impact your resources.

347
00:18:30.480 --> 00:18:33.440
<v Speaker 2>No more frantically checking Twitter to see if others are

348
00:18:33.480 --> 00:18:34.759
<v Speaker 2>experiencing the same issue.

349
00:18:35.000 --> 00:18:38.559
<v Speaker 1>Love that it takes the guesswork out of troubleshooting. Yeah,

350
00:18:38.599 --> 00:18:41.640
<v Speaker 1>what about those interactive reports? Oh yeah, you mentioned earlier.

351
00:18:41.680 --> 00:18:43.400
<v Speaker 1>I think they were called workbooks.

352
00:18:43.440 --> 00:18:48.960
<v Speaker 2>Workbooks, So workbooks are like building custom dashboards within Azure Monitor.

353
00:18:49.160 --> 00:18:49.319
<v Speaker 1>Ok.

354
00:18:49.519 --> 00:18:52.480
<v Speaker 2>You can pull data from various sources and visualize it

355
00:18:52.519 --> 00:18:55.559
<v Speaker 2>in a way that makes sense to you. Imagine tracking

356
00:18:56.039 --> 00:19:00.680
<v Speaker 2>CPU usage across all your virtual machines in a single chart,

357
00:19:01.519 --> 00:19:06.039
<v Speaker 2>or correlating application performance with network traffic workbooks make it

358
00:19:06.079 --> 00:19:08.279
<v Speaker 2>easy to create those tailored views.

359
00:19:08.319 --> 00:19:11.440
<v Speaker 1>Okay, workbooks are officially on my list to explore. Nice

360
00:19:11.640 --> 00:19:14.440
<v Speaker 1>What other perspectives does Azure monitor offer?

361
00:19:14.799 --> 00:19:17.960
<v Speaker 2>So if you're running web applications, you absolutely need to

362
00:19:18.039 --> 00:19:21.440
<v Speaker 2>check out Application Insights. It's like having x ray vision

363
00:19:21.519 --> 00:19:27.279
<v Speaker 2>into your web apps, providing detailed performance metrics, user behavior analytics,

364
00:19:27.599 --> 00:19:29.519
<v Speaker 2>and even code level diagnostics.

365
00:19:30.200 --> 00:19:32.480
<v Speaker 1>So we can see not just how our apps are

366
00:19:32.519 --> 00:19:36.880
<v Speaker 1>performing technically, but also how users are interacting with them.

367
00:19:37.000 --> 00:19:37.519
<v Speaker 2>Exactly.

368
00:19:37.799 --> 00:19:41.559
<v Speaker 1>That's valuable information for optimizing the user experience.

369
00:19:41.880 --> 00:19:45.039
<v Speaker 2>Absolutely, And for those who need to dive deep into

370
00:19:45.160 --> 00:19:50.440
<v Speaker 2>the performance, health, and dependencies of their virtual machines, there's

371
00:19:50.559 --> 00:19:52.079
<v Speaker 2>Virtual Machine Insights.

372
00:19:52.160 --> 00:19:52.519
<v Speaker 1>Okay.

373
00:19:52.599 --> 00:19:57.200
<v Speaker 2>It offers rich visualizations, performance charts, dependency men, wow, everything

374
00:19:57.240 --> 00:19:59.640
<v Speaker 2>you need to diagnose issues and ensure your vms are

375
00:19:59.680 --> 00:20:01.480
<v Speaker 2>running at peak performance.

376
00:20:01.079 --> 00:20:03.000
<v Speaker 1>As your monitor really is a powerful tool.

377
00:20:03.240 --> 00:20:04.400
<v Speaker 2>Oh yeah, but let's.

378
00:20:04.200 --> 00:20:06.519
<v Speaker 1>Shift gears for a bit. We got all this data, yeah,

379
00:20:06.559 --> 00:20:08.559
<v Speaker 1>but sometimes we need to take action based on what

380
00:20:08.599 --> 00:20:09.119
<v Speaker 1>we're seeing.

381
00:20:09.400 --> 00:20:09.599
<v Speaker 2>Right.

382
00:20:09.799 --> 00:20:11.599
<v Speaker 1>That's where automation comes in, right.

383
00:20:11.480 --> 00:20:15.039
<v Speaker 2>Exactly, as your automation is your automation sidekick, right, Okay,

384
00:20:15.519 --> 00:20:18.759
<v Speaker 2>handling those repetitive tasks so you can focus on more

385
00:20:18.799 --> 00:20:22.480
<v Speaker 2>strategic work. We talked about run books earlier. Yeah, PowerShell,

386
00:20:22.599 --> 00:20:27.039
<v Speaker 2>Python and graphical, but let's explore how we can leverage

387
00:20:27.079 --> 00:20:28.000
<v Speaker 2>them effectively.

388
00:20:28.279 --> 00:20:31.319
<v Speaker 1>PowerShell and Python are great for scripting pros. Yeah, but

389
00:20:31.440 --> 00:20:35.440
<v Speaker 1>graphical run books sound more approachable. They are for those

390
00:20:35.480 --> 00:20:37.039
<v Speaker 1>of us who prefer a visual approach.

391
00:20:37.319 --> 00:20:41.559
<v Speaker 2>Absolutely. You can create workflows by dragging and dropping activities,

392
00:20:42.319 --> 00:20:46.079
<v Speaker 2>connecting them logically, and configuring them without writing any code.

393
00:20:46.359 --> 00:20:49.920
<v Speaker 2>Imagine building a flow chart that automates a complex process. Okay,

394
00:20:50.039 --> 00:20:52.079
<v Speaker 2>that's the power of graphical run books.

395
00:20:52.119 --> 00:20:55.519
<v Speaker 1>What are some real world use cases for these run books?

396
00:20:55.799 --> 00:20:56.880
<v Speaker 1>There be some examples.

397
00:20:57.000 --> 00:21:02.039
<v Speaker 2>Imagine automatically scaling your virtual machine up or down based

398
00:21:02.039 --> 00:21:05.920
<v Speaker 2>on CPU usage, or triggering a backup whenever a new

399
00:21:06.000 --> 00:21:07.119
<v Speaker 2>database is created.

400
00:21:07.240 --> 00:21:07.519
<v Speaker 1>Okay.

401
00:21:07.759 --> 00:21:11.319
<v Speaker 2>You could even automate user provisioning, creating new accounts and

402
00:21:11.359 --> 00:21:14.720
<v Speaker 2>assigning permissions based on pre defined rules.

403
00:21:14.960 --> 00:21:17.799
<v Speaker 1>That's impressive. It's like having a virtual IT team. It

404
00:21:17.880 --> 00:21:21.440
<v Speaker 1>is working tirelessly behind the scenes. And here's the best part,

405
00:21:21.920 --> 00:21:24.599
<v Speaker 1>as your automation can extend beyond the cloud.

406
00:21:24.839 --> 00:21:25.240
<v Speaker 2>That's right.

407
00:21:25.279 --> 00:21:28.839
<v Speaker 1>With hybrid workers, you can manage and automate tasks on

408
00:21:28.880 --> 00:21:31.680
<v Speaker 1>your on premises service as well. Exactly, so we can

409
00:21:31.720 --> 00:21:36.079
<v Speaker 1>have a unified automation platform that spans both cloud and

410
00:21:36.200 --> 00:21:41.160
<v Speaker 1>on premises environments. That's a game changer for organizations with

411
00:21:41.240 --> 00:21:42.400
<v Speaker 1>hybrid infrastructures.

412
00:21:42.480 --> 00:21:45.359
<v Speaker 2>It is. And if you want to trigger those automations

413
00:21:45.400 --> 00:21:50.039
<v Speaker 2>from external systems or applications, webbooks are your go to solution.

414
00:21:50.279 --> 00:21:50.640
<v Speaker 1>Okay.

415
00:21:51.160 --> 00:21:57.000
<v Speaker 2>Imagine integrating your monitoring system with Azure automation, automatically triggering

416
00:21:57.000 --> 00:22:00.759
<v Speaker 2>a runbook to scale up resources when it performs threshold

417
00:22:00.799 --> 00:22:01.279
<v Speaker 2>is breached.

418
00:22:01.359 --> 00:22:04.160
<v Speaker 1>Okay, now we're talking right. That's the kind of intelligent

419
00:22:04.200 --> 00:22:07.880
<v Speaker 1>automation that can really optimize our Azure environment. Absolutely, we've

420
00:22:07.880 --> 00:22:11.799
<v Speaker 1>covered governance, monitoring, automation. We have what's next on our

421
00:22:11.880 --> 00:22:13.079
<v Speaker 1>Azure management journey.

422
00:22:13.200 --> 00:22:17.240
<v Speaker 2>Let's talk about something that's often overlooked but absolutely crucial

423
00:22:17.839 --> 00:22:21.400
<v Speaker 2>cost management. After all, what good is a powerful and

424
00:22:21.440 --> 00:22:23.960
<v Speaker 2>efficient cloud environment? Right if it breaks the bank?

425
00:22:24.039 --> 00:22:26.000
<v Speaker 1>We need to keep those cloud costs in check.

426
00:22:26.319 --> 00:22:26.799
<v Speaker 2>Exactly.

427
00:22:26.839 --> 00:22:29.119
<v Speaker 1>How does Azure help us manage our spending?

428
00:22:29.640 --> 00:22:33.359
<v Speaker 2>So az your cost management is our financial guardian, providing

429
00:22:33.400 --> 00:22:38.279
<v Speaker 2>tools and insights to track, analyze, and optimize cloud spending. Okay,

430
00:22:38.440 --> 00:22:41.680
<v Speaker 2>It's like having a personal accountant for your Azure environment.

431
00:22:41.720 --> 00:22:44.240
<v Speaker 1>So it helps us avoid those bill shock moments.

432
00:22:44.279 --> 00:22:45.240
<v Speaker 2>Oh yeah, one d percent.

433
00:22:45.599 --> 00:22:47.519
<v Speaker 1>What are some of the key features it offers.

434
00:22:47.599 --> 00:22:50.359
<v Speaker 2>One are the most important features is cost analysis.

435
00:22:50.480 --> 00:22:51.200
<v Speaker 1>Okay.

436
00:22:51.279 --> 00:22:54.759
<v Speaker 2>It provides a detailed breakdown of your Azure spending, allowing

437
00:22:54.799 --> 00:22:58.119
<v Speaker 2>you to see exactly where your money is going and

438
00:22:58.359 --> 00:23:01.160
<v Speaker 2>identify areas for potential savings.

439
00:23:01.319 --> 00:23:03.880
<v Speaker 1>No more guessing games when it comes to the Azure bills.

440
00:23:03.960 --> 00:23:04.440
<v Speaker 2>Exactly.

441
00:23:04.519 --> 00:23:07.640
<v Speaker 1>What other features help us keep our spending under control?

442
00:23:08.000 --> 00:23:11.960
<v Speaker 2>So as your cost management offers budgets allowing you to

443
00:23:12.000 --> 00:23:18.000
<v Speaker 2>set spending limits for subscriptions, resource groups, or even individual resources,

444
00:23:18.400 --> 00:23:22.000
<v Speaker 2>you could receive alerts when you're approaching those limits, right,

445
00:23:22.440 --> 00:23:24.640
<v Speaker 2>ensuring you stay on track with your budget.

446
00:23:24.759 --> 00:23:26.759
<v Speaker 1>So it's like having financial guardrails.

447
00:23:26.759 --> 00:23:29.839
<v Speaker 2>It's like having financial guardrails for our cloud environment. For

448
00:23:29.880 --> 00:23:32.279
<v Speaker 2>your cloud environment one hundred percent.

449
00:23:32.079 --> 00:23:34.359
<v Speaker 1>So we can set a budget for our development team,

450
00:23:34.640 --> 00:23:37.559
<v Speaker 1>for example, and make sure they don't accidentally spin up

451
00:23:37.559 --> 00:23:40.440
<v Speaker 1>a cluster of high powered vms that break the bank.

452
00:23:40.680 --> 00:23:43.599
<v Speaker 2>Exactly, And if you need to dive deeper into your

453
00:23:43.680 --> 00:23:46.799
<v Speaker 2>cost data, you can export it to a storage account

454
00:23:47.000 --> 00:23:52.240
<v Speaker 2>for custom analysis and visualization. Imagine creating trend reports, identifying

455
00:23:52.319 --> 00:23:56.720
<v Speaker 2>spending patterns and even building custom dashboards to track your

456
00:23:56.720 --> 00:23:58.160
<v Speaker 2>cloud costs over time.

457
00:23:58.599 --> 00:24:02.400
<v Speaker 1>That level of visibility and control is essential for making

458
00:24:02.519 --> 00:24:06.720
<v Speaker 1>informed decisions about our Azure resources. Is we're not just

459
00:24:06.799 --> 00:24:09.519
<v Speaker 1>managing technology, we're managing a budget as well.

460
00:24:09.640 --> 00:24:12.920
<v Speaker 2>One hundred percent And as we delve deeper into Azure management,

461
00:24:12.960 --> 00:24:16.000
<v Speaker 2>we'll see how cost management plays a crucial role in

462
00:24:16.079 --> 00:24:19.279
<v Speaker 2>every decision we make. But before we move on, yeah,

463
00:24:19.359 --> 00:24:23.960
<v Speaker 2>let's address another critical aspect, migrating workloads to Azure.

464
00:24:24.400 --> 00:24:28.200
<v Speaker 1>Right migration, Moving those applications and databases to the cloud.

465
00:24:28.799 --> 00:24:30.559
<v Speaker 1>That can seem like a daunting task.

466
00:24:31.039 --> 00:24:34.160
<v Speaker 2>It can be, but Azure offers a range of services

467
00:24:34.160 --> 00:24:36.880
<v Speaker 2>and tools to guide you through the process. Okay, and

468
00:24:36.920 --> 00:24:38.839
<v Speaker 2>it all starts with Azure Migrate.

469
00:24:39.000 --> 00:24:41.920
<v Speaker 1>Asure Migrate is that like a one stop shop for

470
00:24:42.079 --> 00:24:43.200
<v Speaker 1>migrating to the cloud.

471
00:24:43.400 --> 00:24:46.519
<v Speaker 2>Think of it as your migration command center. It helps

472
00:24:46.519 --> 00:24:51.759
<v Speaker 2>you assess your existing workloads, understand their dependencies, and determine

473
00:24:51.799 --> 00:24:55.880
<v Speaker 2>their suitability for cloud migration. Okay, it's like planning a move, right,

474
00:24:55.960 --> 00:24:58.759
<v Speaker 2>uh huh. You need to know what you're taking with you,

475
00:24:59.200 --> 00:25:01.359
<v Speaker 2>how you're going to get it it there, and where

476
00:25:01.359 --> 00:25:03.799
<v Speaker 2>it's going to fit in your new space makes sense.

477
00:25:03.920 --> 00:25:06.799
<v Speaker 1>So as Your Migrate helps us figure out what to migrate,

478
00:25:07.279 --> 00:25:09.319
<v Speaker 1>how to migrate it, and where it's going to live

479
00:25:09.359 --> 00:25:11.000
<v Speaker 1>in Azure exactly.

480
00:25:11.240 --> 00:25:15.680
<v Speaker 2>And it offers tools for specific migration scenarios. For server migration,

481
00:25:15.759 --> 00:25:20.119
<v Speaker 2>there's Azure Migrate Server Assessment, which analyzes your on premises

482
00:25:20.160 --> 00:25:25.039
<v Speaker 2>servers and provides recommendations on sizing, readiness, and cost estimates

483
00:25:25.079 --> 00:25:26.799
<v Speaker 2>for running those servers in Azure.

484
00:25:27.000 --> 00:25:30.240
<v Speaker 1>It's like getting a virtual moving quote before you pack

485
00:25:30.279 --> 00:25:33.880
<v Speaker 1>a single box. I like that analogy. What about migrating

486
00:25:34.079 --> 00:25:37.160
<v Speaker 1>databases that seems much more complex?

487
00:25:37.400 --> 00:25:39.519
<v Speaker 2>As your Migrate has you covered there as well? Okay,

488
00:25:39.599 --> 00:25:43.160
<v Speaker 2>The as You Migrate Database Assessment tool analyzes your on

489
00:25:43.319 --> 00:25:49.039
<v Speaker 2>premises databases and recommends the best as your database service

490
00:25:49.160 --> 00:25:52.359
<v Speaker 2>for your needs, whether it's as your SQL database, as

491
00:25:52.400 --> 00:25:55.680
<v Speaker 2>your Cosmos dB, or something else.

492
00:25:55.880 --> 00:25:58.039
<v Speaker 1>So it's not a one size fits all approach. No.

493
00:25:58.319 --> 00:26:02.240
<v Speaker 1>Asure Migrate helps us chew use the right cloud database

494
00:26:02.319 --> 00:26:05.319
<v Speaker 1>solution exactly for our specific.

495
00:26:04.799 --> 00:26:06.279
<v Speaker 2>Needs for your specific needs.

496
00:26:06.359 --> 00:26:08.880
<v Speaker 1>Yeah, and for web apps. For web apps, does Asure

497
00:26:08.920 --> 00:26:10.160
<v Speaker 1>Migrate help there as well?

498
00:26:10.359 --> 00:26:13.720
<v Speaker 2>As your Migrate integrates with the app service Migration Assistant,

499
00:26:14.119 --> 00:26:16.880
<v Speaker 2>which helps you assess and migrate your web apps running

500
00:26:16.880 --> 00:26:20.440
<v Speaker 2>on isis to as your app service. It's a smooth

501
00:26:20.440 --> 00:26:23.680
<v Speaker 2>transition to a platform designed specifically for web apps.

502
00:26:23.720 --> 00:26:25.799
<v Speaker 1>It sounds like as your migrate has all the bases covered.

503
00:26:25.920 --> 00:26:26.319
<v Speaker 2>It does.

504
00:26:26.480 --> 00:26:30.000
<v Speaker 1>But once we've migrated our workloads to Azure, what's next.

505
00:26:30.440 --> 00:26:32.160
<v Speaker 1>It's not just set it and forget it.

506
00:26:32.440 --> 00:26:36.000
<v Speaker 2>Absolutely not. Once your workloads are running in Azure, you

507
00:26:36.079 --> 00:26:40.279
<v Speaker 2>need to optimize them, ensuring they're performing efficiently, cost effectively

508
00:26:40.319 --> 00:26:40.960
<v Speaker 2>and securely.

509
00:26:41.400 --> 00:26:44.640
<v Speaker 1>Right, we've talked about cost optimization with azur cost management,

510
00:26:45.200 --> 00:26:48.039
<v Speaker 1>what about optimizing performance and security?

511
00:26:48.240 --> 00:26:50.880
<v Speaker 2>So as your monitor and as your Security center are

512
00:26:50.920 --> 00:26:53.440
<v Speaker 2>your go to tools for that. You can use a

513
00:26:53.519 --> 00:26:59.079
<v Speaker 2>your monitor to track performance, identify bottlenecks, and optimize resource utilization.

514
00:26:59.759 --> 00:27:03.680
<v Speaker 2>And Azure Security Center helps you secure your migrated workloads,

515
00:27:04.359 --> 00:27:09.519
<v Speaker 2>providing recommendations, identifying vulnerabilities, and protecting against threats.

516
00:27:09.799 --> 00:27:13.480
<v Speaker 1>So it's continuous cycle of monitoring, optimizing, and securing.

517
00:27:13.519 --> 00:27:16.200
<v Speaker 2>Exactly, it's about finding that sweet spot where your Azure

518
00:27:16.279 --> 00:27:21.160
<v Speaker 2>environment is running smoothly, sufficiently, and securely without breaking the bank.

519
00:27:21.880 --> 00:27:25.400
<v Speaker 2>But that's a topic for another deep dive another day.

520
00:27:25.680 --> 00:27:28.880
<v Speaker 1>You're killing me with these cliffhangers. I know, I know,

521
00:27:29.240 --> 00:27:31.799
<v Speaker 1>but You're right, We've covered a lot of ground today,

522
00:27:32.000 --> 00:27:37.039
<v Speaker 1>from the intricacies of Azure Monitor to the complexities of migration. Absolutely,

523
00:27:37.039 --> 00:27:38.559
<v Speaker 1>but the journey doesn't end here.

524
00:27:38.759 --> 00:27:39.240
<v Speaker 2>It doesn't.

525
00:27:39.279 --> 00:27:42.039
<v Speaker 1>There's still so much more to explore, oh so much more.

526
00:27:42.039 --> 00:27:44.839
<v Speaker 1>Stay tuned. We'll be back soon to delve deeper into

527
00:27:44.839 --> 00:27:48.720
<v Speaker 1>the world of Azure management, uncovering even more insights and

528
00:27:48.839 --> 00:27:55.440
<v Speaker 1>practical tips. Yeah, to help you master the cloud. Welcome

529
00:27:55.480 --> 00:27:58.839
<v Speaker 1>back to the deep dive. We've covered a lot of ground,

530
00:27:59.079 --> 00:28:02.559
<v Speaker 1>you know, from set up that solid governance foundation to

531
00:28:02.799 --> 00:28:07.039
<v Speaker 1>exploring the depths of Azure Monitor and automation. Absolutely, But

532
00:28:07.200 --> 00:28:10.440
<v Speaker 1>like any well managed system, we need a way to

533
00:28:10.599 --> 00:28:13.880
<v Speaker 1>know right when things need our attention exactly.

534
00:28:13.960 --> 00:28:15.440
<v Speaker 2>That's where Azure alerts come in.

535
00:28:15.559 --> 00:28:15.880
<v Speaker 1>Okay.

536
00:28:15.920 --> 00:28:18.440
<v Speaker 2>Think of them as our early warning system, right okay,

537
00:28:18.680 --> 00:28:22.799
<v Speaker 2>constantly monitoring our environment, alerting us to potential issues.

538
00:28:22.839 --> 00:28:25.720
<v Speaker 1>Alerts like those notifications that pop up on our phones.

539
00:28:25.839 --> 00:28:29.640
<v Speaker 2>It's more than just notifications. It's about proactively responding to

540
00:28:29.839 --> 00:28:33.400
<v Speaker 2>events in your Azure environment. And the beauty of Azure

541
00:28:33.440 --> 00:28:37.599
<v Speaker 2>alerts is the level of customization you have. You can

542
00:28:37.680 --> 00:28:40.720
<v Speaker 2>tailor them to fit your specific needs and workflows.

543
00:28:40.799 --> 00:28:43.880
<v Speaker 1>Okay, color me intrigued. What kind of customization are we

544
00:28:43.920 --> 00:28:45.759
<v Speaker 1>talking about here? Walk me through the options.

545
00:28:46.400 --> 00:28:49.799
<v Speaker 2>Let's start with activity log alerts. Okay, remember those activity

546
00:28:49.839 --> 00:28:51.319
<v Speaker 2>logs we discussed earlier, like a.

547
00:28:51.359 --> 00:28:54.279
<v Speaker 1>Detailed history of everything that happens in azure.

548
00:28:54.440 --> 00:28:59.240
<v Speaker 2>Exactly. With activity lag alerts, you can trigger notifications whenever

549
00:28:59.359 --> 00:29:02.880
<v Speaker 2>specific event it's occur in those logs. Let's say someone

550
00:29:02.920 --> 00:29:06.480
<v Speaker 2>tries to create a virtual machine in a region you're

551
00:29:06.519 --> 00:29:11.279
<v Speaker 2>not supposed to use, or deletes a critical database. An

552
00:29:11.319 --> 00:29:15.039
<v Speaker 2>activity log alert can immediately notify you oh wow, giving

553
00:29:15.039 --> 00:29:17.599
<v Speaker 2>you a chance to intervene before any damage is done.

554
00:29:17.680 --> 00:29:20.279
<v Speaker 1>So that's like having a security guard watching over as

555
00:29:20.319 --> 00:29:21.039
<v Speaker 1>your environment.

556
00:29:21.160 --> 00:29:21.839
<v Speaker 2>It is yet.

557
00:29:21.720 --> 00:29:25.599
<v Speaker 1>Alerting us to any suspicious activity exactly. Okay, what other

558
00:29:25.680 --> 00:29:26.920
<v Speaker 1>types of alerts are there?

559
00:29:27.039 --> 00:29:30.440
<v Speaker 2>So? For performance monitoring, metric alerts are your go to.

560
00:29:31.359 --> 00:29:36.279
<v Speaker 2>They trigger when a specific metric crosses a pre defined threshold. So,

561
00:29:36.400 --> 00:29:39.119
<v Speaker 2>for example, you could set an alert to notify you

562
00:29:39.640 --> 00:29:44.079
<v Speaker 2>if CPU usage on your web server exceeds eighty percent

563
00:29:44.160 --> 00:29:47.960
<v Speaker 2>for an extended period, or if available disk base on

564
00:29:48.000 --> 00:29:50.759
<v Speaker 2>your database server drops below a critical level.

565
00:29:51.000 --> 00:29:54.200
<v Speaker 1>So it's about setting those early warning signs. Exactly, those

566
00:29:54.240 --> 00:29:57.000
<v Speaker 1>trip wires that let us know when something needs attention.

567
00:29:58.000 --> 00:30:00.200
<v Speaker 1>And then we have log alerts, which are based on

568
00:30:00.319 --> 00:30:04.160
<v Speaker 1>queries run against your log analytics data. We talked about

569
00:30:04.240 --> 00:30:07.839
<v Speaker 1>KQL earlier, that powerful query language for analyzing log data.

570
00:30:07.960 --> 00:30:10.519
<v Speaker 1>We did, so we can create custom queries to look

571
00:30:10.559 --> 00:30:14.240
<v Speaker 1>for specific patterns or anomalies in our logs and then

572
00:30:14.279 --> 00:30:15.960
<v Speaker 1>trigger alerts based on those conditions.

573
00:30:16.000 --> 00:30:19.480
<v Speaker 2>You got it. It's a really powerful way to detect

574
00:30:19.599 --> 00:30:23.400
<v Speaker 2>unusual activity. Okay, that might signal a security threat or

575
00:30:23.440 --> 00:30:24.559
<v Speaker 2>a performance issue.

576
00:30:24.599 --> 00:30:24.839
<v Speaker 1>Okay.

577
00:30:24.920 --> 00:30:27.440
<v Speaker 2>For example, you could create a log alert that triggers

578
00:30:27.519 --> 00:30:31.440
<v Speaker 2>if there's a sudden spike in failed login attempts, or

579
00:30:31.519 --> 00:30:36.640
<v Speaker 2>if a particular error message appears repeatedly in your application logs.

580
00:30:36.960 --> 00:30:41.000
<v Speaker 1>So we have activity log alerts, metric alerts, and log alerts,

581
00:30:41.559 --> 00:30:44.559
<v Speaker 1>all working together to keep us informed about what's happening

582
00:30:44.559 --> 00:30:45.599
<v Speaker 1>in our Azure environment.

583
00:30:45.720 --> 00:30:46.160
<v Speaker 2>That's right.

584
00:30:46.359 --> 00:30:49.240
<v Speaker 1>But what happens when those alerts go off. It's not

585
00:30:49.279 --> 00:30:51.480
<v Speaker 1>like hitting the snooze button on an alarm clock.

586
00:30:51.599 --> 00:30:52.039
<v Speaker 2>No, it's not.

587
00:30:52.519 --> 00:30:54.400
<v Speaker 1>We need to take action where.

588
00:30:54.240 --> 00:30:57.440
<v Speaker 2>Action groups come in. Okay. The muscle behind Azure alerts

589
00:30:57.920 --> 00:31:01.640
<v Speaker 2>those automated responders that spring into action when an alert

590
00:31:01.680 --> 00:31:02.240
<v Speaker 2>is triggered.

591
00:31:02.680 --> 00:31:05.799
<v Speaker 1>So we can define specific actions to be taken when

592
00:31:05.799 --> 00:31:09.559
<v Speaker 1>an alert fires, essentially automating our response exactly.

593
00:31:10.279 --> 00:31:14.000
<v Speaker 2>Action groups can run scripts, send emails, integrate with third

594
00:31:14.079 --> 00:31:19.240
<v Speaker 2>party systems, and even trigger Azure functions. Those serverless code

595
00:31:19.240 --> 00:31:21.319
<v Speaker 2>snippets that can handle specific tasks.

596
00:31:21.559 --> 00:31:24.000
<v Speaker 1>Give me like a real world example. Let's say our

597
00:31:24.039 --> 00:31:27.119
<v Speaker 1>web servers overloaded and a metric alert is triggered, right,

598
00:31:27.480 --> 00:31:29.759
<v Speaker 1>what could an action group do in that scenario?

599
00:31:30.079 --> 00:31:32.759
<v Speaker 2>So it could automatically scale out your web server okay,

600
00:31:32.920 --> 00:31:36.319
<v Speaker 2>adding more instances to handle the increased traffic load. Okay.

601
00:31:36.759 --> 00:31:39.240
<v Speaker 2>Or it could send a notification to your on call team,

602
00:31:40.160 --> 00:31:42.519
<v Speaker 2>alerting them to the issue so they can investigate further.

603
00:31:42.720 --> 00:31:46.279
<v Speaker 1>So we're not just passively monitoring our environment. We're actively

604
00:31:46.319 --> 00:31:50.000
<v Speaker 1>responding to events and automating our remediation efforts.

605
00:31:50.119 --> 00:31:51.640
<v Speaker 2>Absolutely, that's powerful.

606
00:31:51.920 --> 00:31:54.559
<v Speaker 1>And here's where it gets even more interesting. As your

607
00:31:54.599 --> 00:31:59.920
<v Speaker 1>security center or ASSE also leverages alerts. It's part of

608
00:32:00.079 --> 00:32:04.920
<v Speaker 1>its threat detection capabilities. Asc our Security Watchdog exactly. We

609
00:32:05.039 --> 00:32:09.160
<v Speaker 1>talked about it secure score recommendations and threat protection features

610
00:32:09.200 --> 00:32:12.599
<v Speaker 1>earlier we did how do alerts fit into that picture?

611
00:32:12.839 --> 00:32:17.839
<v Speaker 2>So ASC is constantly monitoring your Azure environment for security threats. Okay,

612
00:32:18.079 --> 00:32:24.000
<v Speaker 2>analyzing logs, network traffic, user behavior. When it detects something suspicious,

613
00:32:24.240 --> 00:32:28.079
<v Speaker 2>it triggers a security alert, providing detailed information about the

614
00:32:28.079 --> 00:32:31.640
<v Speaker 2>potential threat. Okay, it's severity and the affected resources.

615
00:32:31.839 --> 00:32:34.039
<v Speaker 1>So it's like having a security expert looking over our

616
00:32:34.079 --> 00:32:38.039
<v Speaker 1>shoulder is alerting us to any potential dangers exactly. But

617
00:32:38.079 --> 00:32:40.519
<v Speaker 1>we don't just want to know about threats. We want

618
00:32:40.559 --> 00:32:42.319
<v Speaker 1>to take action to neutralize them.

619
00:32:42.480 --> 00:32:44.960
<v Speaker 2>Absolutely, and that's where action groups come in again.

620
00:32:45.079 --> 00:32:45.359
<v Speaker 1>Okay.

621
00:32:45.599 --> 00:32:49.680
<v Speaker 2>You can configure ASC to trigger specific actions when a

622
00:32:49.720 --> 00:32:52.680
<v Speaker 2>security alert is fired. Okay, So, for example, you could

623
00:32:52.680 --> 00:32:58.240
<v Speaker 2>automatically isolate a compromised virtual machine, block malicious IP addresses,

624
00:32:58.920 --> 00:33:02.200
<v Speaker 2>or even initiate security incident response workflow.

625
00:33:02.359 --> 00:33:05.799
<v Speaker 1>Wow. So we're combining the intelligence of ASC with the

626
00:33:05.839 --> 00:33:09.640
<v Speaker 1>automation capabilities of action groups exactly to create a robust

627
00:33:09.720 --> 00:33:11.079
<v Speaker 1>security response system.

628
00:33:11.200 --> 00:33:15.759
<v Speaker 2>That's right. It's about proactively identifying threats, okay, responding quickly,

629
00:33:16.000 --> 00:33:18.559
<v Speaker 2>and minimizing the impact of any security incidents.

630
00:33:18.680 --> 00:33:20.839
<v Speaker 1>This has been an incredible journey through the world of

631
00:33:20.880 --> 00:33:23.839
<v Speaker 1>Azure management. It has been We've covered so much ground,

632
00:33:24.160 --> 00:33:27.640
<v Speaker 1>from the foundational concepts of governance and monitoring to the

633
00:33:27.799 --> 00:33:33.079
<v Speaker 1>powerful capabilities of automation, security, and even disaster recovery.

634
00:33:33.319 --> 00:33:34.000
<v Speaker 2>It's been a lot.

635
00:33:34.079 --> 00:33:37.920
<v Speaker 1>Yeah, We've explored the tools, the techniques, and the strategies

636
00:33:38.400 --> 00:33:42.599
<v Speaker 1>that empower you to manage your Azure environment effectively, efficiently,

637
00:33:42.720 --> 00:33:46.039
<v Speaker 1>and securely. I feel like I've gained a whole new

638
00:33:46.160 --> 00:33:49.640
<v Speaker 1>level of understanding and appreciation for the complexities and the

639
00:33:49.680 --> 00:33:51.400
<v Speaker 1>possibilities of Azual management.

640
00:33:51.599 --> 00:33:54.839
<v Speaker 2>It is complex, but it's also incredibly powerful.

641
00:33:55.000 --> 00:33:56.200
<v Speaker 1>And that's just the beginning.

642
00:33:56.400 --> 00:34:00.559
<v Speaker 2>It is. The cloud is constantly evolving, right, and so

643
00:34:00.640 --> 00:34:02.599
<v Speaker 2>are the tools and techniques for managing it.

644
00:34:02.680 --> 00:34:03.640
<v Speaker 1>That's true, It's.

645
00:34:03.480 --> 00:34:06.799
<v Speaker 2>An ongoing journey of learning, adapting, and optimizing.

646
00:34:07.000 --> 00:34:11.480
<v Speaker 1>I'm excited to continue this journey, exploring new features, experimenting

647
00:34:11.519 --> 00:34:14.480
<v Speaker 1>with new approaches need too, and pushing the boundaries of

648
00:34:14.519 --> 00:34:15.760
<v Speaker 1>what's possible in Azure.

649
00:34:15.800 --> 00:34:19.159
<v Speaker 2>Absolutely, and remember, you're not alone on this journey, right, Okay.

650
00:34:19.199 --> 00:34:23.840
<v Speaker 2>There's a vibrant community of Azure experts, resources and documentation

651
00:34:24.000 --> 00:34:26.079
<v Speaker 2>to support you every step of the way.

652
00:34:26.239 --> 00:34:30.440
<v Speaker 1>That's reassuring. I'm feeling inspired and empowered to tackle any

653
00:34:30.480 --> 00:34:32.400
<v Speaker 1>Azure management challenge that comes my way.

654
00:34:32.679 --> 00:34:35.159
<v Speaker 2>That's the spirit, go forth and conquer the cloud.

655
00:34:35.480 --> 00:34:37.679
<v Speaker 1>Thank you for joining us on this deep dive into

656
00:34:37.719 --> 00:34:38.400
<v Speaker 1>Azure management.

657
00:34:38.519 --> 00:34:39.239
<v Speaker 2>It's been a pleasure.

658
00:34:39.320 --> 00:34:41.119
<v Speaker 1>Until next time, Happy cloud managing.