Николоски Благоја, Firstly, apologies for the delayed response.
Based on my understanding of your scenario, you may look at these approaches outlined by my colleague, in this discussion thread:
- If the only public access is via the UI/Front end app and that app is "virtual network integrated" then the other apps can be access over a private endpoint and the access through the public endpoint for those other apps can be turned off.
- You have the option of using either Azure Front Door or Application Gateway which both have a Web-Application-Firewall (WAF) feature, if you need that extra layer of functionality in front of your apps. If you did then it would be possible to broker public access to the front end / UI through either Front Door or Application Gateway and have the rest of the network path private
Kindly take a look at these reference docs:
- Tutorial secure ntier app | Scenario architecture
- Tutorial: Authenticate and authorize users end-to-end in Azure App Service
Just to highlight, on custom container for Azure App Service, the following Docker Compose configuration options are unsupported.
Azure doc | Configure a custom container for Azure App Service | Unsupported options
- build (not allowed)
- depends_on (ignored)
- networks (ignored)
- secrets (ignored)
- ports other than 80 and 8080 (ignored)
- default environment variables like $variable and ${variable} unlike in docker
Kindly let us know, I'll follow-up with you further.
If the answer helped (pointed, you in the right direction) > please click Accept Answer - it will benefit community members to find the answers quickly.