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

Bias Types:
⚠️ windows_first
⚠️ powershell_heavy
⚠️ missing_linux_example
⚠️ windows_tools
Summary:
The documentation demonstrates a clear Windows bias: it exclusively uses Windows Server for backend VMs, provides only PowerShell commands for configuration (specifically for installing IIS), and gives instructions for editing the Windows hosts file and using Windows-specific networking commands (ipconfig). There are no Linux-based examples, nor are there instructions for performing equivalent steps on Linux systems.
Recommendations:
  • Include parallel Linux examples for backend VMs, such as using Ubuntu or another popular Linux distribution.
  • Provide Bash/Azure CLI commands for installing a web server (e.g., Apache or Nginx) on Linux VMs, alongside the PowerShell/IIS example.
  • Add instructions for editing the /etc/hosts file on Linux/macOS systems, and mention the use of 'sudo systemctl restart systemd-resolved' or 'sudo systemd-resolve --flush-caches' for DNS cache flushing.
  • When referencing command-line tools, offer both Windows (ipconfig) and Linux/macOS (ifconfig, ip, or systemd-resolve) equivalents.
  • Where possible, use cross-platform Azure CLI commands instead of (or in addition to) PowerShell.
  • Explicitly state that the Application Gateway supports both Windows and Linux backend servers, and provide guidance for both.
GitHub Create pull request

Scan History

Date Scan ID Status Bias Status
2025-08-17 00:01 #83 in_progress ✅ Clean
2025-07-13 21:37 #48 completed ❌ Biased
2025-07-09 13:09 #3 cancelled ✅ Clean
2025-07-08 04:23 #2 cancelled ❌ Biased

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: