1
00:00:00,940 --> 00:00:04,520
New Hybrid Features in Windows Server 2022.

2
00:00:04,520 --> 00:00:08,260
Let's take a look at what we're going to cover. We're going to look at Azure

3
00:00:08,260 --> 00:00:14,090
Arc‑enabled servers and also Automanage. This allows a good hybrid

4
00:00:14,090 --> 00:00:19,590
environment and for you to control your on‑premises machine for Microsoft

5
00:00:19,590 --> 00:00:23,090
Azure. Let's begin with Arc‑enabled servers.

6
00:00:23,090 --> 00:00:28,470
A large benefit to Windows Server 2022 is the hybrid capability.

7
00:00:28,470 --> 00:00:34,710
Azure Arc‑enabled servers allow you consistency on your management through the

8
00:00:34,710 --> 00:00:39,640
Azure portal. You can manage your Windows and Linux physical servers and VM

9
00:00:39,640 --> 00:00:44,990
hosted outside of Microsoft Azure. Your Arc‑enabled servers are treated just

10
00:00:44,990 --> 00:00:50,670
as another resource, and each one of these has a resource ID that can be

11
00:00:50,670 --> 00:00:56,230
identified and differentiates it in Microsoft Azure. Let's go in and enable a

12
00:00:56,230 --> 00:00:59,140
server for Azure Arc.

13
00:00:59,140 --> 00:01:04,090
We begin right here in the Microsoft Azure Home page. Notice up here I

14
00:01:04,090 --> 00:01:07,790
have Azure Arc. That's because I've used it recently.

15
00:01:07,790 --> 00:01:11,740
If it's not up there, you can search for it in the search menu.

16
00:01:11,740 --> 00:01:16,050
I'm going to click on Azure Arc, and this opens up the page for

17
00:01:16,050 --> 00:01:19,220
Azure Arc, and we use this page to set this up.

18
00:01:19,220 --> 00:01:22,220
Notice down here we have Servers, and that's what we

19
00:01:22,220 --> 00:01:24,410
need, so let's go ahead and click on it.

20
00:01:24,410 --> 00:01:28,220
It says no servers in Arc, and we're going to fix that.

21
00:01:28,220 --> 00:01:33,100
We just click on Add, and this brings up some options here.

22
00:01:33,100 --> 00:01:36,710
We have a single server, we have multiple servers,

23
00:01:36,710 --> 00:01:40,900
we can add servers from Update Management, and add servers

24
00:01:40,900 --> 00:01:45,040
from Azure Migrate. We're going to select a single server and

25
00:01:45,040 --> 00:01:47,330
then click on Generate script.

26
00:01:47,330 --> 00:01:51,520
Were first met with the prerequisites. Basically, it makes sure that your

27
00:01:51,520 --> 00:01:57,610
server can connect to Microsoft Azure with HTTPS. You have a local

28
00:01:57,610 --> 00:02:02,550
administrator permission on that server, and you have the connectivity,

29
00:02:02,550 --> 00:02:05,190
along with an existing resource group.

30
00:02:05,190 --> 00:02:10,340
Well, we have all of those, so let's go ahead and continue by clicking Next.

31
00:02:10,340 --> 00:02:13,000
We don't need a lot of information in order to connect our

32
00:02:13,000 --> 00:02:16,670
server and start managing it with a familiar Microsoft Azure

33
00:02:16,670 --> 00:02:19,290
interface. We'll need a subscription,

34
00:02:19,290 --> 00:02:26,570
we got that, a resource group, which in our case will be RG‑AzureArcServers. We

35
00:02:26,570 --> 00:02:31,480
need to know the region, and we're going to use the default East US. Scrolling

36
00:02:31,480 --> 00:02:36,960
down, we can select the connectivity method, and if that is all set, we click

37
00:02:36,960 --> 00:02:39,960
Next. We have the option to apply tags.

38
00:02:39,960 --> 00:02:46,080
It's good to note where your servers are in the world because Microsoft

39
00:02:46,080 --> 00:02:50,360
Azure doesn't necessarily know where they are, so adding a tag for the

