Select our app again, run an assessment this time, and
you notice that there's no errors.
That's because I went back and fixed the binding and changed it
to 443. So it looks like the only warning we have now is to make
sure that our certificate is valid,
which, of course, we would do anyway. Fortunately,
because it's such a tiny application, it doesn't take long.
Okay. Because we didn't see a blocker this time,
it's asking us for specifics on how we want to set up our
app service. That's what it's doing here.
So I'm going to choose my az801‑rg resource group,
the destination site,
I'll call twaz81webapp1. App service plan again is the
underlying compute. I'm actually in East US. Now,
it says here a single premium instance,
that's pretty expensive. I don't actually want to keep that. I'm
going to want to downgrade that to standard as soon as this
finishes deploying, so I'll definitely want to do that. Now
notice that we can skip database,
which is what I'm doing because I would handle the
SQL Server migration separately.
But you can actually do a hybrid scenario where you migrate the IIS
app to Azure App Service and you continue to use your on‑premises SQL
Server or SQL Server cluster. This is called a hybrid connection and
what this allows you to do,
it involves installing a small service in your local environment to act as a
proxy. It enables just a single port connection. In this case, if it were SQL
Server, you would have the on‑premises database server name here, and then you
would do TCP for 1433, and that would allow your app service to poke through
your firewall and come in on that hybrid connection to continue communicating
with your on‑premises database.
So that helps customers when they're doing a more of a phased migration.
I'm going to do a skip on this one. And then notice that we can export
the ARM template if we're going to handle the deployment separately. I'm
going to put that on my desktop.
Nice convenience.
So we could use PowerShell, or the Azure CLI, or whatever, to do
that deployment ourselves, or we can click Migrate. And this
looks like we're ready to go here.
So once we've done our handshake into the Azure Migrate project,
as long as you don't have a blocking error,
you can proceed. I've taken a snapshot copy of the underlying ARM
template, and at this point it's not only sending all of the
discovery and assessment data to Azure Migrate,
but it's actually building out the resources and pushing
the code into the App Service as well.
That's pretty sweet, seems to me. Pretty sweet indeed.
Nice.
So while we're waiting for that,
let me come back to Azure Migrate and do a hard refresh in the portal.
It hasn't updated yet.
So let's come back to the app.
Okay, Congratulations, your site's been successfully migrated! Cool.
So as you can see, we can migrate another site,
we can jump into the Azure portal, or we can browse to the site
directly. And here we can see https, the name of my
webapp.azurewebsites.net. And here it is,
it's running just fine.
So if we go to the Azure App Services blade here in the portal,
we should find there is our running web app and there's the
underlying App Service plan right here.
And like I said, I want to save some money here,
so I'm going to go down to Scale up, and I want to resize this
because the premium's too expensive for just this little
environment here, So I'm going to downgrade to S1 and click Apply
to put that change into effect.
Great! So now that that's finished, it looks like we're ready to continue on our merry way.