[Autogenerated] thus far in the course we've been in Azure
automation so we've seen some of its capability,
Let's double-click now and there's going to be a little bit of review
from what we did in the previous module here and that's fine because
there's a principle of adult education,
I think repetition is great and repetition is also going to
help you lock in these concepts and skills For your as 800
certification exam success.
But let's look at azure automation,
run books configuration management or cm as a systems engineering
process with the goal of establishing consistency of a product's
attributes throughout its life cycle.
And the Azure automation account is our cloud based our Azure
cloud based configuration management solution for both Windows
and Linux systems in Azure and beyond.
Azure automation relies upon log analytics,
so you'll need a log analytics workspace as well as the log
analytics agent deployed to your machines.
Select capabilities include as we saw in the previous lesson,
update management, inventory, tracking, change tracking,
run books desired state configuration.
There's a lot here indeed.
The hybrid run book worker which you can deliver to your
off cloud machines via an extension, particularly your Azure arc enabled servers,
you can install the run book worker on them to extend.
Azure automation run books into your local data centers or other clouds though.
Azure automation was really built for hybrid cloud configuration management.
Specifically an Azure automation run book is simply a
cloud hosted automation script, you might think well wait a minute,
what's the difference between an Azure automation
run book and an Azure function, aren't they?
Both cloud hosted scripts well,
kind of specifically Azure automation run books are
meant for the IT professional really.
The operations person rather than the developer run books share
similarities with Azure functions in that you can trigger them manually
on a schedule or have them be triggered by an event.
And there is another similarity that both Azure functions and automation
run books support PowerShell or PowerShell workflow.
Workflow is a subset of power Shell's capability that allows
you to do more durable long running processes that
potentially could survive a restart.
Azure automation run books have a graphical option
that you do not get with functions.
Both run books can be python scripts as well as functions.
So yes,
there is some overlap between functions and run books but for
our purposes a hybrid cloud administrator,
we're concerned entirely with Azure automation run books.
So just know about functions and function apps just from a
theoretical standpoint like I mentioned,
the Azure automation.
Hybrid worker is what extends Azure automation run book services off cloud
into your local data center as well as in other environments.
Now there's two types of Azure automation.
Hybrid worker,
there's the system worker that's used and managed only by Azure and
it's used with the update management solution,
but then you can deploy user workers with a purpose like I said,
of extending your Azure automation run book executions to your hybrid cloud,
as you can see I know, the text is small and the diagram.
Right and again, I provide attribution for all of these borrowed diagrams.
We're dealing with TCP 443 and TLS encryption.
So the idea is that you don't need a site to site
VPN or virtual private network,
nor do you need an express route circuit in order to do this.
As I mentioned,
the preferred way to create hybrid worker instances is to deploy
with the hybrid run book worker VM extension.
So ideally your on premises or off cloud machine is arc enabled,
which gives you access to the VM extensions in Azure and you can deploy
the hybrid run book worker directly to that machine.
Lastly, you can create these logical groupings of hybrid worker agents.
These are called hybrid run book worker groups.
And the purpose of this is to provide high availability for your off cloud Azure automation run book jobs.