In this demonstration, we'll learn to use the App Service Migration Assistant.
Let's see, what are we looking at?
We're looking at the desktop of a Windows Server 2022
member server, it's a web server.
If I bring up the IIS Manager,
I just have used the default website here in the manager,
and I've already got the site loaded up.
It's just, you know, a relatively simple Blazor Pages app here.
I've customized it a little bit, as you can see.
It's got a couple of pages in it, you know,
it's just something to give us something to work with in terms of
proof of concept given the scope of what we're doing.
Now, you can download the App Service Migration Assistant.
Just do a Google search for it,
and you can find it at the Microsoft Download Center.
It's a free download, it installs in just a minute,
it's a desktop app, and here it is.
I apologize that the text is kind of small.
I record at 1020 and depending upon what your form factor is,
this is all the more reason frankly for you to install
it in your own test environment.
So, as you can see on the left here, we first choose a site.
These are sites that are detected on the local computer.
We'll then do an assessment, login to Azure,
tie into Azure Migrate, and go on from there.
So let's just select the Default Web Site and click Next to continue.
All right,
it says here that there's errors that block automatic migration using this tool,
however you may continue and send the results to an Azure Migrate Project.
So we'll want to look at the successes, one warning that we are using HTTP,
but it's a bogus certificate.
It looks like the error is TCP port bindings are not supported.
Ah, that's my problem.
Yeah, I'm using 7070, I forgot to update the port binding to 443,
and that's not allowed in App Service,
so that's a good example anyway of a real‑world situation.
Now notice you can save this resulting report and
load it back into the interface, and so on,
and so forth.
Let's go next,
and here we have a browser code flow to sign into our Azure subscription.
So I'm going to copy the code, open a browser,
paste the code in here, sign in with an administrative account, yes,
I'm trying to sign in to Azure App Service Migration Assistant.
We can close the window and come back to the tool.
Now what's cool about this is that you can see any
previously created Azure Migrate Projects.
We also can create a new one right on the fly.
I like that a whole lot.
I'm going to see if I can shoehorn this into my ps‑migrate project
that I've created and used elsewhere in this course.
And it's really as simple as sending the assessment data into the project,
that Azure Migrate is such a wonderful one‑stop shop.
While that data's being transferred,
with no need for site‑to‑site VPN or anything like that,
we can go right over the internet.
Let's go to Azure Migrate, and if we look at our Web apps component here,
I've already got the ps‑migrate project in here.
And I just realized that we're going to,
I'm sure,
see an error back in the application because I forgot to
add assessment and migration tools.
That's totally okay here,
and it's all part of our learning. Something that you've seen elsewhere in this
course when we looked at using Azure Migrate, we used it specifically in the
module on server migration is that it's a two phase,
well, three‑phase operation.
You have your project at the top level,
then within that project you have your assessment phase,
and then your migration phase, so let's add in an assessment tool.
This is just the built in, first‑party Azure Migrate Assessment,
supports .NET, Java, and PHP,
so it looks like this ecosystem has changed a little bit
even since the last time I was in here.
It's amazing how fast the Microsoft team works with that.
So here we can see at this time,
no web servers or websites or anything ready for migration yet.
We come back,
we can push those changes from the Azure App Service
Migration Assistant in a moment.
As far as the migration tool, again,
the only option at this point is Microsoft's own,
so we've got support for .NET, Java, and PHP, like I said before.
I think the reason for the Java,
it just occurred to me, is that this is involving the
containerization and the App Service stuff,
so I guess what I said earlier is still valid that the three stacks are .NET,
ASP.NET, and Java.
It says it right up here, containerize your .NET in Java to AKS,
discover and assess ASP.NET, and go to Azure App Service.
There you go.
So let's come back to the tool, and let's send in our assessment data.
Let's give that another try, didn't like that.
Well, let's see if I can quickly start over. Let's come back.