Azure Automation Account Introduction Overview

Azure Automation Account Overview
Azure Automation delivers a cloud-based automation and configuration service that supports consistent management across your Azure and non-Azure environments. It comprises process automation, configuration management, update management, shared capabilities, and heterogeneous features. Automation gives you complete control during deployment, operations, and decommissioning of workloads and resources.
Process Automation
Process Automation in Azure Automation allows you to automate frequent, time-consuming, and error-prone cloud management tasks. This service helps you focus on work that adds business value. By reducing errors and boosting efficiency, it also helps to lower your operational costs. The process automation operating environment is detailed in Runbook execution in Azure Automation.
Process automation supports the integration of Azure services and other public systems required in deploying, configuring, and managing your end-to-end processes. The service allows you to author runbooks graphically, in PowerShell, or using Python. By using a Hybrid Runbook Worker, you can unify management by orchestrating across on-premises environments. Webhooks let you fulfill requests and ensure continuous delivery and operations by triggering automation from ITSM, DevOps, and monitoring systems.
Configuration Management
Configuration Management in Azure Automation allows access to two features:
Change Tracking and Inventory
Azure Automation State Configuration
Change Tracking and Inventory
Change Tracking and Inventory combines change tracking and inventory functions to allow you to track virtual machine and server infrastructure changes. The service supports change tracking across services, daemons, software, registry, and files in your environment to help you diagnose unwanted changes and raise alerts. Inventory support allows you to query in-guest resources for visibility into installed applications and other configuration items.
Azure Automation State Configuration
Azure Automation State Configuration is a cloud-based feature for PowerShell desired state configuration (DSC) that provides services for enterprise environments. Using this feature, you can manage your DSC resources in Azure Automation and apply configurations to virtual or physical machines from a DSC pull server in the Azure cloud.
Update management
Azure Automation includes the Update Management feature for Windows and Linux systems across hybrid environments. Update Management gives you visibility into update compliance across Azure and other clouds, and on-premises. The feature allows you to create scheduled deployments that orchestrate the installation of updates within a defined maintenance window. If an update shouldn't be installed on a machine, you can use Update Management functionality to exclude it from a deployment.
Shared capabilities
Azure Automation offers a number of shared capabilities, including shared resources, role-based access control, flexible scheduling, source control integration, auditing, and tagging.
Shared resources
Azure Automation consists of a set of shared resources that make it easier to automate and configure your environments at scale.
Schedules - Trigger Automation operations at predefined times.
Modules - Manage Azure and other systems. You can import modules into the Automation account for Microsoft, third-party, community, and custom-defined cmdlets and DSC resources.
Modules gallery - Supports native integration with the PowerShell Gallery to let you view runbooks and import them into the Automation account. The gallery allows you to quickly get started integrating and authoring your processes from PowerShell gallery and Microsoft Script Center.
Python 2 packages - Support Python 2 runbooks for your Automation account.
Credentials - Securely store sensitive information that runbooks and configurations can use at runtime.
Connections - Store name-value pairs of common information for connections to systems. The module author defines connections in runbooks and configurations for use at runtime.
Certificates - Define information to be used in authentication and securing of deployed resources when accessed by runbooks or DSC configurations at runtime.
Variables - Hold content that can be used across runbooks and configurations. You can change variable values without having to modify any of the runbooks or configurations that reference them.
#PaddyMaddy #cloudComputing #azuretutorial #microsoftazuretutorialforbeginners #azureforbeginners #azurebasics #microsoftazuretraining #Az900 #AZ500, #microsoftazurecertification, #AZ303 #az300 #az104 #paddyMaddy #azuretraining

[@PaddyMaddy26]

Azure Automation Account Overview

[@Youdont2012]

Can let me know difference netween automation accout vs service principal account

[@PaddyMaddy26]

Hello Youdont2012, Thank you for your question about the difference between automation accounts and service principal accounts. An automation account is used for managing automation jobs and runbooks in Azure Automation, which help streamline manual and repetitive tasks. These accounts are designed for automating deployment, scaling, and management of resources in Azure. On the other hand, a service principal account is used for authentication and authorization in Azure Active Directory. Service principals can be assigned roles and permissions to access Azure resources, and are often used for non-interactive or automated processes that need to interact with Azure APIs. In summary, automation accounts are specific to managing automation tasks, while service principal accounts are used for authentication and access control in Azure. I hope this explanation helps clarify the difference between the two types of accounts. Thank you for your interest and feel free to ask any further questions. Best regards, Paddymaddy

[@Youdont2012]

@@PaddyMaddy26 awesome explanation thanks much for the support

[@Youdont2012]

@@PaddyMaddy26 do you have videos created for azure with terraform Terraform supports a number of different methods for authenticating to Azure: Authenticating to Azure using the Azure CLI Authenticating to Azure using Managed Service Identity Authenticating to Azure using a Service Principal and a Client Certificate Authenticating to Azure using a Service Principal and a Client Secret (which is covered in this guide) Authenticating to Azure using a Service Principal and OpenID Connect

[@Youdont2012]

@@PaddyMaddy26 do you any videos on this below Terraform supports a number of different methods for authenticating to Azure: Authenticating to Azure using the Azure CLI Authenticating to Azure using Managed Service Identity Authenticating to Azure using a Service Principal and a Client Certificate Authenticating to Azure using a Service Principal and a Client Secret (which is covered in this guide) Authenticating to Azure using a Service Principal and OpenID Connect