@Andoni Garrido Albizu If you have already configured the Private DNS zone associated with the VNet and you are still unable to call the backend API from the frontend app service with VNet integration, then there might be some additional configuration required.
Here are a few things you can check:
- Make sure that the VNet integration is set up correctly for the frontend app service. You can refer to the following documentation for more information on how to set up VNet integration for an app service: https://docs.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet
Check if the backend API is accessible from the subnet where the frontend app service is deployed. You can do this by deploying a VM in the same subnet as the frontend app service and trying to access the backend API from there.
Check if the backend API is accessible from the subnet where the VNet integration is set up. You can do this by deploying a VM in the same subnet as the VNet integration and trying to access the backend API from there.
Make sure that the Private Endpoint for the backend API is set up correctly. You can refer to the following documentation for more information on how to set up a Private Endpoint for an app service: https://docs.microsoft.com/en-us/azure/private-link/create-private-endpoint-portal
If you have checked all of the above and are still unable to call the backend API from the frontend app service with VNet integration, then you might need to troubleshoot further. You can refer to the following documentation for more information on how to troubleshoot VNet integration issues: https://docs.microsoft.com/en-us/azure/app-service/troubleshoot-vnet-integration-issues
Let me know the results of what Kapil and I shared so we can assist further if necessary.