By assigning a private endpoint the API, you need to verify that correct A and CNAME DNS records have been configured correctly in Azure DNS. From your front-end app service console, use these troubleshooting steps to verify your private endpoint configuration. Also check your access restriction rules on your app services to make sure that traffic isn't inadvertently being blocked and that your backend API allows traffic from the VNET. Leverage service tags to make the setup easier.
Connect two App Services under the P1V2 SKU Tier making a Frontend Public Access and Backend Private Only
So basically I have these requirements using the P1V2 SKU Tier on App Service Plan I need to network the following Web Apps.
- App Service (Frontend) should be accessible via the internet.
- App Service (API Backend) should only be accessible by the App Service (Frontend)
What I have successfully done is that the App Service (Frontend) is already accessible on the internet but it cannot access the App Service (API Backend). The networking I've done is on the App Service (Frontend) I set up an Outbound Traffic VNet Integration using subnetA and on the App Service (API Backend) I set up the Inbound Traffic Private endpoint using subnetB both of the subnetA and subnetB are using the same VNET.
I am fairly new with Azure and I don't have any idea why the Frontend could reach the Backend when in fact they are in the same VNET.
Azure App Service
1 answer
Sort by: Most helpful
-
Ryan Hill 30,276 Reputation points Microsoft Employee Moderator
2022-12-03T08:28:08.263+00:00