1
00:00:01,040 --> 00:00:04,740
Migrate IIS Web Apps to Azure App Service.

2
00:00:04,740 --> 00:00:08,040
Now I'm presuming that you know what an IIS web app is and that

3
00:00:08,040 --> 00:00:13,060
you're familiar working with IIS on Windows Server. You may not be

4
00:00:13,060 --> 00:00:15,040
as familiar with Azure App Service.

5
00:00:15,040 --> 00:00:15,830
What is it?

6
00:00:15,830 --> 00:00:16,370
Well,

7
00:00:16,370 --> 00:00:20,900
it's a Platform as a Service, or PaaS, product in which a lot of

8
00:00:20,900 --> 00:00:23,220
the underlying compute is abstracted away.

9
00:00:23,220 --> 00:00:26,610
Think of what you've got going on on‑premises. You have

10
00:00:26,610 --> 00:00:30,690
one or more IIS web server machines, physical or virtual,

11
00:00:30,690 --> 00:00:35,400
it doesn't matter, probably behind a load balancer or using the network load

12
00:00:35,400 --> 00:00:39,570
balancing service that's built into Windows Server, probably have a SQL Server

13
00:00:39,570 --> 00:00:44,410
back end, and now you're tasked with rehosting those workloads up into Azure,

14
00:00:44,410 --> 00:00:48,370
and maybe you don't have a site‑to‑site virtual private network or an

15
00:00:48,370 --> 00:00:50,340
ExpressRoute link. What can you do?

16
00:00:50,340 --> 00:00:52,420
Well, the App Service is fantastic.

17
00:00:52,420 --> 00:00:55,490
It's a hosted web application, API application

18
00:00:55,490 --> 00:00:58,260
platform, and it's got a lot going for it.

19
00:00:58,260 --> 00:00:59,340
The agility,

20
00:00:59,340 --> 00:01:02,830
the ability to auto scale with no load balancer is

21
00:01:02,830 --> 00:01:05,350
a great benefit of App Service.

22
00:01:05,350 --> 00:01:10,460
It eases your administration, and the idea, the business idea for Microsoft, is

23
00:01:10,460 --> 00:01:15,460
that App Service allows your developers to focus more on the application and

24
00:01:15,460 --> 00:01:21,230
serving your customers as opposed to worrying about all of the optimizations

25
00:01:21,230 --> 00:01:23,840
and stuff that you need to do on‑premises.

26
00:01:23,840 --> 00:01:27,740
Now there's a place at the table for your infrastructure engineers. The

27
00:01:27,740 --> 00:01:32,750
App Service plan is the underlying compute. And in stark contrast to

28
00:01:32,750 --> 00:01:36,880
when you're running your IIS on a Windows Server VM in Azure, when you

29
00:01:36,880 --> 00:01:39,540
have full control of the entire VM,

30
00:01:39,540 --> 00:01:43,450
the App Service plan is a much more abstracted Platform as a Service

31
00:01:43,450 --> 00:01:46,200
offering where you have some degree of control,

32
00:01:46,200 --> 00:01:46,900
for example,

33
00:01:46,900 --> 00:01:51,560
you can resize to provide more or less relative compute, and

34
00:01:51,560 --> 00:01:54,840
you can do those autoscaling rules and so on,

35
00:01:54,840 --> 00:01:57,010
but you're not going to have full stack access.

36
00:01:57,010 --> 00:02:00,040
That's one of the tradeoffs that we always have when we're thinking

37
00:02:00,040 --> 00:02:03,020
between Infrastructure as a Service on one hand,

38
00:02:03,020 --> 00:02:05,640
Platform as a Service on the other.

39
00:02:05,640 --> 00:02:05,920
Now,

40
00:02:05,920 --> 00:02:09,450
it's beyond our scope for this training because Microsoft puts all of

41
00:02:09,450 --> 00:02:13,810
the Azure data products in entirely different certifications. I would

42
00:02:13,810 --> 00:02:19,320
encourage you to look at the DP exams and also the Azure Architect

43
00:02:19,320 --> 00:02:23,320
AZ‑300 series exams. But I want you to know that Azure Migrate has a

44
00:02:23,320 --> 00:02:25,340
database migration path.

45
00:02:25,340 --> 00:02:26,290
So in summary,

46
00:02:26,290 --> 00:02:29,750
in this course, we're concerned only with taking the IIS web

47
00:02:29,750 --> 00:02:34,580
application, and then we would separately use Azure Migrate tools

48
00:02:34,580 --> 00:02:38,700
to assess and migrate the databases into a Platform as a Service

49
00:02:38,700 --> 00:02:40,210
orientation. For example,

50
00:02:40,210 --> 00:02:49,000
like in this diagram, running your Azure SQL databases under an Azure SQL database virtual server in Azure.