Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
Points to note:
#1 "Subscription" is a logical grouping for billing, it does not dictate latency or connectivity.
#2 Azure Front Door ----> Azure Firewall traffic is going to happen via Public IP only, so placing the AFD in any specific VNET does not matter
Now, to address your queries:
1. Is it good practice to place FrontDoor under spoke subscription if we really want to achieve zero trust because when we use private link that will be spoke vnet only, so what is the best practice?
- As mentioned in #1, Front Door can be in any subscription - need not be in same subscription as Firewall.
- Can you elaborate on what do you mean by "use private link that will be spoke vnet only"
2. Is it good to have two FrontDoors, each for all non-Prod and Prod/DR or using one FrontDoor is good enough understanding our current and future need? Pros and Cons in each scenario?
- This completely depends on Billing and management overhead.
- The AFD, is completely capable of handling a huge volume of requests.
- You can use multiple domains with a single AFD for non-Prod and Prod/DR
3. Should we use Hub sbcription to deploy FrontDoor? Or we can still maintain the desired traffic flow FD—>Azure firewall—>app service by placing FrontDoor under spokes?
- Refer #2
4. If we also want to use API management service connecting to app service and Azure API Health services, how the traffic flow will look like (FD -> Azure Firewall -> API Management -> app service)? Also in which subscription we should place API management service (hub or spoke)?
- It is recommended to place the resource in the same VNET as the Azure Firewall if the resource is going to be integrated into VNET.
- Subscription does not matter as mentioned in #1
5. Is there by detailed documentation available to follow?
- You can follow : https://learn.microsoft.com/en-us/azure/architecture/example-scenario/security/hardened-web-app
As long as you are able to reach the PaaS service
- Via Public EndPoint
- or
- Via Peering/VNET Connection when the PaaS service is VNET Integrated.
This set up should be configurable.
Kindly let us know if this helps or you need further assistance on this issue.
Thanks,
Kapil
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.