Reference Architecture for multiple isolated apps
I would like a published reference architecture that describes the best practices for publishing multiple web applications in Isolated App Service Plan(s).
We want to host multiple web applications with different networking needs:
- Internal LoB applications.
- Internet facing applications.
- There are different application SQL Databases.
- Some applications should not be able to access use resources within the vNET belonging to other applications.
The single subnet per ASE relationship seems to force our hand to dictate multiple vNETs with multiple (costly) isolated plans. Am I missing something?
In the reference architecture, I would like guidance on when is the sharing of an Isolated Service Plan recommended or discouraged?