Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

Bias Analysis

Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation exhibits a clear Windows bias: virtual machine creation is demonstrated exclusively with Windows Server, IIS installation is shown only via PowerShell, and host file editing and DNS commands use Windows-specific paths and tools. There are no Linux VM examples, nor instructions for Apache/Nginx setup, nor Linux shell commands for host file editing or DNS cache management.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend server.
  • Provide Linux-based web server setup steps (e.g., install Apache or Nginx) using Bash or Azure CLI.
  • Include host file editing instructions for Linux/macOS (e.g., /etc/hosts) and relevant commands for DNS cache flushing (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service network-manager restart').
  • Show Azure CLI examples alongside PowerShell for VM extension installation and other automation tasks.
  • Clarify that Application Gateway supports both Windows and Linux backend servers, and provide links to relevant Linux documentation.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-12 00:00 #99 completed Biased Biased
2026-01-11 06:20 #98 completed Clean Clean
2026-01-11 00:00 #95 cancelled Clean Clean
2026-01-10 00:00 #92 completed Clean Clean
2026-01-09 00:00 #87 cancelled Clean Clean
2026-01-06 22:28 #78 completed Clean Clean
2025-12-29 18:00 #48 cancelled Biased Biased
2025-12-15 00:00 #7 completed Clean Clean
2025-12-14 05:05 #6 completed Clean Clean

Flagged Code Snippets

3. Create a second virtual machine and install IIS using the steps that you previously completed. Use *fabrikamVM* for the virtual machine name and for the **VMName** setting of the **Set-AzVMExtension** cmdlet.

### Add backend servers to backend pools

1. Select **All resources**, and then select **myAppGateway**.

2. Select **Backend pools** from the left menu.

3. Select **contosoPool**.

4. Under **Target type**, select **Virtual machine** from the drop-down list.

5. Under **Target**, select the **contosoVM** virtual machine's network interface from the drop-down list.

    ![Add backend servers](./media/create-multiple-sites-portal/edit-backend-pool.png)

6. Select **Save**.
7. Repeat to add the *fabrikamVM* and interface to the *fabrikamPool*.

Wait for the deployment to complete before proceeding to the next step.

## Edit your hosts file for name resolution

After the application gateway is created with its public IP address, you can get the IP address, and use it to edit your hosts file to resolve `www.contoso.com` and `www.fabrikam.com`. In a production environment, you could create a `CNAME` in DNS for name resolution.

1. Select **All resources**, and then select **myAGPublicIPAddress**.

    ![Record application gateway DNS address](./media/create-multiple-sites-portal/public-ip.png)

2. Copy the IP address and use it as the value for new entries your `hosts` file.
1. On your local machine, open an administrative command prompt, and navigate to `c:\Windows\System32\drivers\etc`.
1. Open the `hosts` file, and add the following entries, where `x.x.x.x` is the application gateway's public IP address:
   
1. Save the file.
1. Run the following commands to load and display the changes to your hosts file: