Deploy files to App Service


Starting June 1, 2024, all newly created App Service apps will have the option to generate a unique default hostname using the naming convention <app-name>-<random-hash>.<region> Existing app names will remain unchanged.


For further details, refer to Unique Default Hostname for App Service Resource.

This article shows you how to deploy your code as a ZIP, WAR, JAR, or EAR package to Azure App Service. It also shows how to deploy individual files to App Service, separate from your application package.


To complete the steps in this article, create an App Service app, or use an app that you created for another tutorial.

If you don't have an Azure subscription, create an Azure free account before you begin.

Create a project ZIP package


When creating the ZIP package for deployment, don't include the root directory, but only the files and directories in it. If you download a GitHub repository as a ZIP file, you cannot deploy that file as-is to App Service. GitHub adds additional nested directories at the top level, which do not work with App Service.

In a local terminal window, navigate to the root directory of your app project.

This directory should contain the entry file to your web app, such as index.html, index.php, and app.js. It can also contain package management files like project.json, composer.json, package.json, bower.json, and requirements.txt.

Unless you want App Service to run deployment automation for you, run all the build tasks (for example, npm, bower, gulp, composer, and pip) and make sure that you have all the files you need to run the app. This step is required if you want to run your package directly.

Create a ZIP archive of everything in your project. For dotnet projects, this is everything in the output directory of the dotnet publish command (excluding the output directory itself). For example, the following command in your terminal to create a ZIP package of the contents of the current directory:

# Bash
zip -r <file-name>.zip .

# PowerShell
Compress-Archive -Path * -DestinationPath <file-name>.zip

Deploy a ZIP package

When you deploy a ZIP package, App Service unpacks its contents in the default path for your app (D:\home\site\wwwroot for Windows, /home/site/wwwroot for Linux).

This ZIP package deployment uses the same Kudu service that powers continuous integration-based deployments. Kudu supports the following functionality for ZIP package deployment:

  • Deletion of files left over from a previous deployment.
  • Option to turn on the default build process, which includes package restore.
  • Deployment customization, including running deployment scripts.
  • Deployment logs.
  • A package size limit of 2048 MB.


Files in the ZIP package are copied only if their timestamps don't match what is already deployed.

With zip deploy UI in Kudu

In the browser, navigate to https://<app_name> (see note at top).

Upload the ZIP package you created in Create a project ZIP package by dragging it to the file explorer area on the web page.

When deployment is in progress, an icon in the top right corner shows you the progress in percentage. The page also shows verbose messages for the operation below the explorer area. When deployment completes, the last message should say Deployment successful.

The above endpoint doesn't work for Linux App Services at this time. Consider using FTP or the ZIP deploy API instead.

Without zip deploy UI in Kudu

Deploy a ZIP package to your web app by using the az webapp deploy command. The CLI command uses the Kudu publish API to deploy the files and can be fully customized.

The following example pushes a ZIP package to your site. Specify the path to your local ZIP package for --src-path.

az webapp deploy --resource-group <group-name> --name <app-name> --src-path <zip-package-path>

This command restarts the app after deploying the ZIP package.

Enable build automation for zip deploy

By default, the deployment engine assumes that a ZIP package is ready to run as-is and doesn't run any build automation. To enable the same build automation as in a Git deployment, set the SCM_DO_BUILD_DURING_DEPLOYMENT app setting by running the following command in the Cloud Shell:

az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings SCM_DO_BUILD_DURING_DEPLOYMENT=true

For more information, see Kudu documentation.

Deploy WAR/JAR/EAR packages

You can deploy your WAR, JAR, or EAR package to App Service to run your Java web app using the Azure CLI, PowerShell, or the Kudu publish API.

The deployment process shown here puts the package on the app's content share with the right naming convention and directory structure (see Kudu publish API reference), and it's the recommended approach. If you deploy WAR/JAR/EAR packages using FTP or WebDeploy instead, you might see unknown failures due to mistakes in the naming or structure.

