I have created an azure app service(basic one, with a basic html page)
I have created Front Door, added as Front end, added App service as back end pool and created a rule which has 2 paths
/* and /path
I have this saved, so accessing from main front door open web app properly but opening from path /path throws error
"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
@RashmiSajjan-6545, Could you please share the screen capture of the routing rules and the error you are facing for further analysis.
Here is my front end configuration
BackEnd pool
Rule
One more rule
when I try to access "xxxx.azurefd.net/abc'
Directly accessing 'xxxx.azurefd.net/' works though I have removed /* rule from routing
Hello @RashmiSajjan-6545 ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
Are you able to access your webapp on the configured path directly bypassing the AFD?
If you want to access the backend pool (web app in your case) based on the path URL with Azure front door, you must make sure the virtual path exists on your web app. For example, you have to add the virtual directory /path (like /new in the below example) in your app service like this:
Refer : https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-path-mappings
So you could access your web app via URL https://xxx.azurewebsites.net/new.
Then you could add /new/ or /new* in the PATTERNS TO MATCH and modify the Forwarding protocol to match request in your routing rule of Azure Front door:
After this, you could access the URL frontdoor.azurefd.net/new for your web app.
For more reference: https://docs.microsoft.com/en-us/azure/frontdoor/front-door-route-matching
Kindly let us know if the above helps or you need further assistance on this issue.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Oh, I see... Its working now. Thank you so much
But these Path mapping are for windows app services only, this option is not available for Linux one
Does is need to be configured for every path that we add in routing configuration of front door?
If so , is there any limit of how many 'virtual path exists ' can be added to app service?
Hello @RashmiSajjan-6545 ,
Thank you for the update. Glad to hear that it is working now.
I checked with the App service team and they mentioned that for linux webapps, you need to go to the root folder and create a JSON for the path mapping. And as far as they know, there is no limit on the number of virtual paths in a webapp.
Still, I'm trying to get a more concrete confirmation on this and will update you once I receive any information around it.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Hello @GitaraniSharmaMSFT-4262 , Thanks for the response.
Does this configuration differ for Angular application?
It seem to working for normal app but for Angular app, it is not able to load components(works fine on normal app service endpoint)
As per some documentation I chose path as 'Redirect' and redirected to our website 
path is set as '/sonepar'
6 people are following this question.
