azure/webapps-deploy@v3
Deploy Web Apps/Containerized Web Apps to Azure. github.com/Azure/Actions
At a glance
- Latest major
v3- Repository
- azure/webapps-deploy
- Inputs
- 13 (1 required)
- Outputs
- 1
- Runs using
node24- License
- MIT
- Last checked
Inputs and outputs come straight from the action's official action.yml. See our editorial standards.
Usage
- uses: azure/webapps-deploy@v3Inputs
| Name | Required | Default | Description |
|---|---|---|---|
app-name | Yes | none | Name of the Azure Web App |
publish-profile | No | none | Applies to Web Apps(Windows and Linux) and Web App Containers(linux). Multi container scenario not supported. Publish profile (*.publishsettings) file contents with Web Deploy secrets |
slot-name | No | production | Enter an existing Slot other than the Production slot |
package | No | . | Applies to Web App only: Path to package or folder. *.zip, *.war, *.jar or a folder to deploy |
images | No | none | Applies to Web App Containers only: Specify the fully qualified container image(s) name. For example, 'myregistry.azurecr.io/nginx:latest' or 'python:3.7.2-alpine/'. For multi-container scenario multiple container image names can be provided (multi-line separated) |
configuration-file | No | none | Applies to Web App Containers only: Path of the Docker-Compose file. Should be a fully qualified path or relative to the default working directory. Required for multi-container scenario |
startup-command | No | none | Enter the start up command. For ex. dotnet run or dotnet run |
resource-group-name | No | none | Enter the resource group name of the web app |
type | No | none | Enter deployment type (JAR, WAR, EAR, ZIP, Static) |
target-path | No | none | Target path in the web app. For ex. '/home/site/wwwroot' |
clean | No | none | Delete existing files target directory before deploying |
restart | No | none | Restart the app service after deployment |
sitecontainers-config | No | none | Applies to Sitecontainers, containes a list of siteContainer specs |
Outputs
| Name | Description |
|---|---|
webapp-url | URL to work with your webapp |
Read an output with ${{ steps.<step-id>.outputs.<name> }}; the step needs an id.
Examples
Deploy a folder to an App Service
Publish a built package to a Web App after `azure/login`.
name: Example
on:
push:
branches: [main]
permissions:
id-token: write
contents: read
jobs:
example:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- uses: azure/login@v3
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- name: Azure WebApp
id: deploy
uses: azure/webapps-deploy@v3
with:
app-name: my-web-app
package: dist
- name: Use the output
run: echo "webapp-url = ${{ steps.deploy.outputs.webapp-url }}"Each example passed actionlint (syntax, expressions and the inputs it knows for this action). They were not run in a live repository, so replace placeholder values such as names, ARNs and paths with your own.
Something out of date or wrong? Report it on our Contact page. This page is rebuilt from the action's repository roughly once a week.