Your challenge is to begin the initial planning for the migration of Contoso Mortgage's application to Azure. Remember that while your initial focus is on a subset of servers and applications within the current datacenter, you are tasked with validating that the process you use throughout this journey can be used for future migrations. Do not forget to review and adapt your plan as you encounter new aspects and considerations with each subsequent challenge.
During the first minutes, you will discuss with your team the distribution of workloads, determine the process, tools, and technologies you will use to execute your migration to Azure. Based on your knowledge of the current infrastructure and the target platform, your team must work through the customer requirements to choose how you will migrate your applications, how you will determine the cost of the new environment, and how you will minimize downtime for the users of the applications as migrations occur.

Once that is ready lets begin with the hacking. 

Section 1 – Application server migration

In this challenge we will be downloading the Migration Assistant and start your .NET and PHP app migration to Azure App Service. This local agent will perform a detailed assessment and then walks you through the migration process. The tool performs readiness checks as well as a general assessment of the web app’s configuration settings.

Once the application has received a successful assessment, the tool will walk you through the process of authenticating with your Azure subscription and then prompt you to provide details on the target account and App Service plan along with other configuration details for the newly migrated site.

The Migration Assistant tool will then move your site to the target App Service plan while also configuring Hybrid Connections, should that option be selected.

Download and Install the Azure Migration Assistance Tool

    1. In the Azure Virtual Machine where you have the applications go to the Azure Application Service migration website

    2. Go to the Azure Migrate overview page  https://appmigration.microsoft.com/, click on the Assess and migrate web apps button. This takes you to the Migrate to Azure App Service page

Note: On this page, you can choose to assess and migrate your web app by entering a public URL to the app, or by downloading and installing the Migration Assistant tool on your computer.

    3. Click Download to download the Migration Assistant tool

    4. Once the download is complete, install and run the tool

    5. Open the Migration Assistant application

    6. The tool will show you the websites that are running in iiS. Select the “Default Web Site”  website and click Next.

1. 1. The tool will initiate the assessment of the application to see if it can run in Azure and if anything needs to be changed. This will result in an Assessment Report in which you may encounter some errors:
   2. Common errors are related to the version of HTML and the web.config file
      
      1. Two well-known common errors related with the web.config files are:

File 1: c:\inetpub\wwwroot\web.config

Lines to delete:

    <compilers>

      <compiler language=”c#;cs;csharp” extension=”.cs” type=”Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ warningLevel=”4″ compilerOptions=”/langversion:default /nowarn:1659;1699;1701″ />

      <compiler language=”vb;vbs;visualbasic;vbscript” extension=”.vb” type=”Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ warningLevel=”4″ compilerOptions=”/langversion:default /nowarn:41008 /define:_MYTYPE=\&quot;Web\&quot; /optionInfer+” />

    </compilers>

File 2: C:\inetpub\wwwroot\Views

Lines to delete:

  <appSettings>

    <add key=”webpages:Enabled”
value=”false” />

  </appSettings>

    7. Once the Assessment Report shows no errors that prevent the application from being migrated to Azure, click on Next.

    8. Complete the steps to login into Azure in the following login page and enter the code that is shown in the Migration Assistant.

    9. Once logged in, enter the details of the App Service that we are migrating the application to

1. 1. Select a Resource Group associated to your user (Ex. estudiante5minihackcloudrg)
   2. Fill in a Name for the App Service (Ex. cmweb1)
   3. Pick a Region (East US)
   4. Leave the Database option to “Set up hybrid connection to enable database connection”
   5. Click Migrate

    10. The migration will start. Once it is done, you'll see the Migration Results.

Note: On the step to “Setup Hybrid Connection Manager” we are going to select the option to Skip this step and install HCM setup on this server”.

Note: You will need to execute this steps on the frontdoor (cmweb1) and the backend(cmapp1).

Section 2 – Database Migration

Create a project and add a tool

Set up a new Azure Migrate project in an Azure subscription, and add a tool.

• An Azure Migrate project is used to store discovery, assessment, and migration metadata collected from the environment you're assessing or migrating.
• In a project you can track discovered assets, and orchestrate assessment and migration.

1. In the Azure portal > All services, search for Azure Migrate.

2. Under Services, select Azure Migrate.

3. In Overview, click Assess and migrate databases.

4. In Discover, assess and migrate servers, click Add tools.

5. In Migrate project, select your Azure subscription, and select the resource group estudiante#minihackcloudrg.

6. In Project Details, specify the project name, and geography in which you want to create the project (United States).

7. Click Next, and add an assessment or migration tool.

8.  Note

   When you create a project you need to add at least one assessment or migration tool.

9. In Select assessment tool, add an assessment tool. If you don't need an assessment tool, select Skip adding an assessment tool for now > Next.

10. In Select migration tool, add a migration tool as required. If you don't need a migration tool right now, select Skip adding a migration tool for now > Next.

11. In Review + add tools, review the settings and click Add tools.

After creating the project you can select additional tools for assessment and migration of servers and workloads, databases, and web apps.

Create a single database

Create single database using the Azure portal.

1. Select Azure SQL in the left-hand menu of the Azure portal. If Azure SQL is not in the list, select All services, then type Azure SQL in the search box. (Optional) Select the star next to Azure SQL to favorite it and add it as an item in the left-hand navigation.

2. Select + Add to open the Select SQL deployment option page. You can view additional information about the different databases by selecting Show details on the Databases tile.

