[Autogenerated] now, let's look at Azure policy,
Guest configuration now,
I would recommend you look elsewhere on the Pluralsight library if you
need remedial instruction on Azure policy in general,
I'm going to assume, I have to assume that you have a basic understanding of it.
So as your policy is a way to enforce compliance in your Azure environment,
you've got compliance evaluation and enforcement using JSON
javascript object notation based policy definitions,
you can put guardrails on your Azure environment for example,
you might want to make sure that none of your colleagues
can deploy resources to unauthorized.
Azure regions you may want to enforce particular VM sizes,
you may want to ensure that the deployment will only succeed if
azure log analytics monitoring is enabled,
these sorts of things, you may also want to apply consistent taxonomic tax.
Now as your policy for Azure is fantastic but what if we
could apply Azure policy off cloud?
Well, guess what?
That's where Azure arc enabled servers come in we can use select Azure
policies with Azure arc enabled servers that are outside of Azure as well
as our Azure Native VMS And don't get me wrong,
azure policy applies to far more than VMS applies to anything in azure but
remember in this 800 context we're concerned with supporting Windows server
machines running both in azure as well as off.
Azure now as your policy guest configuration is a subset of
capability within as your policy Now as your policy deals
with the resources themselves,
the virtual machines themselves as objects or as resources as your policy.
Guest configuration extends.
Azure policy to the operating system settings of those monitored machines.
In a way,
guest configuration is very similar to PowerShell desired state configuration,
or PowerShell Dsc.
And as a matter of fact,
the options for Azure policy Guest configuration
includes simply auditing compliance,
as well as doing remediation that does use desired state configuration. Pretty cool.