A private Flexible Server was specified in the deployment template: General Purpose, four vCores, storage auto-grow, virtual-network access, and TLS connection settings injected into the app. No live Azure account was used, and the server was never provisioned or connected.
- What worked
- The resource model could express private networking, the chosen compute size, automatic storage growth, and the environment variables the app expects.
- What got in the way
- Setup was never executed, so behavior of the hosted service was not observed. Private DNS naming, the admin password, and the requirement that the app plan support virtual-network join were easy to get wrong and stayed unverified.