Skip to content

Latest commit

 

History

History
121 lines (72 loc) · 4.52 KB

README.md

File metadata and controls

121 lines (72 loc) · 4.52 KB
Raw

Going Live

Overview

In this lab you will learn how to transition a source environment to Azure.

Prerequisites

Ensure you have completed the previous labs where the following is already configured:

  1. Create a new azure internal DNS server which will host the DNS records and also do recursion to the on prem version ( this will be DNS server which you already have up and running)

  2. Setup the monitoring solution for Azure DNS as well

Exercises

Exercise 1: DNS

Monitor Azure DNS https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-dns

  1. Resolve names from the container to check that it's working

  2. Now that we have an application up and running in a container on our Container host, the last step is you to finalize the migration. We will do that by simply cutting over the routing and DNS information

  3. Update the DNS records by RDPing into the DNS/AD Server, in this case the server is 'dc1.contoso.com' and open DNS. Here we can see that the ibusyspy dns record is a cname pointing to 'aw-webapp.contoso.com'

    image

  4. Update the record to point to the Windows Container host, in this case 'host1.contoso.com'

    image

  5. Open a browser to verify that you can indeed get to the site.

    image

Exercise 2: Containers

Assumptions

  1. internal DNS server configuration of the containers will be targetting the on prem DNS server

  2. setup configuration to hit the azure dns server

Azure DNS delegation https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns

Exercise 3: Application Gateway

Assumptions

  1. Deploy a new application gateway

  2. Setup WAF and deploy a new self signed certificate to have SSL termination and enable OWASP

  3. Enable monitoring for the application gateway

Exercise 4: Traffic manager

Assumptions

External endpoints are used for services hosted outside Azure, either on-premises or with a different hosting provider.

  1. Setup a new traffic manager and target the WAF you've just created

  2. The balancing method whilst everything is not configured will be having one of the endpoints disabled

  3. Enable monitoring for traffic manager as well

  4. Open the browser and validate that which you're reaching the new server

Exercise 5: Verify the whole setup

Let's verify the changes

Assumptions

  1. Setup NSG which will block all traffic: DC/DNS, Web server, IaaS SQL server
  2. Test the website
  3. Monitor the new resources through the dashboard

Exercise 6: Deploy a reference architecture

During these labs, you've explored deploying Windows Containers onto three services: Virtual Machines, App Service and AKS. You can also deploy to Azure Container Apps, but we did not cover that in these labs. Each of these platforms has a production ready reference implementation that includes a suggested infrastructure setup and guidance for configuring your application. Try deploying one of the reference architectures below with your legacy application.

AKS Windows Baseline Azure App Service Landing Zone Accelerator Azure Container Apps Landing Zone Accelerator

Summary

In this hands-on lab, you learned how to:

  • Configure internal DNS
  • Configure Azure DNS
  • Cut over live traffic using Azure services

Copyright 2023 Microsoft Corporation. All rights reserved. Except where otherwise noted, these materials are licensed under the terms of the MIT License. You may use them according to the license as is most appropriate for your project. The terms of this license can be found at https://opensource.org/licenses/MIT.