Your datacenter servers must be connected to Azure Arc through a corporate proxy that requires authentication. The estate includes Windows Server 2012 R2, Ubuntu 14.04, and RHEL 8. You need to ensure successful onboarding while meeting agent and network requirements. Which two actions should you take?

The correct actions are to enable TLS 1.2 and allow outbound HTTPS to Azure Arc service endpoints, and to configure the proxy using azcmagent proxy set with credentials. TLS 1.2 is a mandatory requirement for Azure Arc connectivity, and outbound HTTPS (TCP 443) is the standard communication port. Since the corporate proxy requires authentication, the azcmagent proxy set command is necessary to configure the agent with the proxy server details and credentials before onboarding. The legacy MMA agent is not required for proxy chaining with Azure Arc Connected Machine agent; the Connected Machine agent handles its own proxy configuration. While WPAD/PAC files can be used for proxy discovery, they do not support authenticated proxies, which is a requirement here. Ubuntu 14.04 is an End-of-Life operating system and is not supported by Azure Arc, making onboarding impossible.