Hi, I've tried updating backendip-address in application gateway backend pool successfully. But, when tried the same for updating the Virtual machine in application gateway backend pool. It is throwing exception to check the syntax. Kindly let me know, how to add/remove the virtual machine in backend pool of application gateway using Azure-Cli. Thanks & Regards Bharath

@Bharath-FT , thank you for posting this question here. I understand that you are trying to update the backend pool of application gateway so that it can point to the VMs with your application installed. Edit 10/31/2022 The following are some resources that should help you with this issue: az network application-gateway address-pool - can be used to manage the address pools of an application gateway. The following link has samples to update, add and delete IPs from existing pools - az network application-gateway address-pool update . Note the use of index for removing existing IP address, while IP address is used for update or add. Please note that the routing in Application Gateway happens based on the IP/FQDN and not the VM Name. Therefore, the " VM Name " itself is not a valid type to be used for updating the backend addresses. For more details, please see How an application gateway routes a request and ApplicationGatewayBackendAddress in Application Gateway ARM Template Even in the portal, when updating the Application Gateway's backend pool, if Type is selected as Virtual machine --> the available options are NICs associated to that VM and not the VM itself . Please let us know if you have any questions.

Azure Cli command to add virtual machine in application gateway backend connection pool

Accepted answer

AnuragSingh-MSFT 21,466 Reputation points

2022-10-27T04:51:57.417+00:00

@Bharath-FT , thank you for posting this question here. I understand that you are trying to update the backend pool of application gateway so that it can point to the VMs with your application installed.

Edit 10/31/2022

The following are some resources that should help you with this issue:

az network application-gateway address-pool - can be used to manage the address pools of an application gateway. The following link has samples to update, add and delete IPs from existing pools -
az network application-gateway address-pool update. Note the use of index for removing existing IP address, while IP address is used for update or add.

Please note that the routing in Application Gateway happens based on the IP/FQDN and not the VM Name. Therefore, the "VM Name" itself is not a valid type to be used for updating the backend addresses. For more details, please see How an application gateway routes a request and ApplicationGatewayBackendAddress in Application Gateway ARM Template

Even in the portal, when updating the Application Gateway's backend pool, if Type is selected as Virtual machine --> the available options are NICs associated to that VM and not the VM itself.

Please let us know if you have any questions.
Please sign in to rate this answer.
Bharath-FT 21 Reputation points

2022-10-27T10:06:45.283+00:00

Hi Anurag,

Thanks for the reply.

For IP address update, it works successfully shown below
$ az network application-gateway address-pool update -g test_rg_bharath --gateway-name test_appgateway -n Backendpool --add backendAddresses ip_address=10...*

For Virtual Machine update, it fails with below
az network application-gateway address-pool update -g test_rg_bharath --gateway-name test_appgateway -n Backendpool --add VirtualMachine ip_address=10...*
Couldn't find 'VirtualMachine' in ''. Available options: ['backendAddresses', 'backendIpConfigurations', 'etag', 'id', 'name', 'provisioningState', 'type']

Note: I've tried the below command also, but is adding with ipaddress and not as Virtual machine
az network application-gateway address-pool update -g test_rg_bharath --gateway-name test_appgateway -n Backendpool --servers 10...*

Bharath-FT 21 Reputation points

2022-10-27T10:48:10.617+00:00

here the targetType="Virtual machine" is not working.
targetType="IPAddress" is working fine.

I need targetType="Virtual machine" to work.

AnuragSingh-MSFT 21,466 Reputation points

2022-10-28T07:45:05.99+00:00

@Bharath-FT , thank you for the clarification. Please note that the routing in Application Gateway happens based on the IP/FQDN and not the VM Name. Therefore, the "VM Name" itself is not a valid type to be used for updating the backend addresses. For more details, please see How an application gateway routes a request and ApplicationGatewayBackendAddress in Application Gateway ARM Template

Even in the portal, when updating the Application Gateway's backend pool, if Type is selected as Virtual machine --> the available options are NICs associated to that VM and not the VM itself.

Hope this helps. Please let me know if you have any questions.

Bharath-FT 21 Reputation points

2022-10-28T09:37:08.73+00:00

Hi Anurag,

Thanks for your support and clarification provided to my issue.
issue resolved now with Nic of VM.
Thanks once again.

Regards,
Bharath

Seth Gwartney 0 Reputation points

2024-08-27T22:43:58.68+00:00

Hi,

I know this is an old thread, but I have the same issue as the OP. I want to add the backend target by VM/NIC, not by IP address. I see no way to do this via the CLI or Rest API.

One reason I want to do this by NIC is this statement in another place in documentation: https://learn.microsoft.com/en-us/azure/load-balancer/backend-pool-management#limitations

When a backend pool is configured by IP address, it will behave as a Basic Load Balancer with default outbound enabled. For secure by default configuration and applications with demanding outbound needs, configure the backend pool by NIC.

In my workload, I want the benefits of "secure by default configuration" and "demanding outbound needs" for my pool configuration. So is there really no programmatic way to add the backend by NIC? I may only programmatically add the backend target by IP Address, and then only modify it to NIC in the UI? This doesn't seem right.

I understand not being able to use the "VM Name" in the CLI, but I can query and find the exact NIC/IPConfiguration resource I want to add - I just can't add it as a NIC type to the backend pool because there is no option for this in the CLI.

Any help would be appreciated!

Thanks,

Seth
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Cli command to add virtual machine in application gateway backend connection pool

0 additional answers

Your answer