Delete your Front Door and recreate it as I commented above.
Don't rush creating resources.
Otherwise, your Door will be a little bit confused.
As the product is under preview, this will be stable before GA, I think.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello, guys.
I'm trying to use Azure Front Door standard (preview) and have an issue.
Could you give me some hints?
My Front Door have 4 DNS domains. (named 1.example.com to 4.example.com for now)
And my backend is 2 VM that open same port numbers. (named backend-a and backend-b for now)
I created 4 origin groups like:
A for (backend-a:4000 + backend-b:4000)
B for (backend-a:4100 + backend-b:4100)
C for (backend-a:14000 + backend-b:14000)
D for (backend-a:14100 + backend-b:14100)
And I created 4 routes like
1.example.com to A
2.example.com to B
3.example.com to C
4.example.com to D
I expected that the traffic to 1.example.com is dispatched to the origin group A.
But actually the endpoint returns content in the origin group B.
Is this behavior from my misunderstandings? Or some inconsistency is happened in the cloud?
Thanks for your support.
Delete your Front Door and recreate it as I commented above.
Don't rush creating resources.
Otherwise, your Door will be a little bit confused.
As the product is under preview, this will be stable before GA, I think.