
Principal Cloud Solutions Architect
Azure Arc-enabled servers are a solution for managing Windows and Linux physical servers and virtual machines outside of Azure, such as on a corporate network or another cloud provider. In Azure Arc, these externally hosted machines are considered "hybrid machines". Azure Arc allows for consistent management and integration with standard Azure constructs like Azure Policy and tag application.
To establish a connection from hybrid machines to Azure, the Azure Connected Machine agent needs to be installed on each machine. This agent doesn't take the place of the Azure Log Analytics agent/Azure Monitor Agent, which is necessary for proactive monitoring of the OS and workloads on the machine, its management using Automation runbooks or solutions like Update Management, and utilization of other Azure services like Microsoft Defender for Cloud.
The Log Analytics agent or Azure Monitor Agent for Windows can be installed either manually, or on a large scale across many machines, based on the deployment method that suits a given scenario best. Once a hybrid machine is connected to Azure, it's identified as a connected machine and seen as a resource in Azure, with a dedicated Resource ID which allows the machine to be included in a resource group.
The goal of Azure Arc-Enabled servers is to simplify complex and distributed environments across on-premises, edge and multi-cloud. Azure Arc extends Azure management to any infrastructure and allows Azure services to run anywhere. If you have servers that cannot be migrated to Azure due to business or regulatory compliance requirements, you can still benefit from Azure's services without compromising on your unique needs.
The main topic is about Azure Arc-Enabled Servers, which allows the management of Windows and Linux physical servers and virtual machines hosted outside of Azure, on corporate networks or other cloud providers. These machines are considered as hybrid machines in the context of Azure Arc. The management approach for these hybrid machines is aimed to be consistent with management of native Azure virtual machines using Azure constructs like Azure Policy and tags.
Upon connecting a hybrid machine to Azure, it becomes a "connected machine" and is treated as an Azure resource, with each machine having a Resource ID for inclusion in a resource group. The connection is made possible by installing the Azure Connected Machine agent on the required machines. The agent can be installed manually or on multiple machines at scale, using the best deployment method for the scenario. Network requirements, supported environments, agent pre-requisites, and other details are covered.

Microsoft specialist, Azure professional, Microsoft solutions expert, Microsoft certified professional, Microsoft trained expert