In this demonstration will now going to go about creating our first app service plan in the azure pool
too and we'll use this to deploy our web apps on top of later on.
So let's head over to the Azure portal and in the azure portal on the top left simply select create
a resource type in app service plan and you'll see it come up simply select it once it's there and that
will give you the option to create the service plan.
Go ahead and click Create and now we need to enter our details so first of all what's the name of our
app service plan.
I'm going to use SL dash app service plan as my example
select our subscription I'm going to use my pay as you go on and I'm going to create a new resource
group to put all of these objects sentence calls when SL dash app services
choose your operating system that your web apps that you're going to put on top are going to run on
so if you do in Dalton that apps for Windows you use Windows if you're doing some kind of Linux based
apps you would choose Linux as your operating system and then select your location.
So in my case I'm going to use central U.S. and then choose pricing tier.
Now this brings us up to a good point.
If we go over to our web browser and pull up apps service plans on the Microsoft site and if we scroll
down this we need to understand all the differences between the app service plans and you can see Linux
is called out specifically on the apps service Linux there as well.
So if we look at these we've got free shared basic standard premium and isolated as we mentioned in
the tutorial section.
So some of the key things we need to remember as we look through these.
So first of all they all limits on the number of apps you can deploy in free and shared.
So it's 10 for free.
Hundred for shared they are disk space limits as well.
So 1 gig for those shed tears then as we get up to basic it's 10 gig standard 50 gig tunes and 50 gig
and premium and then one terabyte and isolated and then we also have a max number of instances.
So you may get questions on this on the exam and you can see that on the basic we can go up to three
standard up to 10 premium jumps us to 20 and then isolate it is 100 to scroll further down you'll see
some other things like deployment slots are only available when you get up to the standard tier and
higher development tools.
Everything's pretty much there but things like cloning apps or reserve for premium and isolated as well
as some of the testing and production options those awful standard premium isolated and app service
for Linux as well.
Most of the diagnostics and monitoring tools were there throughout to some exceptions for service Linux
and then for networking you'll see there as well if one vignette integration we have to be at standard
premium or the dedicated isolated tier as well for programming languages if we drop down pretty much
good across the board there.
You'll see though the difference between what you can deploy on top of app service for Linux and the
generic Windows app services there as well.
So that's important to be aware of the one extra when you get there is Ruby on Linux which you can't
do on Windows systems.
And then as far as scale goes that's the other important thing you can see that auto scaling is only
supported on standard or higher as well as traffic managers only support on standard premium and isolated
as well.
So just be aware of this matrix you know I think I've covered the major ones you'll get asked on the
exam they're the big one that you'll see is probably around scaling and the sizes that you can scale
up and down you know there's a lot of questions on those.
So with that let's jump back to our portal and go in and select a tier so we'll scroll down and you
can see that that these represent the price of the underlying infrastructure.
So if I go and select a standard this is a two core three and a half gig of ram.
You I've got that 50 gig of storage.
I can scale up to 10 instances as you get a good summary then I get five deployment slots.
So if I select that one hit select and then go ahead and click Create that one that's spin up that UPS
service plan and should take probably a minute or two for that to be available so we'll fast forward
while that completes K and we can see in our notifications that deployment succeeded.
So we'll go ahead and select that resource that should take us directly to our APs service plan take
away these notifications and we can see an overview there we can see it's obviously not very much in
use right now CPM percentage is low but you got this kind of good monitoring overview of your amp service
plan right at the front of the main screen we can see that it's in central U.S. status is ready.
And on the right hand side we don't have any apps deployed you know live or into any deployment slots
at the moment.
So with that that concludes this demonstration and let's move on to the next module which we'll start
looking at deploying web apps themselves.