Azure Update Manager Implementation for On-Premises Environment with Limited Internet Bandwidth

We are planning to implement Azure Update Manager in an on-premises environment consisting of approximately 200 virtual machines, all joined to the abc.local domain. These VMs are currently managed within our local infrastructure and are not configured to communicate directly with the internet due to bandwidth constraints and high traffic sensitivity.

To ensure efficient patching and update management without saturating our outbound connection, we require a solution where a single on-premises server acts as a control point or proxy for update orchestration. The goal is to centralize communication with Azure Update Manager through this server, minimizing direct internet traffic from individual VMs.

We are seeking guidance on:

Recommended architecture for Azure Update Manager in this scenario.

Whether a proxy or gateway server can be configured to relay update metadata and instructions.

Network and firewall requirements to support this setup.

Integration considerations with our existing domain (abc.local) and group policies.

Best practices for update deployment scheduling and bandwidth optimization.

Thank you for your support.