Merge pull request #312570 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-04 06:00 UTC

Author: learn-build-service-prod[bot]

articles/dns/tutorial-alias-pip.md

@@ -5,7 +5,7 @@ services: dns
 author: asudbring
 ms.service: azure-dns
 ms.topic: tutorial
-ms.date: 11/30/2023
+ms.date: 03/03/2026
 ms.author: allensu
 ms.custom: template-tutorial #Required; leave this attribute/value as-is.
 #Customer intent: As an experienced network administrator, I want to configure Azure an DNS alias record to refer to an Azure public IP address.
@@ -76,11 +76,11 @@ Create a virtual network and a subnet to place your web server in.
 
 ## Create a web server virtual machine
 
-Create a Windows Server virtual machine and then install IIS web server on it.
+Create a Linux virtual machine and install NGINX web server on it.
 
 ### Create the virtual machine
 
-Create a Windows Server 2019 virtual machine.
+Create an Ubuntu virtual machine.
 
 1. In the Azure portal, enter *virtual machine* in the search box at the top of the portal, and then select **Virtual machines** from the search results.
 1. In **Virtual machines**, select **+ Create** and then select **Azure virtual machine**.
@@ -92,16 +92,17 @@ Create a Windows Server 2019 virtual machine.
     | Subscription   | Select your Azure subscription. |
     | Resource Group    | Select **PIPResourceGroup**. |
     | **Instance details**  |     |
-    | Virtual machine name   | Enter **Web-01**. |
+    | Virtual machine name   | Enter **web-01**. |
     | Region    | Select **(US) East US**. |
     | Availability options   | Select **No infrastructure redundancy required**. |
     | Security type  | Select **Standard**. |
-    | Image   | Select **Windows Server 2019 Datacenter - Gen2**. |
+    | Image   | Select **Ubuntu Server 24.04 LTS - x64 Gen2**. |
     | Size    | Select your VM size. |
     | **Administrator account** |            |
+    | Authentication type | Select **SSH public key**. |
     | Username | Enter a username. |
-    | Password | Enter a password. |
-    | Confirm password    | Reenter the password. |
+    | SSH public key source | Select **Generate new key pair**. |
+    | Key pair name | Enter a name for the key pair. |
     | **Inbound port rules**  |   |
     | Public inbound ports | Select **None**. |
 
@@ -118,35 +119,40 @@ Create a Windows Server 2019 virtual machine.
     | Public IP | Take the default Standard SKU public IP. |
     | NIC network security group | Select **Basic**. |
     | Public inbound ports | Select **Allow selected ports**. |
-    | Select inbound ports | Select **HTTP (80)**, **HTTPS (443)** and **RDP (3389)**. |
+    | Select inbound ports | Select **HTTP (80)** and **HTTPS (443)**. |
 
 1. Select **Review + create**.
 1. Review the settings, and then select **Create**.
 
 This deployment may take a few minutes to complete.
 
 > [!NOTE]
-> **Web-01** virtual machine has an attached NIC with a Standard SKU dynamic public IP that changes every time the virtual machine is restarted.
+> The **web-01** virtual machine has an attached NIC with a Standard SKU dynamic public IP that changes every time the virtual machine is restarted.
 
-### Install IIS web server
+> [!NOTE]
+> The network security group rules block inbound SSH access from the internet. To run commands on the virtual machine, use the **Run command** feature in the Azure portal or deploy Azure Bastion. For more information about Azure Bastion, see [Quickstart: Deploy Azure Bastion with default settings](../bastion/quickstart-host-portal.md).
+
+### Install NGINX web server
+
+Install NGINX web server on **web-01** using the **Run command** feature in the Azure portal.
+
+1. In the search box at the top of the portal, enter *virtual machine*. Select **Virtual machines** in the search results.
+
+1. Select the **web-01** virtual machine.
+
+1. In the **Operations** section of the left menu, select **Run command**.
 
-Install IIS web server on **Web-01**.
+1. Select **RunShellScript**.
 
-1. In the **Overview** page of **Web-01**, select **Connect** and then **RDP**.
-1. In the **RDP** page, select **Download RDP File**.
-1. Open *Web-01.rdp*, and select **Connect**.
-1. Enter the username and password entered during virtual machine creation.
-1. On the **Server Manager** dashboard, select **Manage** then **Add Roles and Features**.
-1. Select **Server Roles** or select **Next** three times. On the **Server Roles** screen, select **Web Server (IIS)**.
-1. Select **Add Features**, and then select **Next**.
+1. In the **Run Command Script** pane, enter the following command:
 
