We begin here on the home page of Microsoft Azure portal. I have our machine
that is Arc enabled right here, and I'm going to click on it.
It gives us an overview, tells us the resource group,
the operating system,
our subscription, and here we have the FQDN a of the machine.
Now I want to explain this. We have the name up here.
This is because I've changed the name since enabling Arc server on
this. So there is the discrepancy between this name for the
computer name and then the resource name,
which is right here.
If I would have changed the name before I enabled Arc server,
then these would match.
On the left‑hand side, we have all the things that we can do to this server.
This is a little bit different than your normal Azure virtual machine.
We don't have all the features of a normal Azure virtual
machine on here, but we have quite a few.
Let's go through these one by one.
We have the activity log. We haven't had any activities on this
server since installing it for Arc capabilities.
But if we did, our activity log would show up here.
This is something interesting, access control, or IAM. With this,
we can take our Azure Active Directory users and groups and
assign them access to this on‑premises machine.
If we want to do that, we come right down here to Add role assignment,
click on it.
These roles are a little bit different than an Azure VM.
We have the usual Owner, Contributor, and Reader, and as I scroll down, we
can see all the different roles that we have here. We're going to come up
and pick one, Reader here, and then click Next.
Here's where we can select what users have this particular role.
I'm going to come up here to where it says Select
members, and there are our members.
Audra Costa. We have a group, FrancePartners. We have
individual accounts and groups inside of here.
So if I wanted to assign this to Audra, I click right here,
say Select, and then click Next. As simple as that, say Review +
assign, and we've just added an Azure AD account to a role on our
on‑premises server. Coming a little further down,
we have Tags.
If we wanted to assign tags, we can do it right here.
Going down to Diagnose and solve problems, I have one problem inside of here.
This machine was shut off for a little while, and Azure
couldn't contact it, so it says Unavailable.
I can download the report here, and it asks me, Did you resolve this issue?
I'm going to just say Yes.
So with the Azure Arc through Microsoft Azure portal,
we can actually see some of the problems that we had on here.
I'm going to come down to Security, click on it, and this
is going to be a little bit different.
We need the Microsoft Defender for Cloud in order for this to work.
This is not your normal Microsoft Defender that we have locally on the machine.
We have some extensions, and if we wanted to add an extension,
we could do so here by clicking on Add, which gives us the
option of a Custom Script Extension,
Log Analytics Agent, or an SQL Server Extension, which
furthers the capability of Azure Arc.
We're going to come back to our server,
go down to Properties, and what I want to highlight here is the resource
ID. Within Microsoft Azure, we've got a resource ID.
This is treated as a resource on Microsoft Azure,
but we're in a hybrid environment.
Its on‑premises. A lock.
If you're unfamiliar with this, you have two types of lock,
read only and do not delete.
What this is meant to do is protect our resource from somebody coming in
here and deleting it or making changes to it. Scrolling down a little bit
further, we have Policies. We're 100% compliant because we don't have any
kind of policies inside of here.
If we wanted to assign a policy,
we come right here to Assign policy and click on it.
Our policy definitions can be accessed by clicking on this button, and
it gives us allowed locations and a whole bunch more.
You can see there's 874 at this recording. I'm going to click on Cancel
and we're going to move on by clicking on here and going back to our
servers. Update management is something that requires an automation
account. For an automation account, we don't have one at this time, so
we're going to create one.
We come up here to Home,
I have accessed it before, so it's right here, Automation Accounts, but I'll
show you how to search for this. Type in auto, Automation Accounts right here.
Create automation account in order to create this.
It doesn't require very much information.
We're going to put it in our resource group for Arc servers.
We're going to enter a name,
just my name, garygrudzinskas. I'm going to click on Next, and
we're going to assign this through the system.
We can also assign it through the user. Click on Next,
which states how do we contact this server,
public or private?
We're going to take the default here of Public access. Skip over
Tags, and then say Create. It takes just a little bit, and we can
see it's complete. And once we go to our automation account, we
can access it right here.
If we wanted to turn on Update Management for this particular account,
we select this, Update management.
We can create a new workspace and enable it right here.
It takes just a little bit to deploy this.
The deployment has succeeded, so we're going to come back to our
server and then come down here to Inventory.
If we need inventory,
we go back to our automation account and enable change tracking,
and this will come down here to change tracking,
which will keep track of any changes we've made to our machine.
Last thing to show you is this Resource health,
which tells us okay, this machine is healthy, this machine is not healthy,
So there is a general overview of how you use Azure Arc in order to control your on‑premises Windows Server 2022.