Score:0

Application gateway multi site set up

US flag

I have created a set up which uses application gateway to route traffic to app services. Below are the details:

  1. Application Gateway - 1
  2. Azure App Service - 2
  3. App Service Plan - 1
  4. VNET and one subnet

App Service - 1 for .net 5 web app, 1 for .net 5 api app

Both browse locally and after publishing to app service, for api app when browsed from Azure portal I have to append /swagger which then translates to https://mywebapiapp.azurewebsites.net/swagger/index.html

App Gateway Set up Backend pool 1 for App Target type: App Services Target: Selected my web app (azure app)

1 for Api Similar with Target azure app service name changed

Backend Setting enter image description here

Front end public IP is available

Listeners enter image description here

Listener Type is selected as Multi site

Rules

App rule enter image description here

Backend targets tab enter image description here

Similar set up for API Rule

Hosts file is updated

x.x.x.x www.fabrikam.com x.x.x.x www.xyz.com

When I browse fabrikam.com I end up in micorsoft.com/en-in/ not in my azure app hosting the .net 5 web app

First posted on StackOverflow here

Lucky avatar
md
Thank you so much for the edit
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.