>> Hello. My name is Natasha.
I'm an engineer on Azure App Service.
Today, I'd like to show you App Service Migration Assistant.
So Azure App Service is
a fully managed platform that allows you to
deploy your code and run your application
at scale without having to worry about infrastructure problems.
There are a few ways you can migrate
your applications over to the platform.
One is if you already have your code ready,
you can use our CICD Pipeline to deploy your code.
You can also deploy your containers,
Linux or Windows over to the platform.
Finally, you can even use
our App Service Migration Assistant
to lift and shift your applications.
That's the one I'm going to be talking about today.
So the way to access
it, it's on https://appmigration.Microsoft.com.
I'm going to quickly take us over to that site.
When you come here, we have an assessment based on
this application where if you have an internet facing application,
you can quickly assess what technologies,
what frameworks is using and more importantly,
if this application can be lifted
and shifted on Azure App Services.
So let me enter our domain, target.com.
Within seconds, you will see us returning all the supported,
actually we detected all the domains
for this application and then we are
returning information about the framework
this application runs on,
the hosting platform,
the web server details and you can
have more details as well if you want to.
Super importantly, we have actually analyzed
this application against our top about 45,000
applications is our sample set to determine if
applications like this are already
hosted on App Services and if they run well.
So you notice here,
we have determined that
target.com can fully work on Azure App Services.
So now you can actually start
the migration process by clicking this button here.
You would install
that particular App Service Migration Assistant on your server.
This is your IIS server.
So the server where your application might be hosted on.
We do run it as administrator.
So for example, when you run this application,
you will see we are running as administrator and we are quickly
scanning your IIS server to
determine which sites might be running on your platform.
So look at the local host site.
I already have provisioned for this demo.
It is an ASP.net site that is working with SQL database.
So coming here, this is the site
that App Service Migration tool has figured
out exists on the platform on the local VM.
By default, we are collecting telemetry
from this tool but customers can
choose to skip it if they don't
want to send us the telemetry. Though, please don't.
If you do select a site,
we run an on-prem readiness check
on these sites content and configuration.
So these are a few rules that we
run against your local content and configuration
to make sure we have not found scenarios which will
prevent us from simply lifting and shifting this application.
So for example, if you're using
an HTTP protocol or you
are using any non ASP.net stacks because at this time,
ASP.net is the only framework we are supporting,
we would likely block your migration.
Because we want to make sure apps
that do pass the readiness checks,
we are able to migrate successfully.
At this point, since this works just fine,
if we had blocked the migration,
customers do have an option to save the report,
retry if there are
some fixes that they can
make to allow for the site to be migrated,
and be able to find a partner so
that these are the curated set
of App Service partners that can help
you positively refactor your application if it is not
something that can be lifted and
shifted or fixed for lift and shift easily.
So here, I'm going to go next.
This is the time where we're
asking you to authenticate yourself to arm.
So note that before then,
there was no authentication.
We were just running as a local administrator.
I'm authenticating myself here and
this tool has detected it. Wait for it.
It has detected that I have authenticated.
It's figured out all the subscriptions that are
running on my account and I am going
to create a new resource group and a new site.
We'll pick a region for you,
but the customers could choose to select
another region if they wanted to deploy their application.
So note that we detected there is
a database with your application content.
There are two options at this point.
We have learned more document link to explain.
One option is customers can
use the Azure Database Migrations Service.
So skip the database setup from us and instead,
bring their data separately using Azure DMS.
Or this is both customers can use
Azure App Service Hybrid Connection capability
to keep their data on-prem,
deploy their application content to App Services,
and have the application talk to
the local database using
Azure App Service Hybrid Connection feature.
So note that we have detected the host name,
the server name already,
and the boat for us to establish the hybrid connection with.
Now, we're actually setting up
the resources on Azure App Service end.
So first, we make sure
the information entered on the form before is valid.
So you have picked a resource group that's valid,
a plan that can actually support creation of more resources,
then we are creating the site resources.
Because we chose to set up a hybrid connection,
there are bunch of resources that we are
creating to set up hybrid connections successfully.
After that, we are going to serialize the content on
your machine for default website
and set up zip deploy for your content.
So Hybrid Connection Setup is
the longest step in this entire process.
But by longest, really it's still a few minutes.
Of course, the size of your site will
determine how long it'll take for us to serialize,
zip it and publish it.
But you can see all of this gets done super quickly.
So we do make sure that you
have Hybrid Connection Manager set up on your machine.
We have now added,
when the step is done,
a connection string on
your local Hybrid Connection Manager so it can
talk to the App Service we just created,
and voila, we are done.
So now, if you go to your website,
this is the part where
this application is hosted on Azure App Service.
It's an ASP.net so you're seeing a cold start.
It should be using
hybrid connection to dock to the database that we left behind.
Look at that. It works just fine.
Okay. So just to summarize,
what you saw showcase was
an App Service Migration Assistant
which helps you assess your application.
We have an online assessment tool
that helps you assess your Internet facing
applications to determine if they would be
good lift and shift candidates and will work on Azure App Service.
When you download our Migration Assistant,
we re-scan your application on
your local IIS server to make sure that it is a good lift and
shift candidate and it doesn't have configuration or
content that will prevent us from moving it to the Cloud as is.
Finally, when we have the application created,
you have the entire power of
all the past features available to you so you can manage
your application on the portal
and use more and more features of paths.
That's it for me. Thank you so much.
Thanks for watching and have a good Microsoft Build 2019.