Share via

Unable to deploy to new Azure App Services from the GitHub Actions webapps-deploy Action with OneDeploy

Andy Vanosdale 20 Reputation points
2026-02-07T17:12:19.9466667+00:00

Hi,

Sometime between Feb 1, 5:37 PM PST and Feb 6, 8:20 AM PST, I am seeing an issue deploying to new (Free) Azure App Services when using the GitHub Actions webapps-deploy Action. It is using OneDeploy behind the scenes.

This is what my step looks like:

   steps:
      runs-on: ubuntu-latest
      - name: Login to Azure
        uses: azure/login@v2
        with:
          client-id: ${{ secrets.azure-client-id }}
          tenant-id: ${{ secrets.azure-tenant-id }}
          subscription-id: ${{ secrets.azure-subscription-id }}
      - name: Deploy to Azure Web App
        id: deploy-to-webapp
        uses: azure/webapps-deploy@v3
        with:
          app-name: ${{ inputs.web-app-name }}
          slot-name: 'Production'
          package: package/package.zip

This is the output from the job run-

Run azure/webapps-deploy@v3
  
    app-name: <<app name>>
    slot-name: Production
    package: package/package.zip
Validating SPN Linux Web App inputs...
Predeployment Step Started
Deployment Step Started
Starting deployment for web app...
Package deployment using OneDeploy initiated.
Error: 
Error: 
Site Unavailable (CODE: 503)
App Service Application URL: <<app service URL>>

When I try to go to the SCM site, it also returns a 503 every time, so I can not see any deployment logs.

I have another Free App Service already running along with a Basic App Service, and both can be deployed to without any failures. I'm happy to share any details of the App Service configuration as well.

Thanks!

Andy

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

{count} votes

Answer accepted by question author
  1. Shree Hima Bindu Maganti 6,890 Reputation points Microsoft External Staff Moderator
    2026-02-08T08:43:25.45+00:00

    Hi @Andy Vanosdale
    The “Service Unavailable (503)” error during deployment with azure/webapps-deploy@v3 usually means the Azure App Service can’t process the request because of limited resources or platform issues. Deployments through GitHub Actions use the Kudu (SCM) endpoint, and if that’s also returning a 503 error, the deployment will fail. As noted in Microsoft’s documentation, “HTTP 503 Service Unavailable errors can occur when the app doesn’t have sufficient resources (CPU, memory, disk) to run or the platform is unable to allocate resources. Apps in lower tiers such as Free or Shared are subject to resource quotas that can result in a 503 if those quotas are exceeded.” Restarting the App Service may fix temporary resource problems, but if the issue continues, Microsoft suggests upgrading the App Service Plan to a higher tier for dedicated resources and to prevent quota-related errors.
    https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-http-502-http-503?utm_source=chatgpt.com
    Let me know if you have any further assistances needed.
    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


1 additional answer

Sort by: Most helpful
  1. Andy Vanosdale 20 Reputation points
    2026-02-11T06:06:25.4333333+00:00

    It looks like this was a Free-instance resource exhaustion issue. Sadly, the error message was extremely unhelpful and led to numerous rabbit holes trying to understand what the issue was. It would be great if there was a better error message and explanation used when there is a resource exhaustion.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.