You plan to deploy the Azure Monitor agent to 100 on-premises servers that run Windows Server. Which parameters should you provide when you install…

To deploy the Azure Monitor agent (AMA) to non-Azure environments such as on-premises servers, the host machines must first be registered as Azure Arc-enabled servers. When deploying at scale across 100 on-premises Windows servers, non-interactive authentication is required during the deployment script execution. This requires providing the client ID and client secret of an Azure Active Directory (Microsoft Entra ID) service principal created specifically for Azure Arc onboarding. The service principal authenticates the automated installation and registers each server with Azure Arc. Once registered to Azure Arc, the Azure Monitor agent extension can be deployed and managed centrally from the Azure portal.

B. Storage account credentials are used for storage access and do not authenticate Azure Arc onboarding or agent installation on hybrid machines.

C. Azure SQL Database connection strings provide database access and play no role in server onboarding or monitoring agent deployment.

D. Workspace ID and workspace keys were required for the legacy Log Analytics agent (MMA), whereas Azure Monitor agent relies on Azure Arc identity.

- Microsoft Learn: "Azure Monitor Agent overview - Prerequisites for hybrid environments", Section: "Non-Azure machines", Doc ID: azure-monitor-agent-overview.

- Microsoft Learn: "Connect hybrid machines to Azure at scale using a service principal", Section: "Create a Service Principal for onboarding at scale", Doc ID: connect-at-scale-service-principal.