Leon Welicki: Hello there and thank you very much for joining
us today in this new Azure Portal How To video.
Today, we learn about the new and improved experience for
creating App Services, and for that we have Byron Tardif,
who’s going to show us all about it. So, thank you very much
for joining us, Byron.
Byron Tardif: Thanks for having me, Leon. Hello, everybody.
And today, we’re going to talk about App Service and the
new full screen create experience. You guys must already be
familiar, this is the new Azure landing page. And you can see
we have App Service right here on top. If you click in, you
can see all of your App Service apps that you have created,
and you can create a new one either clicking here on add or
going to the global create. And here, you’ll also find Web
Apps immediately. And this is where we dive into the new
experience.
There’s a couple of things that are common across all of the
resources that are adopting this view. One of them is the
first selection that you’re going to have is the subscription
and the resource group. The way that I usually explain the
resource group is like a virtual folder where you put all of
your resources inside and then you can use that to share
access to somebody else. For example, if I wanted to give
Leon access to my new web app that I wanted to create, I
would do it at the resource group level.
So, let’s call this Live Demo.
And now, we’re jumping into the specifics of the web app
that I am creating. I’m going to give it a name.
This is going to validate that this is unique. And then these
were some of the changes that we did to create to start to
come in. First of all, you’re going to be able to choose
whether you want to push your own code or you want to
push a Docker container. A lot of people don’t know that
App Service supports both modes. And for this demo, let’s
just say that I’m going to do code. And then this is another
change that we made, where you’re going to make an upfront
select of what runtime stack you’re going to use. So, what’s
your favorite runtime stack, Leon?
Leon: I would use .Net Core, for example.
Byron: Awesome. So, you can see that we have .NET Core
2.2 And at that point, we see that we supported both on
Linux and Windows. But in this case, we recommend Windows
for this particular selection. If you wanted to run something
on Wubi for one of your weekend projects for example, you
would see that we supported on Linux. And for example, if
you wanted to go with THP 7.2, you see that we supported
both on Windows and Linux. And in this case, we usually
recommend running it on Linux.
For this demo, let’s just go with .NET.
And then the next thing is the location drop down. So,
this is where you choose where your app is going to live.
And one of the cool things that I want to show here is
that we actually have now presence in Africa. App Service
is a Ring 1 Service, so whenever a data center is open to
the public, App Service has to be there. And this is the newest,
latest region that is now available.
Then just for the sake of this demo, I’m going to switch over
and run it on Linux and I’m going to show you something
else that’s new here. For Linux instances, we didn’t use to
have a free offer. And now, we have a perpetual free offer
if you’re running web apps on Linux. The way this works is
you’re going to be hosted on a shared env. There’s limits
on the amount of memory that you can consume, the
amount of bandwidth and the amount of CPU. But it’s a
perfect environment for you to do like your testing out the
waters, figuring out how this works, how is Linux different
than Windows for hosting apps, all of that stuff. So, I’m
going to go ahead and select my free instance. And I’m going
to jump over to the next tab. This is where we have
integration with Application Insights. It’s not available for
all stacks but for the ones that are available, here’s where
you would configure it. Then we go into tags. This is a global
Azure feature. I’ve seen people use it to tag their resources
with, for example, a cost center. Because these tags get
populated all the way down to your bill. So if you want to
know what project is costing you what money, this is a good
way to do it.
And finally, we jump over to review and create, where
you’re going to get a summary of what are the resources
that are going to be created? In this case, you can see
there’s details for the app and the App Service plan. And
here’s also where we take a second to do the validation.
So, this is where we make sure that whatever input you
provided is going to complete with a successful creation
of your app. If I click create here, that’s basically what’s
happening now. The app’s going to deploy and 30 seconds
from now, I’m going to have a web app running in the cloud
and ready to scale.
Leon: That’s really cool. And these patterns that you show
us is very similar. In fact, it’s not very similar. It’s the same
that we use in many other places, right?
Byron: Exactly. So if we jump over here where that create
is happening, you’ll see that for App Service resources, we
have web apps. We have App Service plans. They look exactly
the same. If I switch over to App Service environment, they
look exactly the same. And even for things that are not
App Service specific, you can create a VM, SQL database,
Azure storage—they’re all using this same pattern that
your team is providing.
Leon: So, basically, the idea is that customers can learn on
a small set of partners and then apply them across the board,
so it makes it easier to accomplish these tasks.
Byron: Yeah. And it makes a lot of sense because if I know
how to create a web app, now I know how to create any
other resource.
Leon: That’s great. So, thank you very much, Byron. And
thanks, every one of you for watching. Please try this and
leave us a comment. Let us know what you think. Leave us
a comment on the video. Follow us on Twitter. And look forward
to seeing you in the next video. Thank you very much.
Byron: Thank you, guys.