How can we improve Azure Virtual Machines?

Azure VM Agent support for Forced Tunneling / User Defined Routes

To meet legal requirements, like many, we employ "forced tunneling", to push traffic through our proxy server. Many of your services, including agents are "Proxy Unaware" (like your developers!)

One possible way to overcome this, is to add a UDR to the special VM Agent IP of 168.63.129.16, however, when I try to create a route of 168.63.129.16/32, I get the below error, essentially saying it is in a restricted address space.

Please remove this restriction, post hast.

This is an incredibly quick and easy way to overcome your lack of proxy support with the VM agent.

Full error message:
Failed to add route 'DirectRouteToVMAgent' to route table 'UDR-TABLE-001'. Error: AddressPrefix 168.63.129.16/32 for route DirectRouteToVMAgent is not allowed because its in restricted address space.

2 votes
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Adrian Walker shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base