App Service on Linux provides a highly scalable, self-patching web hosting service using the Linux operating system. This quickstart shows how to create a .NET Core app on App Service on Linux. You create the web app using the Azure CLI, and you use Git to deploy the .NET Core code to the web app.
You can follow the steps in this article using a Mac, Windows, or Linux machine.
If you don’t have an Azure subscription, create a free account before you begin.
To complete this quickstart:
Create the app locally
In a terminal window on your machine, create a directory named
hellodotnetcore and change the current directory to it.
md hellodotnetcore cd hellodotnetcore
Create a new .NET Core web app.
dotnet new web
Run the app locally
Restore the NuGet packages and run the app.
dotnet restore dotnet run
Open a web browser, and navigate to the app at
You see the Hello World message from the sample app displayed in the page.
In your terminal window, press Ctrl+C to exit the web server. Initialize a Git repository for the .NET Core project.
git init git add . git commit -m "first commit"
Open Azure Cloud Shell
Azure Cloud Shell is a free, interactive shell that you can use to run the steps in this article. Common Azure tools are preinstalled and configured in Cloud Shell for you to use with your account. Just select the Copy button to copy the code, paste it in Cloud Shell, and then press Enter to run it. There are a few ways to open Cloud Shell:
|Select Try It in the upper-right corner of a code block.|
|Open Cloud Shell in your browser.|
|Select the Cloud Shell button on the menu in the upper-right corner of the Azure portal.|
Create a deployment user
In the Cloud Shell, create deployment credentials with the
az webapp deployment user set command. This deployment user is required for FTP and local Git deployment to a web app. The user name and password are account level. They are different from your Azure subscription credentials.
In the following example, replace <username> and <password> (including brackets) with a new user name and password. The user name must be unique within Azure. The password must be at least eight characters long, with two of the following three elements: letters, numbers, symbols.
az webapp deployment user set --user-name <username> --password <password>
You should get a JSON output, with the password shown as
null. If you get a
'Conflict'. Details: 409 error, change the username. If you get a
'Bad Request'. Details: 400 error, use a stronger password.
You create this deployment user only once; you can use it for all your Azure deployments.
Record the user name and password. You need them to deploy the web app later.
Create a resource group
A resource group is a logical container into which Azure resources like web apps, databases, and storage accounts are deployed and managed. For example, you can choose to delete the entire resource group in one simple step later.
In the Cloud Shell, create a resource group with the
az group create command. The following example creates a resource group named myResourceGroup in the West Europe location. To see all supported locations for App Service on Linux in Standard tier, run the
az appservice list-locations --sku S1 --linux-workers-enabled command.
az group create --name myResourceGroup --location "West Europe"
You generally create your resource group and the resources in a region near you.
When the command finishes, a JSON output shows you the resource group properties.
Create an Azure App Service plan
The following example creates an App Service plan named
myAppServicePlan in the Standard pricing tier (
--sku S1) and in a Linux container (
az appservice plan create --name myAppServicePlan --resource-group myResourceGroup --sku S1 --is-linux
When the App Service plan has been created, the Azure CLI shows information similar to the following example:
"adminSiteName": null, "appServicePlanName": "myAppServicePlan", "geoRegion": "West Europe", "hostingEnvironmentProfile": null, "id": "/subscriptions/0000-0000/resourceGroups/myResourceGroup/providers/Microsoft.Web/serverfarms/myAppServicePlan", "kind": "linux", "location": "West Europe", "maximumNumberOfWorkers": 1, "name": "myAppServicePlan", < JSON data removed for brevity. > "targetWorkerSizeId": 0, "type": "Microsoft.Web/serverfarms", "workerTierName": null
Create a web app
In the Cloud Shell, you can use the
az webapp create command. In the following example, replace
<app_name> with a globally unique app name (valid characters are
-). The runtime is set to
dotnetcore|2.0. To see all supported runtimes, run
az webapp list-runtimes --linux.
az webapp create --resource-group myResourceGroup --plan myAppServicePlan --name <app_name> --runtime "dotnetcore|2.0" --deployment-local-git
When the web app has been created, the Azure CLI shows output similar to the following example:
Local git is configured with url of 'https://<username>@<app_name>.scm.azurewebsites.net/<app_name>.git' "availabilityState": "Normal", "clientAffinityEnabled": true, "clientCertEnabled": false, "cloningInfo": null, "containerSize": 0, "dailyMemoryTimeQuota": 0, "defaultHostName": "<app_name>.azurewebsites.net", "deploymentLocalGitUrl": "https://<username>@<app_name>.scm.azurewebsites.net/<app_name>.git", "enabled": true, < JSON data removed for brevity. >
You’ve created an empty web app in a Linux container, with git deployment enabled.
The URL of the Git remote is shown in the
deploymentLocalGitUrl property, with the format
https://<username>@<app_name>.scm.azurewebsites.net/<app_name>.git. Save this URL as you need it later.
Browse to your newly created web app. Replace <app name> with your web app name.
Here is what your new web app should look like:
Push to Azure from Git
Back in the local terminal window, add an Azure remote to your local Git repository. Replace <deploymentLocalGitUrl-from-create-step> with the URL of the Git remote that you saved from Create a web app.
git remote add azure <deploymentLocalGitUrl-from-create-step>
Push to the Azure remote to deploy your app with the following command. When prompted for credentials by Git Credential Manager, make sure that you enter the credentials you created in Configure a deployment user, not the credentials you use to log in to the Azure portal.
git push azure master
This command may take a few minutes to run. While running, it displays information similar to the following example:
Counting objects: 22, done. Delta compression using up to 8 threads. Compressing objects: 100% (18/18), done. Writing objects: 100% (22/22), 51.21 KiB | 3.94 MiB/s, done. Total 22 (delta 1), reused 0 (delta 0) remote: Updating branch 'master'. remote: Updating submodules. remote: Preparing deployment for commit id '741f16d1db'. remote: Generating deployment script. remote: Project file path: ./hellodotnetcore.csproj remote: Generated deployment script files remote: Running deployment command... remote: Handling ASP.NET Core Web Application deployment. remote: ............................................................................................... remote: Restoring packages for /home/site/repository/hellodotnetcore.csproj... remote: .................................... remote: Installing System.Xml.XPath 4.0.1. remote: Installing System.Diagnostics.Tracing 4.1.0. remote: Installing System.Threading.Tasks.Extensions 4.0.0. remote: Installing System.Reflection.Emit.ILGeneration 4.0.1. remote: ... remote: Finished successfully. remote: Running post deployment command(s)... remote: Deployment successful. To https://cephalin-dotnetcore.scm.azurewebsites.net/cephalin-dotnetcore.git * [new branch] master -> master
Browse to the app
Browse to the deployed application using your web browser.
The .NET Core sample code is running in a web app with a built-in image.
Congratulations! You’ve deployed your first .NET Core app to App Service on Linux.
Update and redeploy the code
In the local directory, open the Startup.cs file. Make a small change to the text in the method call
await context.Response.WriteAsync("Hello Azure!");
Commit your changes in Git, and then push the code changes to Azure.
git commit -am "updated output" git push azure master
Once deployment has completed, switch back to the browser window that opened in the Browse to the app step, and hit refresh.
Manage your new Azure web app
Go to the Azure portal to manage the web app you created.
From the left menu, click App Services, and then click the name of your Azure web app.
You see your web app’s Overview page. Here, you can perform basic management tasks like browse, stop, start, restart, and delete.
The left menu provides different pages for configuring your app.
Clean up resources
In the preceding steps, you created Azure resources in a resource group. If you don’t expect to need these resources in the future, delete the resource group by running the following command in the Cloud Shell:
az group delete --name myResourceGroup
This command may take a minute to run.