[MUSIC].
>> Hello, everyone, and welcome.
My name is Vineet Vikram
and I'm a Program Manager with the Azure Migrating.
Today, I'm here to talk about the next set of innovations
we're driving in Azure Migrate,
to help you discover and assess
web apps for migration to Azure App Service.
Azure App Service is a flexible and
fully managed service for building,
deploying, and scaling
your web apps seamlessly in Azure.
Before we see this new feature in action,
let's learn about Azure Migrate and its features first.
Azure Migrate is a one central place in Azure portal
that provides a unified experience to discover,
assess, and migrate your servers,
databases, and apps to Azure.
We also have coverage for scenarios
such as ISP integrations, containers, and VDIs.
You start off by discovering
your large-scale data center.
These could be VMware, Hyper-V, bare-metal, AWS, GCP,
or any other Cloud Service provider.
You could also inventory installed software,
perform application dependency analysis,
and discover SQL instances and
databases without installing any agents.
Azure Migrate Assessment provides you
rightsizing and Azure readiness recommendations.
Once you have discovered your entire estate,
you could create assessments for migrating to Azure IS.
ADS, and Azure SQL.
Once you are ready to migrate,
Azure migrate provides additional migration capabilities
for migration of your servers,
databases, and apps to Azure App Service.
Until now, you could do agentless discovery
and assessment of your virtual machines
and bare metal server with Azure Migrate.
But you would use integrations with tools like
App Service Migration Assistant
for assessing your web apps individually.
With that newest edition to Azure Migrate,
you can discover .NET web apps running
in your VMware environment
and create assessment or migration recommendations
at scale for migration to Azure App Service.
With that, let's jump right into the demo
and let me show you this new feature in action.
Here I am on the Azure Portal
and I'll browse to Azure Migrate overview page.
You can see that Azure Migrate
supports various migration and assessment scenarios.
Since we will be focusing on at scale discovery
and assessment of web apps today,
I'll just select servers, databases,
and web apps under migration goals,
and create a project.
I specify the desired subscription,
resource group, project name,
and the desired region to create my project.
Once the project is created,
you can see that Azure Migrate discovery and
assessment tool has already been added to my project.
To begin discovering my on-premises
IT environment in a unified manner,
I click on "Discover".
I will continue with the default option
to discover using an appliance.
I will indicate whether the source IT estate
is virtualized or not.
In this case, I'm selecting the option, yes,
with VMware vSphere Hypervisor,
as I'm going to discover a VMware-based environment.
Next, I will provide
a name for my Azure Migrate appliance.
Let's go with appliance01,
and click on "Generate Key" to create a key
to register my Azure Migrate appliance on my project.
Now there are two ways in which I can
deploy my Azure Migrate appliance.
One, by downloading
a virtual machine image in my VMware environment.
Two, by choosing to download an installer and
converting one of my servers into an appliance.
For this demo, I have already gone ahead
and deployed my appliance.
Once I've registered my appliance to
the project that I had created earlier,
I will enter the credentials of the vCenter Server,
which manages this server that I want to discover.
To identify the installed applications on my servers,
including IIS installations,
I'll provide credentials to
the individual servers running in my VMware environment.
I can add both domain and non-domain credentials.
In this case, I will add non-domain credentials.
Please make sure that the account used
has local admin privileges on the source server.
Azure Migrate automatically maps
credentials to the respective servers,
so one doesn't have to map them manually.
Most importantly, these credentials
are never sent to Microsoft
and remain on the appliance running in your data center.
Once I've configured my Azure Migrate appliance,
I'll initiate discovery and let it run.
Note that based on the size of the target environment,
it can take up to a few hours to
discover servers and web apps running on them.
I'm now going to go back to
the Azure Migrate Project in the Azure portal.
I can see that 441 servers have been discovered
and 61 servers out of these are found to be running IIS.
I can now start investigating deeper into
these IIS web servers to understand
what type of .NET web apps,
and what attributes about
those web apps have been discovered.
I click on these servers running IIS.
It takes me to the discovered servers page
where I can see details of the IIS web servers.
Under the web app columns,
I can see the number of web apps
hosted on each IIS server.
I click on it to view the list of apps
along with attributes like the web server type,
version, URLs, binding ports, and application pools.
Now that we have seen all the discovery information,
I just want to pause and learn
that we were able to do this
without placing any agent on any of the servers
and we were able to do it for the entire estate,
discovered using Azure Migrate in a matter of minutes.
Now I'm ready to start creating an assessment.
Creating an assessment is straightforward.
I go and click "Create Assessment",
I pick "Azure App Service" as the target.
Once I've specified that in the next step,
I can then specify attributes of
the assessment that I deeply care about.
For example, do I want to run my apps in
an isolated environment or not in App Service plan?
In this case, I will go with the default options
and click "Next".
I will provide a name for my assessment and group.
I can choose to assess
a few web servers or my entire estate.
Let's go ahead
and assess every web server that is discovered.
Review the assessment properties,
and click on "Create Assessment".
It only takes a couple of minutes
for the assessment to get computed.
When I go back to the Azure Migrate portal,
I click on "Refresh",
and there you have it.
You see one assessment
has been created for App Service.
Let's click on that.
The list of assessment shows up,
and here's the assessment that I just created,
web app assessment.
Let's go deeper into the assessment
and see what Azure Migrate is telling me about my estate
and its readiness for Azure.
I can see the readiness status of the assess web app,
it's also telling me
that I'll need a composite of 67 plan,
and it's going to cost me around $9,400
to host these web apps in Azure App Service.
I click through and I can see the recommendations.
Let's look at this specific one
why is it not ready to migrate to Azure.
I'm very curious to know about that.
I click on it and there you go.
It tells me that Azure App Service
only supports port 80 and 443
and this one was using port 85.
Our discovery was so detailed
that it was able to understand
what was really happening with the web app,
and it's configuration on prem,
and what may not ideally work for App Service
and it gives us recommendation and remediation guidance.
The assessment also provides a recommended SKU,
recommended target deployment type,
and has allocated my web app to an App Service plan.
An App Service plan defines a set of compute resources
for a web app to run.
Let me select this plan and to view the details,
I can see the core, RAM, memory, etc.
that this plan provides.
I can also see other web apps that are part of this plan.
Only those apps whose readiness status is ready
or ready with conditions gets allocated to a plan.
Please note that in-app service,
run this task for the number of plans running in
App Service and not the number of web apps.
There, the assessment is helping you understand readiness,
suitability, the right plan, and what it will cost
to host your web apps in App Service.
I just showed you very quickly at scale discovery
and assessment for web apps that
need to migrate to App Service.
Again, App Service is a great target
for your .NET and other web apps.
To learn more and start using these new capabilities,
check out these links
and have a great migration experience.
Thanks for watching.
[MUSIC]