3. Select Create:

4. On the Basics tab, in the Project Details section, type or select the following values:

   • Subscription: Drop down and select the correct subscription, if it doesn't appear.

   • Resource group: Select estudiante#minihackcloudrg.

5. In the Database Details section, type or select the following values:

   • Database name: Enter contosomortgagedb.

   • Server: Select Create new, enter the following values and then select Select.

     • Server name: Type cmdb1; along with some numbers for uniqueness.

     • Server admin login: Type demouser.

     • Password: demo!pass123.

     • Location: East US.

      

   • Want to use SQL elastic pool: Select the No option.

   • Compute + storage: Keep the default settings.

6. Select the Networking tab.

   1. Select the Private endpoint 
   2. Click + Add Private endpoint
      1. Type the Name: azuresqlvnetcon
      2. Select the virtual network named: Azurevnet
      3. Select the subnet: Azure
      4. Click on OK

7. Select the Additional settings tab.

8. In the Data source section, under Use existing data, select None.

9. Under Enable advanced data security, select Not now.

    

10. Leave the rest of the values as default and select Review + Create at the bottom of the form.

11. Review the final settings and select Create.

12. On the SQL Database form, select Create to deploy and provision the resource group, server, and database.

Note: Repeat the process to create a second database named contosomortgageidentity on the same Azure SQL server .

Section 3 – Update the connections to the database and web apps

Note: You may need to go to your Azure SQL Database and get a copy of the connection string. When updating the connection string make sure that you add the database password.

Create a Front Door for your application

1. Add a frontend host for Front Door

Create a Front Door configuration that directs user traffic based on lowest latency between the two backends.

1. On the top left-hand side of the screen, select Create a resource > Networking > Front Door > Create.
2. In the Create a Front Door, you start with adding the basic info and provide a subscription where you want the Front Door to be configured. Similarly, like any other Azure resource you also need to provide a ResourceGroup (estudiante#minihackcloudrg). conto
3. Once the basic info is filled in, the first step you need to define is the frontend host for the configuration. The result should be a valid domain name like myappfrontend.azurefd.net. This hostname needs to be globally unique but Front Door will take care of that validation.

Next, you need to configure your application backend(s) in a backend pool for Front Door to know where your application resides.

1. Click the '+' icon to add a backend pool and then specify a name for your backend pool, say myBackendPool.
2. Next, click on Add Backends to add your websites created earlier.
3. Select Target host type as 'App Service', select the subscription in which you created the web site and then choose the first web site from the Target host name, that is, myAppServicePlanEastUS.azurewebsites.net.
4. Leave the remaining fields as is for now and click Add'.
5. Repeat steps 2 to 4 to add the other website, that is, myAppServicePlanWestEurope.azurewebsites.net
6. You can optionally choose to update the Health Probes and Load Balancing settings for the backend pool, but the default values should also work. Click Add.
7. Add a routing rule

Lastly, click the '+' icon on Routing rules to configure a routing rule. This is needed to map your frontend host to the backend pool, which basically is configuring that if a request comes to myappfrontend.azurefd.net, then forward it to the backend pool myBackendPool. Click Add to add the routing rule for your Front Door. You should now be good to creating the Front Door and so click on Review and Create.

 Warning: You must ensure that each of the frontend hosts in your Front Door has a routing rule with a default path ('/*') associated with it. That is, across all of your routing rules there must be at least one routing rule for each of your frontend hosts defined at the default path ('/*'). Failing to do so, may result in your end-user traffic not getting routed correctly.

View Front Door in action

Go to your Azure Front Door frontend host address and test the functionality.

Create a WAF policy (optional)

First, create a basic WAF policy with managed Default Rule Set (DRS) by using the portal.

1. On the top left-hand side of the screen, select Create a resource>search for WAF>select Web application firewall (Preview) > select Create.
2. In the Basics tab of the Create a WAF policy page, enter or select the following information, accept the defaults for the remaining settings, and then select Review + create:

1. In the Association tab of the Create a WAF policy page, select Add frontend host, enter the following settings, and then select Add:

 Note

If the frontend host is associated to a WAF policy, it is shown as grayed out. You must first remove the frontend host from the associated policy, and then re-associate the frontend host to a new WAF policy.

1. Select Review + create, then select Create.
2. Configure WAF rules (optional)

Change mode

When you create a WAF policy, by the default WAF policy is in Detection mode. In Detection mode, WAF does not block any requests, instead, requests matching the WAF rules are logged at WAF logs. To see WAF in action, you can change the mode settings from Detection to Prevention. In Prevention mode, requests that match rules that are defined in Default Rule Set (DRS) are blocked and logged at WAF logs.

Default Rule Set (DRS)

Azure-managed Default Rule Set is enabled by default. To disable an individual rule within a rule group, expand the rules within that rule group, select the check box in front of the rule number, and select Disable on the tab above. To change actions types for individual rules within the rule set, select the check box in front of the rule number, and then select the Change action tab above

Associate a WAF Policy (optional)

Create a Front Door configuration that directs user traffic based on lowest latency between the two backends.

1. On the top left-hand side of the screen, select Create a resource > Networking > Front Door > select you FrontDoor > click on Web Appliction firewall > select the Frontend
2. Click on Add policy
3. From the Policy dropdown select your policy and click on Add
4. Click on save.