You plan to use the legacy Azure Automation Update Management solution to patch 20 on-premises Windows Server 2019 machines. Requirements: centralize update assessment data in a single Log Analytics workspace; stop a custom service before patching and restart it afterward; enforce a 60-minute maintenance window. What should you configure?

To use the legacy Azure Automation Update Management solution, you must first create or link an Azure Automation account to a Log Analytics workspace. This workspace is essential for collecting and centralizing update assessment data from your on-premises servers. After linking, you enable Update Management for the workspace, which integrates the solution. Once Update Management is enabled, you create an Update Deployment. Within this deployment, you can configure pre- and post-scripts using runbooks to stop and restart your custom service, respectively. The maintenance window requirement of 60 minutes is set as the duration for this Update Deployment. Update Management Center is a newer solution and does not directly use Azure Automation runbooks for pre/post scripts in the same way the legacy solution does. Azure Policy Guest Configuration is for auditing and enforcing configurations, not for orchestrating update deployments with pre/post scripts. Windows Admin Center can manage updates but doesn't offer the centralized assessment and pre/post script capabilities required by this scenario in the same way Azure Automation does.