Deploy a WAR package to Tomcat or JBoss EAP by using the az webapp deploy command. Specify the path to your local Java package for --src-path.

az webapp deploy --resource-group <group-name> --name <app-name> --src-path ./<package-name>.war

The CLI command uses the Kudu publish API to deploy the package and can be fully customized.

Deploy individual files

Deploy a startup script, library, and static file to your web app by using the az webapp deploy command with the --type parameter.

If you deploy a startup script this way, App Service automatically uses your script to start your app.

The CLI command uses the Kudu publish API to deploy the files and can be fully customized.

Deploy a startup script

az webapp deploy --resource-group <group-name> --name <app-name> --src-path scripts/ --type=startup

Deploy a library file

az webapp deploy --resource-group <group-name> --name <app-name> --src-path driver.jar --type=lib

Deploy a static file

az webapp deploy --resource-group <group-name> --name <app-name> --src-path config.json --type=static

Deploy to network-secured apps

Depending on your web app's networking configuration, direct access to the app from your development environment might be blocked (see Deploying to Network-secured sites and Deploying to Network-secured sites, Part 2). Instead of pushing the package or file to the web app directly, you can publish it to a storage system accessible from the web app and trigger the app to pull the ZIP from the storage location.

The remote URL can be any publicly accessible location, but it's best to use a blob storage container with a SAS key to protect it.

Use the az webapp deploy command like you would in the other sections, but use --src-url instead of --src-path. The following example uses the --src-url parameter to specify the URL of a ZIP file hosted in an Azure Storage account.

az webapp deploy --resource-group <group-name> --name <app-name> --src-url " --type zip

Kudu publish API reference

The publish Kudu API allows you to specify the same parameters from the CLI command as URL query parameters. To authenticate with the Kudu REST API, it's best to use token authentication, but you can also use basic authentication with your app's deployment credentials.

The following table shows the available query parameters, their allowed values, and descriptions.

Key Allowed values Description Required Type
type war|jar|ear|lib|startup|static|zip The type of the artifact being deployed, this sets the default target path and informs the web app how the deployment should be handled.
- type=zip: Deploy a ZIP package by unzipping the content to /home/site/wwwroot. target-path parameter is optional.
- type=war: Deploy a WAR package. By default, the WAR package is deployed to /home/site/wwwroot/app.war. The target path can be specified with target-path.
- type=jar: Deploy a JAR package to /home/site/wwwroot/app.jar. The target-path parameter is ignored
- type=ear: Deploy an EAR package to /home/site/wwwroot/app.ear. The target-path parameter is ignored
- type=lib: Deploy a JAR library file. By default, the file is deployed to /home/site/libs. The target path can be specified with target-path.
- type=static: Deploy a static file (such as a script). By default, the file is deployed to /home/site/wwwroot.
- type=startup: Deploy a script that App Service automatically uses as the startup script for your app. By default, the script is deployed to D:\home\site\scripts\<name-of-source> for Windows and home/site/wwwroot/ for Linux. The target path can be specified with target-path.
Yes String
restart true|false By default, the API restarts the app following the deployment operation (restart=true). To deploy multiple artifacts, prevent restarts on the all but the final deployment by setting restart=false. No Boolean
clean true|false Specifies whether to clean (delete) the target deployment before deploying the artifact there. No Boolean
ignorestack true|false The publish API uses the WEBSITE_STACK environment variable to choose safe defaults depending on your site's language stack. Setting this parameter to false disables any language-specific defaults. No Boolean
target-path An absolute path The absolute path to deploy the artifact to. For example, "/home/site/deployments/tools/driver.jar", "/home/site/scripts/". No String

Next steps

For more advanced deployment scenarios, try deploying to Azure with Git. Git-based deployment to Azure enables version control, package restore, MSBuild, and more.

More resources