What is the difference between "Azure Web app" and "Azure App Service"? - azure

I'm quite new to Azure, trying to learn how to explore what are the possibilities of publishing a website on azure, to be a bit more at ease to do the the AZ-204.
On the azure dashboard, I can create "Azure web apps", "Azure app service"(not mentionning CI/CD and serverless).
What are the difference between the two? I initially taught the azure web app was code driven(connected to git) and "App Service" one was docker-based.
But for both option, when you move to next step, you can choose if you publish the code or the docker container:
Can some body explain what is the difference between the two? And/or the most important advantage of one over the other?
I've searched for a while, but it's not the same product name everytime and I'm really sure it's still the same product.

There is no difference. To quote the documentation:
The only difference between the three app types (API, web, mobile) is
the name and icon used for them in the Azure portal.
Behind the scene it is already using app service all the time. If you consider WebApp and WebApp for containers is a part of Appservice, you don't actually pay for webApps, but you pay for the Appservice plan!

If you go to the Azure Web Apps site and click on the Documentation tab, it will take you to the MS Documentation for App Service Overview. Furthermore take a look at the MS Documentation Choose an Azure compute service for your application. This is a decision flowchart to host your application code. Azure Web Apps does not appear in the decision tree. Next take a look at the following subtopic Create and deploy web app service with Azure CLI command. The CLI command is as follows: "az webapp up --name <your_app_name> --logs --launch-browser". A little confusing but not if you look at the following documentation Azure CLI Documentation: Azure Web Apps, which shows the following commands:
az staticwebapp - Manage static apps.
az webapp - Manage web apps.
Finally, look at the following MS Documentation: CLI samples for Azure App Service. This is a list of numerous scripts for creating an Azure Service Plan and App Service. They ALL use either "az staticwebapp" or "az webapp". So the documentation use the term "Azure App Service" but the CLI command does not. There is no separate MS product for Azure Web Apps!

Web app is a part of App service.
There are 4 types of App Services:
Web App – used for hosting websites and web applications (previously Azure Websites)
API App – used for hosting the RESTful APIs
Logic App – used for business process automation, system integration and sharing data across clouds
Mobile App – used for hosting mobile app back ends (previously delivered by Azure Mobile services)

Azure runs App Services on a fully managed set of virtual machines in either a dedicated or shared mode, based on your App Service Plan. ... Web App – used for hosting websites and web applications (previously Azure Websites) API App – used for hosting the RESTful APIs.

Related

Understanding Azure Release Pipeline

I'm very new with Azure DevOps and I need some help to understand how to create a Release Pipeline. The Microsoft Doc is very extensive but I can't find what I'm looking for.
I've created a Build Pipeline with the sample python repository. Then I would like to create a Release Pipeline. I linked my account with my subscription, select the App type, but then I'm asking for App service name.
What is this App service ? How can I create it ?
On their documentation (here) they are just saying
App Service Name: Select the name of the web app from your subscription..
No more explanation.
Could someone please give me more information about that ?
Thanks a lot
An Azure DevOps release pipeline deploys the artifacts that are the output of a build pipeline to some environment that you define (Test, QA, Production, etc.).
For web apps the environment will be a "web hosting" (for other apps it could be something different).
The "web hosting" can be a 3rd party (you would deploy using tasks for FTP, WebDeploy, etc.) or it can be Azure "web hosting" PaaS offering, which is named Azure Web Apps.
Azure Web Apps require an Azure App Service Plan (which defines its characteristics and pricing): https://azure.microsoft.com/en-us/pricing/details/app-service/windows/
Note: an Azure App Service can be used not only to host web apps but also to host the back-end (Web APIs) of mobile apps, containers and serverless functions apps. See App Service overview and for high scale and security see Introduction to the App Service Environments
The template for the Release Pipeline that you have chosen (assuming is the one named "Deploy a Python app to Azure App Service and Azure database for MySQL") is intended to "Deploy a Python Django, Bottle, or Flask application to an Azure Web App and database to Azure Database for MySQL." Since it's deploying to an Azure Web App, the task asks you for its Azure Subscription and its App Service Plan within that subscription.
So, if you plan to deploy to an Azure Web App, create a Service Plan in your Azure subscription (you can use the Azure Portal, Azure CLI, etc.). Otherwise remove the task and use a different task to deploy to your 3rd party web hosting.
If you are new to Azure DevOps and want to try out all the cool things, I suggest you to follow Azure DevOps Labs which has a great content to get started from Zero to Advanced.