-    :::image type="content" source="./media/tutorial-alias-pip/iis-web-server-installation.png" alt-text="Screenshot of Add Roles and Features Wizard in Windows Server 2019 showing how to install the I I S Web Server by adding Web Server role.":::
+    ```bash
+    sudo apt-get update && sudo apt-get install -y nginx
+    ```
 
-1. Select **Confirmation** or select **Next** three times, and then select **Install**. The installation process takes a few minutes to finish.
-1. After the installation finishes, select **Close**.
-1. Open a web browser. Browse to **localhost** to verify that the default IIS web page appears.
+1. Select **Run**.
 
-    :::image type="content" source="./media/tutorial-alias-pip/iis-web-server.png" alt-text="Screenshot of Internet Explorer showing the I I S Web Server default web page.":::
+1. Wait for the command to complete. The output displays the installation progress and finishes when NGINX is installed.
 
 ## Create an alias record
 
@@ -157,18 +163,18 @@ Create an alias record that points to the public IP address.
 1. In the **Add record set**, enter *web01* in the **Name**.
 1. Select **A** for the **Type**.
 1. Select **Yes** for the **Alias record set**, and then select the **Azure Resource** for the **Alias type**.
-1. Select the **Web-01-ip** public IP address for the **Azure resource**.
+1. Select the **web-01-ip** public IP address for the **Azure resource**.
 1. Select **OK**.
 
-    :::image type="content" source="./media/tutorial-alias-pip/add-public-ip-alias-inline.png" alt-text="Screenshot of adding an alias record to refer to the Azure public IP of the I I S web server using the Add record set page." lightbox="./media/tutorial-alias-pip/add-public-ip-alias-expanded.png":::
+    :::image type="content" source="./media/tutorial-alias-pip/add-public-ip-alias-inline.png" alt-text="Screenshot of adding an alias record to refer to the Azure public IP of the web server using the Add record set page." lightbox="./media/tutorial-alias-pip/add-public-ip-alias-expanded.png":::
 
 ## Test the alias record
 
 1. In the Azure portal, enter *virtual machine* in the search box at the top of the portal, and then select **Virtual machines** from the search results.
-1. Select the **Web-01** virtual machine. Note the public IP address in the **Overview** page.
-1. From a web browser, browse to `web01.contoso.com`, which is the fully qualified domain name of the **Web-01** virtual machine. You now see the IIS default web page.
+1. Select the **web-01** virtual machine. Note the public IP address in the **Overview** page.
+1. From a web browser, browse to `web01.contoso.com`, which is the fully qualified domain name of the **web-01** virtual machine. You now see the NGINX default web page.
 1. Close the web browser.
-1. Stop the **Web-01** virtual machine, and then restart it.
+1. Stop the **web-01** virtual machine, and then restart it.
 1. After the virtual machine restarts, note the new public IP address for the virtual machine.
 1. From a web browser, browse again to `web01.contoso.com`.
 

articles/dns/tutorial-alias-tm.md

@@ -6,7 +6,7 @@ services: dns
 author: asudbring
 ms.service: azure-dns
 ms.topic: tutorial
-ms.date: 09/19/2024
+ms.date: 03/03/2026
 ms.author: allensu
 ms.custom:
   - template-tutorial #Required; leave this attribute/value as-is.
@@ -90,11 +90,11 @@ Create a virtual network and a subnet to place your web servers in.
 
 ## Create web server virtual machines
 
-Create two Windows Server virtual machines, and install IIS web server on them, and then add DNS labels to their public IPs.
+Create two Linux virtual machines, install NGINX web server on them, and then add DNS labels to their public IPs.
 
 ### Create the virtual machines
 
-Create two Windows Server 2019 virtual machines.
+Create two Ubuntu virtual machines.
 
 1. In the Azure portal, enter *virtual machine* in the search box at the top of the portal, and then select **Virtual machines** from the search results.
 2. In **Virtual machines**, select **+ Create** and then select **Azure virtual machine**.
@@ -106,16 +106,17 @@ Create two Windows Server 2019 virtual machines.
     | Subscription  | Select your Azure subscription. |
     | Resource Group   | Select **TMResourceGroup**. |
     | **Instance details**   |   |
-    | Virtual machine name  | Enter *Web-01*. |
+    | Virtual machine name  | Enter *web-01*. |
     | Region    | Select **(US) East US**. |
     | Availability options  | Select **No infrastructure redundancy required**. |
     | Security type    | Select **Standard**. |
-    | Image   | Select **Windows Server 2019 Datacenter - Gen2**. |
+    | Image   | Select **Ubuntu Server 24.04 LTS - x64 Gen2**. |
     | Size   | Select your VM size. |
     | **Administrator account** |  |
