Hello @Matthew Jung
I understand that you would like to know how many flows an Azure Front Door can support.
May I know what are you referring as "flows"?
Is it the number of concurrent connections on Azure Front Door or maximum requests per sec or something else?
We don't officially publish these limits.
Azure Front Door has a very high limit, so connections are not a bottleneck. But if we see too many requests coming from same customer, we throttle it, as it might be an attack.
So, if you want higher limits, then you need to create a support request for same, and the support team can engage the AFD backend team to increase these limits.
Coming to the point where you mentioned "I can see all of requests are going to 13.107.246.**."
Azure Front Door uses Anycast IPs, so the IP addresses are the same globally. Traffic routed to the Azure Front Door edge locations uses Anycast for both DNS (Domain Name System) and HTTP (Hypertext Transfer Protocol) traffic.
Anycast is a network addressing and routing methodology in which a single destination IP address is shared by devices (generally servers) in multiple locations.
Also, sharing the best practices for Azure Front Door for your reference:
https://learn.microsoft.com/en-us/azure/frontdoor/best-practices
Kindly let us know if 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.