Create an Azure App Service

This guide provides step-by-step instructions on how to create and configure an Azure App Service, a powerful platform for hosting web applications, REST APIs, and mobile backends.

Prerequisites


Steps to Create an App Service

1

Sign in to the Azure Portal

Open your web browser and navigate to the Azure portal (portal.azure.com). Sign in with your Azure account credentials.

2

Navigate to App Services

In the Azure portal search bar at the top, type "App Services" and select it from the results. Alternatively, click on the menu icon (three horizontal lines) in the top-left corner, then select App Services.

Click the + Create button or the Create App Service link to start the creation process.

3

Configure Basics

On the Create App Service page, you will need to configure the following settings:

  • Subscription: Select the Azure subscription to use for this App Service.
  • Resource Group: Choose an existing resource group or create a new one. Resource groups help you manage related Azure resources.
  • Name: Enter a unique name for your App Service. This name will be part of the default URL (e.g., your-app-name.azurewebsites.net).
  • Publish: Select how you want to deploy your application (e.g., Code, Docker Container, Static Web App). For this guide, we'll assume Code.
  • Runtime stack: Choose the programming language and version for your application (e.g., .NET, Node.js, Python, Java).
  • Operating System: Select the operating system for your App Service (Windows or Linux).
  • Region: Choose the Azure region closest to your users for optimal performance.
Note: The App Service name must be globally unique across Azure.
4

Configure Hosting Plan

Next, you'll configure the App Service Plan, which defines the compute resources, OS, region, and pricing tier for your application.

  • App Service Plan: Select an existing plan or create a new one.
  • Operating System: This should match the OS selected in the Basics tab.
  • Region: This should match the region selected in the Basics tab.
  • Pricing tier: Choose a pricing tier that fits your needs and budget (e.g., Free, Basic, Standard, Premium). The pricing tier determines features like custom domains, SSL certificates, and scaling options.

Click Next: Deployment >.

5

Configure Deployment (Optional)

You can configure continuous deployment from various sources like GitHub, Azure DevOps, or Bitbucket here. For now, we can skip this or set it up later.

Click Next: Monitoring >.

6

Configure Monitoring

Enable Application Insights to gain insights into your application's performance and usage. You can create a new Application Insights resource or use an existing one.

Click Next: Networking >.

7

Configure Networking (Optional)

Configure network access rules, such as enabling a public endpoint or configuring VNet integration, if required.

Click Next: Tags >.

8

Configure Tags (Optional)

Tags are key-value pairs that help you organize your Azure resources. You can add relevant tags here.

Click Next: Review + create >.

9

Review and Create

Review all the settings you have configured. If everything looks correct, click the Create button.

Tip: You can also use the Azure CLI to create an App Service. Here's an example command:
az appservice create --name my-unique-app-name --resource-group my-resource-group --plan my-app-service-plan --runtime "python|3.9"
10

Deployment and Access

Azure will now deploy your App Service. This process typically takes a few minutes. Once deployed, you will see a notification indicating that the deployment is complete.

You can then navigate to your App Service resource. On the overview page, you'll find the default URL (e.g., your-app-name.azurewebsites.net) to access your newly created App Service.

From here, you can proceed to deploy your application code using various methods like FTP, Git, or CI/CD pipelines.

Next Steps

Note: This documentation covers the basic creation process. Azure App Services offers a wide range of advanced configurations and features. Refer to the official Azure documentation for more in-depth information.