+    | Authentication type | Select **SSH public key**. |
     | Username  | Enter a username. |
-    | Password  | Enter a password. |
-    | Confirm password  | Reenter the password. |
+    | SSH public key source | Select **Generate new key pair**. |
+    | Key pair name | Enter a name for the key pair. |
     | **Inbound port rules** |    |
     | Public inbound ports | Select **None**. |
 
@@ -128,57 +129,65 @@ Create two Windows Server 2019 virtual machines.
     | **Network interface** |  |
     | Virtual network | Select **myTMVNet**. |
     | Subnet  | Select **WebSubnet**. |
-    | Public IP   | Select **Create new**, and then enter *Web-01-ip* in **Name**. </br> Select **Basic** for the **SKU**, and **Static** for the **Assignment**. |
+    | Public IP   | Select **Create new**, and then enter *web-01-ip* in **Name**. Select **Standard** for the **SKU**. |
     | NIC network security group | Select **Basic**. |
     | Public inbound ports  | Select **Allow selected ports**. |
-    | Select inbound ports  | Select **HTTP (80)**, **HTTPS (443)** and **RDP (3389)**. |
+    | Select inbound ports  | Select **HTTP (80)** and **HTTPS (443)**. |
 
 6. Select **Review + create**.
 7. Review the settings, and then select **Create**.
-8. Repeat previous steps to create the second virtual machine. Enter *Web-02* in the **Virtual machine name** and *Web-02-ip* in the **Name** of **Public IP**. For the other settings, use the same information from the previous steps used with first virtual machine.
+8. Repeat previous steps to create the second virtual machine. Enter *web-02* in the **Virtual machine name** and *web-02-ip* in the **Name** of **Public IP**. For the other settings, use the same information from the previous steps used with first virtual machine.
 
 Each virtual machine deployment may take a few minutes to complete.
 
-### Install IIS web server
+> [!NOTE]
+> The network security group rules block inbound SSH access from the internet. To run commands on the virtual machines, use the **Run command** feature in the Azure portal or deploy Azure Bastion. For more information about Azure Bastion, see [Quickstart: Deploy Azure Bastion with default settings](../bastion/quickstart-host-portal.md).
+
+### Install NGINX web server
+
+Install NGINX on both **web-01** and **web-02** virtual machines using the **Run command** feature in the Azure portal.
+
+1. In the search box at the top of the portal, enter *virtual machine*. Select **Virtual machines** in the search results.
+
+1. Select the **web-01** virtual machine.
+
+1. In the **Operations** section of the left menu, select **Run command**.
+
+1. Select **RunShellScript**.
 
-Install IIS on both **Web-01** and **Web-02** virtual machines.
+1. In the **Run Command Script** pane, enter the following command:
 
-1. In the **Connect** page of **Web-01** virtual machine, select **RDP** and then **Download RDP File**.
-2. Open *Web-01.rdp* file, and select **Connect**.
-3. Enter the username and password entered during virtual machine creation.
-4. On the **Server Manager** dashboard, select **Manage** then **Add Roles and Features**.
-5. Select **Server Roles** or select **Next** three times. On the **Server Roles** screen, select **Web Server (IIS)**.
-6. Select **Add Features**, and then select **Next**.
+    ```bash
+    sudo apt-get update && sudo apt-get install -y nginx && echo 'Hello World from web-01' | sudo tee /var/www/html/index.html
+    ```
 
-    :::image type="content" source="./media/tutorial-alias-tm/iis-web-server-installation.png" alt-text="Screenshot of Add Roles and Features Wizard in Windows Server 2019 showing how to install the I I S Web Server by adding the Web Server role.":::
+1. Select **Run**.
 
-7. Select **Confirmation** or select **Next** three times, and then select **Install**. The installation process takes a few minutes to finish.
-8. After the installation finishes, select **Close**.
-9. Go to *C:\inetpub\wwwroot* and open *iisstart.htm* with Notepad or any editor of your choice to edit the default IIS web page.
-10. Replace all the text in the file with `Hello World from Web-01` and save the changes to *iisstart.htm*. 
-11. Open a web browser. Browse to **localhost** to verify that the default IIS web page appears.
+1. Wait for the command to complete. The output displays the installation progress and finishes when NGINX is installed.
 
-    :::image type="content" source="./media/tutorial-alias-tm/iis-on-web-01-vm-in-web-browser.png" alt-text="Screenshot of Internet Explorer showing the I I S Web Server default page of first virtual machine.":::
+1. Repeat the previous steps for the **web-02** virtual machine. Use the following command instead:
 
