How to create app services in azure

Table of Contents

1. What is Azure App Service
2. How to Create App Services in Azure
3. Different Types of Plans Available in Azure
4. Creation of a Deployment Slot
5. Deployment Slot
6. Deployment Centre
7. Creation of a Custom Domain
8. How to Deploy an App Service
9. How to Monitor an App Service
10. Application Insights
11. Video Tutorial ( 2 Videos )

Azure app service

Azure App Service is a platform as a service that is offered from Azure. Azure App Service enables the user to build and host web apps and mobile backend in the programming language of the user’s choice without managing infrastructure.

Therefore, Azure will manage the infrastructure and offers auto-scaling and high availability that supports both Windows and Linux. The user will be able to select an operating system of their choice and choose their desired programming language and the backend infrastructure will be maintained.

How to create app services in azure

The first step is to log into the Azure portal by using the user’s credentials. Under the list of services that are offered by Azure, the option called ‘App Services’ must be clicked in order to create an Azure App Service.

Once the option has been selected, it will redirect the user to another page requiring information to be filled in to create the new App Service. Project Details which consist of information such as Subscription and Resource Group must be chosen accordingly.

Likewise, once that has been done, the Instance Details must be filled in which consist of information such as Name, Publish (Code / Docker Container), Run Time Stack, Operating System, Region. The App Service Plan includes information such as Windows Plan and SKU & Size.

The next step is to Review and Create the App Service Plan. If any validation errors arise, the user must revert back to the information filled and make the necessary changes in order for the process of creating an App Service in Azure to be successful.

Different types of plans available in azure

There are Free, Shared, Basic, Standard, Premium, Isolated, and App Service Linux which are the various different types of plans that are available.

The capabilities of each of the plans are divided into the following types of limits –

1. Apps – The number of plans in the app that can be applied. The maximum number allowed will be specified under each time of plan that differs in quantity for each of the categories.
2. Disk Space
3. Max Instances
4. SLA
5. Functions on App Service Plans

Once the App Service has been deployed successfully, it can be entered into and go through the overview of the information available of the App Service.

Creation of a deployment slot

The option to create a Deployment Slot is located on the dropdown menu on the left-hand side of the screen of the App Service that has been created. To create a Deployment Slot, the user will need to have opted for a Premium or Standard plan.

This can be checked by using the option called ‘Scale-Out App Service Plan’ which is located on the same dropdown menu on the left-hand side of the screen of the App Service that has been created. There is an option for the process of Scale Up App Service Plan as well. If a custom domain is desired, it can’t be achieved with a shared infrastructure.

Deployment slot

Assuming a scenario where production comes after the scaling environment, then the user may choose to add a slot which will have to be named and where they would want to clone the settings from.

Deployment centre

In the Deployment Centre, the user will be able to see the FDP path and the recent activities performed. It contains Azure Repos, GitHub, or Bitbucket and the user will also be able to create a Continuous Deployment (CI / CD) and publish the code into the Azure App Service.

Custom domain

In the overview page for the App Service, it can be noted that the URL given will be from Azure and applied in default. In the case that the user does not wish to use this and desires for their personal custom domain, then a custom domain can be created. The custom domain can be configured through the option called ‘Custom Domain’ that is located on the dropdown menu on the left-hand side of the screen.

How to deploy an app service

The first step in this process is to log into the Azure portal with the user’s credentials. Go to the overview page of the Azure App Service that has already been created. By going into the URL of the App Service, it can be viewed that the App Service is up and running but the screen that is displayed will be the default page that has been provided by Microsoft for the App Services.

Before beginning the process of deployment of the App Service, repositories must be checked whether the appropriate application as per the run time chosen is available. This will be first deployed into the App Service.

On the dropdown menu located on the left-hand side of the screen, there is an option called ‘Deployment Centre’ which is to be clicked. There the user will be able to see CI / CD which is Continuous Integration and Continuous Delivery. The CI / CD can be set up for the App Service.

The repository where the code is stored will be required at first. The user will be able to take the core from multiple repositories like Azure Repos, GitHub, Bitbucket, or Local Git. If the authentication process already been complete, the user will then need to opt for a building service which can be from either App Service Build Service or the Azure Pipelines. If Azure Pipelines are selected, it will go and create a CI / CD.

The next step is the configuration part where Code information is required to be filled in. The Organisation, Repository, and Branch must be specified.

The last step is the overview of the Summary after which the process of setting up deployment is complete. This will take a while to be finished. In the background, it basically compiles the core application and pushes it into the App Service. When this is going on, the status will show ‘Pending’ and the page is refreshed to check whether the deployment has been successful.

Changes and edits can be made in the Git Repository in order for the changes to reflect in the App Service. Any changes made in the Git must be committed. Refreshing the URL again is the method to check whether the same is reflected in the App Service.

How to monitor an app service

On the dropdown menu located on the left-hand side of the App Service screen, there is an option called ‘Application Insights’ which is to be clicked.

Application insights

Application Insights – Application Insights is a feature of Azure Monitoring and is an extendable Application Performance Management (APM) Service. It will capture the application telemetric details that are necessary to the application in order to be hosted in Azure. The user can capture an insight using Application Insights.

If the Application Insights option hadn’t been turned on during the deployment process, it can be done so by clicking on the option to enable it. When it is turned on, it will expect information pertaining to the resource to be created if the user wishes to create a new resource, some of which are as follows –

1. New Resource Name – A default name will be provided which can be changed.
2. Location

An existing resource can also be opted for otherwise.

It will take a while to create the Application Insight. Once completed, it can be opened to see several metrics such as the failed requests, response time and availability of the user etc. These data can be recovered of the last thirty minutes or one hour and so on.

Video Tutorial-1

Video Tutorial-2