Azure Front Door (premium) not working with new private endpoints

Question

We had a Front Door that was deployed last week that was working with an App Service that was secured with private endpoints. We were also creating a private endpoint from AFD --> App Service.

We deleted the AFD and created a new one today and now we cannot get that the endpoint set up again.

We get:

Our services aren't available right now
We're working to restore all services as soon as possible. Please check back soon.

20210802T214233Z-y0ebdkrzct3mp3fhmspkbmwkgg0000020020000000003vdm

We've been trying for most of the day to resolve this. We have deleted the entire application infrastructure and re-deployed - right now the app service is just serving an empty app service / welcome to app service page.

We have approved the private endpoint that AFD creates on the App Service.

We do see that it is trying to use the private endpoint from the AFD logs:

originUrl_s: https://privatehub-prod-xx01-xxx.privatehub.azureedge.net:443/

What are we missing? Was there any changes to break this functionality? We have added AFD with App Service and Private Endpoints dozens of times before with no major issues, but starting today we are not having any luck.

Answer 1

Through our support ticket, we found Microsoft rolled back a change so this is now resolved for us.

Answer 2

@Joshua Johanning , Azure Front Door private endpoints are available in the following regions during public preview: East US, West 2 US, South Central US, and UK South. Can you cross check with this limitation? Also, it is not recommended deploying this preview staged resource in your production environment.

----------

Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.