Having trouble launching my Blazor Web Application using Azure Web App

Question

Having trouble launching my Blazor Web Application using Azure Web App

Andrew Sabin 40

Hello Azure Support Team,

I decided to recreate my Blazor WASM + ASP.NET Core application as a Blazor Web App due to how much faster it is in performance.

Blazor Web App Description.PNG

However, I am still seeing the Your web app is running and waiting for your content screen after setting the application up with Azure Web App, setting up the necessary environment variables, having a successful deployment from my GitHub Repository, and setting the startup application to be the server application. I have looked into the Log files, and I have not found any kind of issues going on there.

Is there anything that can be done to help me out with getting my Web Application running on the Azure Web App?

Thank you very much for your help and time,

Andrew Sabin

Ajay Rathod 170 Reputation points Microsoft External Staff Moderator

2026-07-23T22:45:45.89+00:00

Hi @Andrew Sabin

Greetings for the day, Thanks for reaching out Q&A.

We are working on it and we will get back to you shortly.

Thanks,

Ajay Kumar
Ajay Rathod 170 Reputation points Microsoft External Staff Moderator

2026-07-23T23:12:35.4033333+00:00

Hi @Andrew Sabin

Thanks for sharing the details.

From what you've described, your Blazor WASM + ASP.NET Core application was successfully migrated to a Blazor Web App, and the GitHub deployment completed without errors. However, instead of your application, App Service displays "Your web app is running and waiting for your content."

This message is the default Azure App Service page. Since your deployment logs don't show any errors, it usually means that App Service isn't able to find or start your application's server project. This is commonly caused by the published files being deployed to the wrong location or by the startup configuration not matching the new Blazor Web App.

Here are a few things to check:

"Publish an app in Release configuration and deploy the contents of the bin/Release/{TARGET FRAMEWORK}/publish folder, where the {TARGET FRAMEWORK} placeholder is the target framework."

1. Verify the deployed files

Open the Kudu File Manager:

https://<your-app>.scm.azurewebsites.net/newui/fileManager

Then browse to site/wwwroot.

At the root of wwwroot, you should see your server application's DLL (for example, <YourServerApp>.dll) along with the _framework folder.

If you only see hostingstart.html or your application files are inside another folder, then the deployment output is likely going to the wrong location.

2. Configure the Startup Command (Linux App Service only)

If your App Service is running on Linux, go to:

App Service → Configuration → General settings

Set the Startup Command to:

"dotnet <YourServerApp>.dll"

Save the changes and restart the App Service.

3. Verify the .NET runtime version

Go to:

App Service → Configuration → General settings → Stack settings

Make sure the configured .NET version matches the target framework of your application. After updating it, save the changes and restart the App Service.

If you find that the published files are nested inside another folder, the long-term fix is to update your GitHub Actions workflow so that the server project's publish output is deployed directly to the App Service root (site/wwwroot).

You can also refer to the Microsoft documentation on deploying Blazor applications to Azure App Service:

https://learn.microsoft.com/aspnet/core/blazor/host-and-deploy/server/

Thank you

Your answer

Ajay Rathod 170 Reputation points Microsoft External Staff Moderator

2026-07-23T22:45:45.89+00:00

Hi @Andrew Sabin

Greetings for the day, Thanks for reaching out Q&A.

We are working on it and we will get back to you shortly.

Thanks,

Ajay Kumar