Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Vanilla Blazor WebAssembly-App gets started locally on the iis the manifest gets deployed correct. If the Blazor WebAssembly-App gets deployed on azure the manifest gets missing. Browser shows

Manifest fetch from https://-------------------------------.azurewebsites.net/manifest.webmanifest failed, code 404

Because its missing the application can`t start as PWA.

Expected Behavior

Manifest should be there and in correct place

Steps To Reproduce

Create Blazor WebAssembly-App with PWA, deploy to azure

Exceptions (if any)

workaround or fix

.NET Version

10

Anything else?