Azure DevOps new release pipeline is not deploying correctly to App service

Hi Steve Bullington

Could you please share the YAML File in private message if possible.

Since it is a Windows App Service deployment, ensure web.config is present. If web.config is missing or incorrect, the app won’t route correctly.

After the pipeline completes, connect to the App Service via Kudu (Advanced Tools) or FTP. In the Kudu console (https://<yourapp>.scm.azurewebsites.net/DebugConsole):

• Navigate to site/wwwroot
• Check for:
  • index.html
  web.config

If not present or nested incorrectly (e.g., site/wwwroot/dist/your-app-name/index.html), it won’t work.

Hope this helps!

Please Let me know if you have any queries.

Hi Steve Bullington

Could you please share the YAML File in private message if possible.

Meanwhile check if site/wwwroot/webconfig exists. If not, then create it as below:

<configuration>
  <system.webServer>
    <rewrite>
      <rules>
        <rule name="Angular Routes" stopProcessing="true">
          <match url=".*" />
          <conditions logicalGrouping="MatchAll">
            <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
            <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
          </conditions>
          <action type="Rewrite" url="/index.html" />
        </rule>
      </rules>
    </rewrite>
    <staticContent>
      <mimeMap fileExtension=".json" mimeType="application/json" />
    </staticContent>
  </system.webServer>
</configuration>

Check inside your deployed index.html

If you see something like <base href="/dist/">, the app won’t load correctly on Azure.

Then Set correct base path during build:

ng build --configuration production --base-href "/"

Try navigating directly to https://<yourapp>.azurewebsites.net/index.html. If that works, but https://<yourapp>.azurewebsites.net/ doesn’t, it’s definitely a default document or rewrite issue.

Then Go to your App Service in the Azure Portal -> Configuration -> Default Documents.

1. Ensure index.html is listed at the top of the default documents list.
2. If it’s missing or lower in priority, IIS might not serve it automatically.

Hope this helps!

Please Let me know if you have any queries.