Missing options during deployment

Question

Dear Azure Community Support,

I am currently working on a CI/CD project where I am deploying a full-stack application (React frontend with a Node.js backend) using Azure DevOps and Azure App Service. The deployment pipeline completes successfully, and the App Service is running under a Basic (B2) plan. However, when I access the application URL, I only see the default Azure placeholder page (“Your web app is running and waiting for your content”) instead of my deployed frontend.

While following a learning tutorial, I noticed that the instructor selected a runtime stack option called “STATICSITE 1.0” in the App Service configuration to serve the frontend build files. In my Azure environment, this option is not available in the Runtime Stack list (I can only see Node, Python, Tomcat, etc.). Because of this, the static frontend content is not being served, even though the deployment artifacts are present.

I would like clarification on the following:

1. Has the STATICSITE 1.0 runtime stack been deprecated or removed from Azure App Service?
2. If so, what is the recommended modern approach to host and serve a frontend build alongside a backend API?

My goal is to follow the best-practice architecture rather than relying on outdated configurations, and I want to ensure I am using the correct Azure service for this deployment model.

Thank you for your guidance and support. I look forward to your response.

Best regards.

Answer 1

Hi @Naseer Hussain

The “STATICSITE 1.0” option shown in the tutorial is no longer a current App Service runtime. For React or other SPA frontends, the recommended approach today is to use Azure Static Web Apps, and keep your Node.js API on Azure App Service.

The “Your web app is running and waiting for your content” page usually means App Service isn’t serving the React build output (for example, build/ or dist/), even if the pipeline succeeds.

Best practice is:

• React frontend > Azure Static Web Apps

• Backend API >Azure App Service (Node.js)

Reference:

https://learn.microsoft.com/en-us/azure/static-web-apps/deploy-react?pivots=github

https://learn.microsoft.com/en-us/azure/static-web-apps/

lease do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you

 

Answer 2

1. The STATICSITE 1.0 runtime stack option is not mentioned in the current Azure documentation, and it appears that Azure Static Web Apps is the recommended service for hosting static frontends. Azure App Service is primarily designed for dynamic applications, and while it can serve static files, it may not have the same dedicated features as Azure Static Web Apps.
2. The recommended modern approach to host and serve a frontend build alongside a backend API is to use Azure Static Web Apps for the frontend and Azure App Service for the backend API. Azure Static Web Apps is specifically designed for static sites and single-page applications, providing features like automatic builds, custom domains, and integrated API support. You can deploy your React frontend to Azure Static Web Apps, while your Node.js backend can be hosted on Azure App Service. This separation allows for better scalability and management of both parts of your application.