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.
Related
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
My company has a direction to create web app to be published and sold on Azure Marketplace.
After reading up on the topic on https://azure.microsoft.com/en-us/marketplace/programs/certified/, I am confused that what is actually the right way to achieve what we want to do above.
Do we need to create a VM as a container for our webapp so that it can be sold on Market Place? In this method, are subscribers creating their own VM service from the image we publish? I wonder how are updates/fixes being pushed out to every subscriber.
I then came across AppSource. In this way, are we creating/hosting the app in our azure app service, and users are authorized into the app through AAD (it looks like we have to use AAD authentication?)? Are we able to segregate user data by say, organizations?
I really appreciate if someone can shed some light on this.
For point 1, you could look at this question: Publishing a web application on Azure
i think what you are looking for is the "solution template". it took me a while to get it, but if you look at the docs there is a comparison between "Virtual machine" and "Solution template".
From the docs:
VM example:
As an Azure publisher, you've created and validated a VM with an innovative database service. Other Azure subscribers want to procure and deploy this VM into their cloud service environments.
Solution template example
As an Azure publisher, you've bundled a set of services from across Azure that make it quick to deploy cloud services with load balancing, enhanced security, and high availability. Other Azure subscribers can save time by procuring the solution template that meets their objective. They don't have to manually locate, procure, deploy, and configure the same or similar Azure services.
When I publish an api to azure from visual studio I see an existing app-service plan and also an option to create a new plan. The api I am going deploy will be used by the web application which was deployed using the existing service.
I have the following questions:
If I use the existing plan what would happen to the sites which are
already deployed using that plan?
Should I create new or use
existing?
Cost-wise which is the best option?
By using the same service plan to host the web app and the api, nothing will happen to the existing website besides you won't have any extra cost. The web apps will share the same resources.
If you create a new service plan for you api, you will have extra cost depending on the pricing tier you need.
The choice can depend on your scaling needs. If you need to define differents scaling plan for the api and the web app, it's a good idea to use two services plan, if not an unique service plan can be used.
I'm currently use azure in trial mode. I created a web app that use "South Central US" location. As far as I could see when I created this, I could not select anything else than South Central US, I would like to change this to north Europe. How do I do that?
Recently, I meet the same question. After I investigated the azure app service documents, I found I can use "Clone APP" feature to conveniently deploy my web app to another region.
Choose "Change APP Service Plan", and add a new premium service plan (So that I can use "Clone APP" feature).
Choose "Clone APP", then I can clone my app to another region.
Change the service plan to original and delete the other service plan.
You can't simply pick a new region for your web app: It resides within an app service plan within a given region.
To deploy into a different region, you'd need to create a new app service plan in that target region, then redeploy your app there. If you're taking advantage of built-in source code management (e.g. github), redeployment should be fairly straightforward.
Your question around which regions your subscription exposes is off-topic: That's something you'll need to open a billing support ticket and discuss directly with Azure support about.
It is very simple to change the location instead of cloning or redeploy your app. Here is the process to change app service plan for the existing and running Web app
Step 1:
Create new App service plan as your preferred location and pricing tier
Step 2:
Select change app service plan under your web app settings blade - app service section and choose your available app service plan just you created in step 1. now it updates your plan.
Step 3:
Delete the previous app service plan from your resource group, otherwise charges will apply for the previous associated app service plan.
I'm new to Azure, and a stronger developer than a network guy. I have read that you can host multiple websites/domains in each Basic plan.
I choose the B1 Basic plan for one of my web apps and it is deployed. I have others currently under the free option, all in the same resource group.
Do I just upgrade the others to B1 Basic, and it will treat them as one financially?
When reading online I see references to VMs and instances...which confuse me. So I'm not sure if its more complicated than that, requiring additional components and/or configuration?
A thorough explanation would be great.
The cost of Web Apps, or any other app that's part of App Service, is tied to something called App Service Plans. Apps are always associated with one App Service Plan and you are billed for the App Service Plans in your subscription, e.g. you will be billed for the same amount regardless if you have one Web App in a Free tier App Service Plan and one Web App in a Basic tier or if the Basic tier App Service Plan contained 10 Web Apps.
The number of apps you can host within an App Service Plan depends on your requirements and the pricing tier, see the documentation for subscription limits.
Apps can also be freely moved between App Service Plans, so if your apps need to the use the features offered in the Basic tier you can move them into a Basic tier App Service Plan.