1
00:00:01,040 --> 00:00:04,450
Let's take a look at a new feature with Microsoft

2
00:00:04,450 --> 00:00:08,040
Server 2022 called Azure Automanage.

3
00:00:08,040 --> 00:00:13,570
This is designed to simplify the IT management inside of the cloud. You apply

4
00:00:13,570 --> 00:00:19,210
consistent best practices across the entire lifecycle of a virtual machine

5
00:00:19,210 --> 00:00:22,840
because you can use the Azure Security Center.

6
00:00:22,840 --> 00:00:24,770
This will enhance reliability,

7
00:00:24,770 --> 00:00:28,610
security, and management for all of your virtual machines,

8
00:00:28,610 --> 00:00:31,640
both on‑premises and in the cloud.

9
00:00:31,640 --> 00:00:34,670
This works for both Linux and for Windows.

10
00:00:34,670 --> 00:00:38,740
One of the key features of Automanage is Hotpatch.

11
00:00:38,740 --> 00:00:44,140
Hotpatch establishes a baseline for planned and unplanned releases.

12
00:00:44,140 --> 00:00:49,540
A planned release is with the regular cadence of your updates.

13
00:00:49,540 --> 00:00:54,870
An unplanned release is if something happens and you have a 0‑day

14
00:00:54,870 --> 00:00:58,100
update that you've got to get on your server right away.

15
00:00:58,100 --> 00:01:04,620
Hotpatch differentiates the reboot and non‑reboot patches and automatically

16
00:01:04,620 --> 00:01:09,730
applies critical and security updates in the off hours.

17
00:01:09,730 --> 00:01:14,250
The benefits of hotpatching, servers don't have to reboot as much

18
00:01:14,250 --> 00:01:17,540
and this is the main benefit of hotpatching.

19
00:01:17,540 --> 00:01:22,870
Since we differentiate between what patches require a reboot and

20
00:01:22,870 --> 00:01:29,080
what patches don't require a reboot, then we can identify the ones

21
00:01:29,080 --> 00:01:31,090
that aren't going to need a reboot,

22
00:01:31,090 --> 00:01:36,000
apply them automatically, and then the patches that require reboot are going

23
00:01:36,000 --> 00:01:40,530
to be less frequent. Let's say you have a cumulative update and that

24
00:01:40,530 --> 00:01:45,840
cumulative update has 15 updates that don't require a reboot and one that

25
00:01:45,840 --> 00:01:51,400
does. Well, let's apply the ones that don't require it and then every once in

26
00:01:51,400 --> 00:01:54,640
a while or let's just say less frequently,

27
00:01:54,640 --> 00:01:58,110
you're going to apply the ones that require a reboot.

28
00:01:58,110 --> 00:02:01,480
Since the patches are differentiated a lot better,

29
00:02:01,480 --> 00:02:05,630
they come in smaller packages, so much faster deployment.

30
00:02:05,630 --> 00:02:10,400
We also have better protection through scoping and health signals. With

31
00:02:10,400 --> 00:02:15,650
hotpatching, you know what updates are applied and what updates might have

32
00:02:15,650 --> 00:02:18,740
run into trouble when they're trying to be applied.

33
00:02:18,740 --> 00:02:29,000
So that is a look at Automanage with Microsoft Azure for Windows Server 2022 Data Center Azure Edition.