40
00:02:50,360 --> 00:02:52,940
location or data center is a good idea.

41
00:02:52,940 --> 00:02:57,240
We're not going to add any tags at this time, so let's click Next.

42
00:02:57,240 --> 00:02:58,550
Here's our script.

43
00:02:58,550 --> 00:03:01,550
You can run the script anyway you would like to, but

44
00:03:01,550 --> 00:03:03,270
I'd like to show you the easiest way.

45
00:03:03,270 --> 00:03:08,110
Let's go ahead and select all, copy the entire script, and then go to

46
00:03:08,110 --> 00:03:13,720
the PowerShell ISE. This is important. We have to right‑click and say

47
00:03:13,720 --> 00:03:19,950
Run as administrator, or this is not going to work. Now we simply paste

48
00:03:19,950 --> 00:03:23,340
the script in and hit Return.

49
00:03:23,340 --> 00:03:26,680
This runs the script and does everything in the background in order to

50
00:03:26,680 --> 00:03:32,600
connect our on‑premises server up to Microsoft Azure. It installs this

51
00:03:32,600 --> 00:03:37,650
local package after downloading it, and when it's done, we get this little

52
00:03:37,650 --> 00:03:42,680
line right here. It says open your web browser to this link and then enter

53
00:03:42,680 --> 00:03:44,940
this code. Simple as that.

54
00:03:44,940 --> 00:03:47,940
So let's go ahead and copy this link.

55
00:03:47,940 --> 00:03:54,080
Go to Microsoft Edge and paste it into the browser, and this brings

56
00:03:54,080 --> 00:03:56,970
this up where it says, well, give me the code.

57
00:03:56,970 --> 00:04:01,540
So let's go back to our ISE, copy the code,

58
00:04:01,540 --> 00:04:07,140
come back to Microsoft Edge, and then enter it. We'll click on Next,

59
00:04:07,140 --> 00:04:12,430
and it asks us for the credentials we need for Microsoft Azure. I'm

60
00:04:12,430 --> 00:04:15,760
going to go ahead and put in my credentials here, and it gives us a

61
00:04:15,760 --> 00:04:19,210
little warning sign. We get past that and then tells us go ahead and

62
00:04:19,210 --> 00:04:20,390
close the page.

63
00:04:20,390 --> 00:04:24,540
Now let's go back to the PowerShell ISE, and we can see right here,

64
00:04:24,540 --> 00:04:29,340
Successfully Onboarded this Resource to Azure.

65
00:04:29,340 --> 00:04:34,240
So let's go to our page, go to our Azure Arc,

66
00:04:34,240 --> 00:04:38,940
hit refresh, wait just a moment, and there it is.

67
00:04:38,940 --> 00:04:44,850
This server is now under the management of our Microsoft Azure page.

68
00:04:44,850 --> 00:04:48,060
We can treat it like any other resource that we have in Microsoft

69
00:04:48,060 --> 00:04:51,620
Azure. Let's go ahead and click on this server, and here we have an

70
00:04:51,620 --> 00:04:54,640
overview, and notice all the information on it.

71
00:04:54,640 --> 00:04:57,950
I'm going to scroll down, and this machine is truly

72
00:04:57,950 --> 00:05:01,140
treated as a Microsoft resource.

73
00:05:01,140 --> 00:05:04,290
We have managing logs, insights, policies,

74
00:05:04,290 --> 00:05:05,850
inventory, security,

75
00:05:05,850 --> 00:05:09,220
all the things that we would have with a regular

76
00:05:09,220 --> 00:05:11,900
Microsoft Azure virtual machine.

77
00:05:11,900 --> 00:05:12,970
The policy,

78
00:05:12,970 --> 00:05:20,470
that's a big deal, because if we want governance over our entire hybrid network,

79
00:05:20,470 --> 00:05:23,860
it's a good idea to consolidate all of that in one

80
00:05:23,860 --> 00:05:25,780
place, and that's what this does.

81
00:05:25,780 --> 00:05:37,000
So that is how you use Microsoft Azure Arc to connect to your Windows Server 2022 in order to have a more comprehensive hybrid environment.