-12. Repeat previous steps to install IIS web server on **Web-02** virtual machine. Use `Hello World from Web-02` to replace all the text in *iisstart.htm*.
+    ```bash
+    sudo apt-get update && sudo apt-get install -y nginx && echo 'Hello World from web-02' | sudo tee /var/www/html/index.html
+    ```
 
 ### Add a DNS label
 
 Public IP addresses need DNS labels to work with Traffic Manager.
 
 1. In the Azure portal, enter *TMResourceGroup* in the search box at the top of the portal, and then select **TMResourceGroup** from the search results.
-2. In the **TMResourceGroup** resource group, select the **Web-01-ip** public IP address.
+1. In the **TMResourceGroup** resource group, select the **web-01-ip** public IP address.
 3. Under **Settings**, select **Configuration**.
 4. Enter *web01pip* in the **DNS name label**.
 5. Select **Save**.
 
     :::image type="content" source="./media/tutorial-alias-tm/ip-dns-name-label-inline.png" alt-text="Screenshot of the Configuration page of Azure Public IP Address showing D N S name label." lightbox="./media/tutorial-alias-tm/ip-dns-name-label-expanded.png":::
 
-6. Repeat the previous steps for the **Web-02-ip** public IP address and enter *web02pip* in the **DNS name label**.
+6. Repeat the previous steps for the **web-02-ip** public IP address and enter *web02pip* in the **DNS name label**.
 
 ## Create a Traffic Manager profile
 
-1. In the **Overview** page of **Web-01-ip** public IP address, note the IP address for later use. Repeat this step for the **Web-02-ip** public IP address.
+1. In the **Overview** page of **web-01-ip** public IP address, note the IP address for later use. Repeat this step for the **web-02-ip** public IP address.
 2. In the Azure portal, enter *Traffic Manager profile* in the search box at the top of the portal, and then select **Traffic Manager profiles**.
 3. Select **+ Create**.
 4. In the **Create Traffic Manager profile** page, enter or select the following information:
@@ -200,7 +209,7 @@ Public IP addresses need DNS labels to work with Traffic Manager.
     |---------|-------|
     | Type | Select **External endpoint**. |
     | Name | Enter *EP-Web01*. |
-    | Fully qualified domain name (FQDN) or IP | Enter the IP address for **Web-01-ip** that you noted previously.  |
+    | Fully qualified domain name (FQDN) or IP | Enter the IP address for **web-01-ip** that you noted previously.  |
     | Priority  | Enter *1*.  |
 
     :::image type="content" source="./media/tutorial-alias-tm/add-endpoint-tm-inline.png" alt-text="Screenshot of the Endpoints page in Traffic Manager profile showing selected settings for adding an endpoint." lightbox="./media/tutorial-alias-tm/add-endpoint-tm-expanded.png":::
@@ -212,7 +221,7 @@ Public IP addresses need DNS labels to work with Traffic Manager.
     |---------|-------|
     | Type | Select **External endpoint**. |
     | Name   | Enter *EP-Web02*. |
-    | Fully qualified domain name (FQDN) or IP | Enter the IP address for **Web-02-ip** that you noted previously.  |
+    | Fully qualified domain name (FQDN) or IP | Enter the IP address for **web-02-ip** that you noted previously.  |
     | Priority  | Enter *2*. |
 
 ## Create an alias record
@@ -234,9 +243,9 @@ Create an alias record that points to the Traffic Manager profile.
 
 ## Test the alias record
 
-1. From a web browser, browse to `contoso.com` or your apex domain name. You see the IIS default page with `Hello World from Web-01`. The Traffic Manager directed traffic to **Web-01** IIS web server because it has the highest priority. Close the web browser and shut down **Web-01** virtual machine. Wait a few minutes for the virtual machine to completely shut down.
+1. From a web browser, browse to `contoso.com` or your apex domain name. You see the NGINX page with `Hello World from web-01`. The Traffic Manager directed traffic to **web-01** because it has the highest priority. Close the web browser and shut down **web-01** virtual machine. Wait a few minutes for the virtual machine to completely shut down.
 2. Open a new web browser, and browse again to `contoso.com` or your apex domain name.
-3. You should see the IIS default page with `Hello World from Web-02`. The Traffic Manager handled the situation and directed traffic to the second IIS server after shutting down the first server that has the highest priority.
+3. You should see the NGINX page with `Hello World from web-02`. The Traffic Manager handled the situation and directed traffic to the second web server after shutting down the first server that has the highest priority.
 
 ## Clean up resources