What should be configured on Azure before publishing an ASP.NET Core web application?

I have an ASP.NET Core MVC application along with Entity Framework Core. Now I would like to host that application in Azure. I am new to Azure, so I don't know what needs to be configured on Azure before publishing the application to Azure.
Like Sajeetharan said you can quickly publish your ASP.NET MVC Application in Azure easily from Visual Studio itself.
But you need to understand how this actually works within azure
WebApps
The service which is used to host every Web Application (PaaS) is called Azure Web
Web.
App Service Plan
An App Service plan is the container for your app. The App Service plan settings will determine the location, features, cost and compute resources associated with your app. The Cost is based on the App Service plan and not the WebApps
While publishing your web applications in Azure, is nothing but just deploying your code to WebApps.
Update 1
Happy Coding !
You do not have to configure anything, if you already have an Azure subscribe just connect to your azure account via visual studio and create a new Web App to publish your code.
Read more here
Create an ASP.NET Core web app in Azure

Can Azure CloudServices (Web Role) be provisioned using ARM Template? [duplicate]

My understanding so far on PaaS deployment using WebRoles or Worker Roles-
Spinning Web roles or Worker roles will create Cloud service to manage it.
However, in ARM resource group, their is no concept of Cloud service, then how are web & worker roles managed in ARM resource group?
Also I tried adding the webroles via JSON Outline in VS 2015, but no option to add webroles. So not sure if you can deploy webroles via JSON template?
Any information will be of great help.
Cloud Services have been around since the beginning of Azure.
To the deploy or manage them, you have to use the old APIs (Azure Service Management).
As far as I know, they won't be migrated to the new APIs (Azure Resource Manager), but you could use Virtual Machine Scale Sets instead.
Azure Resource Manager Web apps rely on the concept of App Service Plans, rather than cloud services. Basically this is the underlying VM(s) that the service runs on. You can specify the size and number of servers that make up the App Service plan, and then deploy on to those as a single unit.
You create an App service plan, then run web / worker roles inside that (as well as Logic, API, Functions)
As far as Web / Worker roles are concerned, App Service Plans do not draw a distinction between the two. You simply deploy code to it and it will run it however it is packaged. See here
The concept of cloud services simply don't exist within the Azure Resource Management model.
You can find a template for deploying a Web App here

Azure Cloud Services and Web Jobs

I have an Azure cloud service in which there are multiple background processing tasks which I would like to turn into WebJobs. I've read all I could find on the subject but it seems that WebJobs are tightly related to Web Apps and not Cloud services. I managed to create a web job in my cloud service solution and it seems it deployed correctly but I can't find a way to see it or its output on the new Azure portal (I couldn't see it in the classic management portal either)
Can one have a set of WebJobs running with a cloud service?
Web Jobs is a feature specific to Azure Web Apps. You'd need to create a Web App (in an App Service Plan) to create your Web Jobs. These are unrelated to Cloud Services (web/worker roles).

How to create or see existing App Service Plans in Azure portal and modify them?

I am trying to determine Azure portal provides any option to create an App Service Plan in a separate step (not while creating the website) and to modify them.
Currently I am creating App Service Plans in the WebSite creation step and modify them in WebSite's Scale option.
Is there any way to create them separately and see a list of available
App Service Plans?
Do websites created within an App Service Plan share the resources in it (CPU, Memory etc)?
What exactly happens when there is an auto scale up?
a.) Will it create a new instance of the App Service Plan and replicate all the websites within it?
b.) or will it create a new instance of the website and share the resources of same App Service Plan?
I am confused because, the App Service Settings (pricing tiers, scale-up option etc) are seen in websites scale option.
Please clarify my doubts.
Thanks in advance.
See page 8 of Developing Microsoft Azure Solutions Exam Reference for 70-532.
"Web hosting plans are created as part of website creation and are not created directly"
Even though this book was published in Feb 2015 some of the terminology is already out of date. It's an "application service plan", not "web hosting plan". And they call what is now known as a "web app" a "website".
Here is an awesome blog post about setting up azure web apps and deployment slots and hosting plans. It goes over what's shared and how to migrate between application service plans about halfway through.
Found this article which explains about App Service Plans in detail.

Resources