I currently have this scenario in Azure:

I need to host a Rabbit MQ UDP MQTT endpoint in a Container App environment fronted by a Internal Load Balancer that would be exposed publicly via Azure Front Door – However Azure Front Door does not support UDP MQTT while a External Load Balancer is.

One scenario that i tested is: Provision an External Load Balancer with a Backend rule pointing to a VM and where a reverse proxy is hosted that forwards the UDP traffic over to the RabbitMQ Container App.

Unfortunately, client policies prohibit the provisioning or utilization of any VMs. Is there a method to implement a Public-facing Load Balancer that can proxy UDP traffic to the Private Load Balancer?

I currently have this scenario in Azure:

I need to host a Rabbit MQ UDP MQTT endpoint in a Container App environment fronted by a Internal Load Balancer that would be exposed publicly via Azure Front Door – However Azure Front Door does not support UDP MQTT while a External Load Balancer is.

One scenario that i tested is: Provision an External Load Balancer with a Backend rule pointing to a VM and where a reverse proxy is hosted that forwards the UDP traffic over to the RabbitMQ Container App.

Unfortunately, client policies prohibit the provisioning or utilization of any VMs. Is there a method to implement a Public-facing Load Balancer that can proxy UDP traffic to the Private Load Balancer?