I need to give staff in my organization access to a very simple web app. Users will select a few dropdown values, and the app will generate a sample file name. I don't expect significant traffic or server usage. The app is built with Node.js, and I'm wondering whether a free or very low-cost Azure VM is the best deployment option, or whether another Azure service would be simpler and more appropriate.
4 Answers
Azure App Service is probably a better fit than managing a VM yourself. It handles the hosting and maintenance, and the free tier may be sufficient for such a lightweight internal app. Just confirm whether Node.js is required at runtime or whether Node is only being used to build a static frontend. If it needs a live Node server, App Service is the more straightforward choice.
If the finished application is a static site or single-page app, Azure Static Web Apps would likely be simpler and cheaper than a VM. It can deploy from a source repository and is well suited to lightweight internal tools. The main limitation is that its Node.js support is more restricted than a full App Service environment, so it depends on how the app is built and hosted.
Azure Container Apps is another option if the application already runs cleanly in a container. Configure it to scale to zero when idle, which can keep costs very low for an app that is used occasionally. It adds more deployment complexity than Static Web Apps or App Service, so I wouldn’t choose it unless you’re already comfortable with containers.
For an internal application, don’t overlook authentication and access controls. App Service or Static Web Apps can integrate with organizational identity, while an existing on-premises app could potentially be published securely through an application proxy with conditional access policies. A VM would leave you responsible for more of the patching, security, networking, and availability work.
That distinction helps. The app may be mostly static, but I’ll verify whether the Node process is needed after the build.