Can't see VMSS from Application gateway in different resource group

Kristian Iliev 20

How can I make my Application Gateway from one resource group communicate with the Virtual machine scale set of another resource group in the same subscription? I have established Network Peering between the two virtual networks, but the Backend pools of the Application Gateway still can't locate the VMSS.

Ganesh Patapati 1,275 Reputation points Microsoft Vendor

2024-09-23T10:28:37.2933333+00:00

Hello Kristian Iliev,

Good day!

I'd like to continue with the thread.

Just dropping in to see if you had a chance to read my response to your query about correcting the issue. If you have any further concerns, please do not hesitate to contact us.

We are pleased to help you.

I look forward to your response and appreciate your time on this.

Regards,

Ganesh
Kristian Iliev 20 Reputation points

2024-09-24T06:50:31.51+00:00

Hello Ganesh,

Sorry for the late answer.

My idea is to use a gateway that is in different Vnet and different resource group. I am trying with vnet peering but cannot see the VMSS in the gateway.

I cannot set the IP directly because I would need to swap it manually if one of the VMs shutdowns.

If there is different way to set it up, I am open to suggestions as well!

Thank you!

Best regards,
Kristian
Ganesh Patapati 1,275 Reputation points Microsoft Vendor

2024-09-24T15:12:53.34+00:00

Hello Kristian Iliev,

Good day!

I Strongly recommend you go with PowerShell command for this scenario:

Refer: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking?tabs=powershell1#add-a-virtual-machine-scale-set-to-an-application-gateway

It might work for your solution, if not Please let us know so that we can drive further and get the required solution.

We are Pleased to Help you

Regards,

Ganesh
Kristian Iliev 20 Reputation points

2024-09-25T06:40:27.9133333+00:00

Hello Ganesh,

I have tried with the AZ CLI as well yesterday. It shows that the command is going trough but no targets are added...

Regards,
Kristian
Ganesh Patapati 1,275 Reputation points Microsoft Vendor

2024-09-25T18:03:08.31+00:00
Hello Kristian Iliev,

In most circumstances, it should work as described in the documentation, but we need to know how you configured it.

can you please send me how you had been configured in screenshot manner to better understanding thread in detail.

Regards,

Ganesh
Kristian Iliev 20 Reputation points

2024-09-26T06:26:59.4833333+00:00

Hello Ganesh,

Would it be convenient to have a meeting for easier explanation? Currently I have destroyed everything in order to prevent further cost but I still need to do it so I could create it again.

Best regards,
Kristian
Ganesh Patapati 1,275 Reputation points Microsoft Vendor

2024-09-26T18:59:33.3+00:00
Hello Kristian Iliev,

Good day!

No, we can't go for the meeting, please create it once again to better understand the query for the issue.

We are happy to assist to you

Regards,

Ganesh
Kristian Iliev 20 Reputation points

2024-09-27T13:19:53.0166667+00:00

Hello, Ganesh,

After I tried to replicate the issue I managed to Add the instances from the VMSS to the Gateway by following your link. I have chosen Azure CLI not Powershell and this time I used the Azure Cloud Shell.
A side note - The '*' in the provided command in the provided link was not working without double quotes for me.
Now finally I have my targets in the pool. I need to test and see if it works properly with scaling and etc..

Thank you for your help, @Ganesh Patapati
Ganesh Patapati 1,275 Reputation points Microsoft Vendor

2024-09-27T13:48:12.0533333+00:00
Hello Kristian Iliev,

Greetings,

I've turned my comment into an answer.

So please accept it and give it your best vote so that those in the community who are experiencing similar issues may quickly discover a solution.

We are very grateful for your contribution.

Best wishes,

Ganesh

Accepted answer

Ganesh Patapati 1,275 Reputation points Microsoft Vendor

2024-09-20T13:36:06.69+00:00
Hi Kristian Iliev,

Good day!

Welcome to the Q&A Platform for Microsoft. We appreciate you asking this question here.

We understand from your query that you are experiencing an issue while trying to Can't see VMSS from Application gateway in different resource group?

The Application Gateway needs to be in the Vnet as scale set, if not it will not show when you try to add it to a backend pool.

If you have VNet peering, you can just add the internal IP of the VM to target the backend pool.

A backend pool routes request to backend servers, which serve the request. Backend pools can contain:

Refer: https://learn.microsoft.com/en-us/azure/application-gateway/application-gateway-components#backend-pools

I Strongly recommend you go with PowerShell command for this scenario:

Refer: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking?tabs=powershell1#add-a-virtual-machine-scale-set-to-an-application-gateway

If the preceding response helps to solve your concern, please remember to "Accept Answer" and "Upvote it" so that others in the community with similar problems can easily find a solution.

Your contribution is greatly appreciated.

Regards,

Ganesh
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

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

Share via

Can't see VMSS from Application gateway in different resource group

0 additional answers

Your answer