Application Gateway in hub and spoke architecture

Shola Lawani 531 Reputation points Microsoft Employee
2020-09-30T12:35:00.523+00:00

Hello Experts,

when designing application gateway architecture in a hub and spoke architecture is it a supported scenario where an application gateway in the hub can be leveraged by the spokes (Production, staging and Development subscription) or each of the spokes should have its own application gateway?

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,180 questions
Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
965 questions
0 comments
Accepted answer
  1. suvasara-MSFT 10,011 Reputation points
    2020-10-01T09:54:17.33+00:00

    anonymous user , as long as you have connectivity between APPGW and backends in the spokes, you will be to implement path-based routing / URL based routing.

    Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andreas Baumgarten 97,731 Reputation points MVP
    2020-09-30T19:12:32.73+00:00

    The Application Gateway supports URL based routing.
    This way it's possible to route different URLs to different pools (e.g. /prod/, /stage/, /dev/*).

    Source: What is Azure Application Gateway?

    figure1-720.png

    In the first picture is a scenario with different VMS in Azure and on-premises. So my assumption is a "hub and spoke" architecture with different vNets/Subnets is suported.

    Source: Azure Application Gateway features

    figure1-720.png

    Maybe this is helpful.

    Regards
    Andreas Baumgarten

    (Please don't forget to Accept as answer if the reply is helpful)

    0 comments