You are planning the implementation Azure Arc to support the planned changes. You need to configure the environment to support configuration management policies. What should you do?

To use Azure Arc for configuration management policies on servers outside of Azure, you must first onboard them into the Azure control plane. This is accomplished by deploying the Azure Connected Machine agent to each server. This agent connects the machine to Azure, projecting it as an Azure resource. Once the server is an Azure Arc-enabled resource, you can leverage Azure management services like Azure Policy's Guest Configuration feature to audit and enforce configuration settings directly inside the machine's operating system.

A. Hybrid Azure AD join all the servers.

This option is incorrect because Hybrid Azure AD join is an identity feature for registering devices in Azure AD, primarily for single sign-on and conditional access, not for Azure Arc configuration management.

B. Create a hybrid runbook worker m Azure Automation.

This is incorrect. A Hybrid Runbook Worker is a component of Azure Automation used to execute runbooks on non-Azure machines, which is distinct from applying declarative configuration policies via Azure Policy.

D. Deploy the Azure Monitor agent to all the servers.

This is incorrect because the Azure Monitor agent's purpose is to collect monitoring data (logs and metrics) from the guest OS, not to enforce configuration management policies.

1. Microsoft Learn. "Azure Connected Machine agent overview." Azure Arc documentation. This document states

"The Azure Connected Machine agent enables you to manage your Windows and Linux machines hosted outside of Azure... After you've configured your machine with the Azure Connected Machine agent

you can... Assign Azure Policy Guest Configuration policies to audit settings on the machine."

2. Microsoft Learn. "What is Azure Arc-enabled servers?" Azure Arc documentation. This article clarifies

"When a hybrid machine is connected to Azure

it becomes a connected machine and is treated as a resource in Azure. Each connected machine has a Resource ID... and benefits from standard Azure constructs such as Azure Policy and applying tags." This establishes that the connection via the agent is the foundational step.

3. Microsoft Learn. "Understand Azure Policy's Guest Configuration feature." Azure Governance documentation. In the "Client" section

it specifies

"The configuration assignments are processed by the Guest Configuration extension for Azure virtual machines

or the Azure Connected Machine agent for Arc-enabled servers." This directly links the Connected Machine agent to the implementation of configuration policies.