Firewall

90
Total Pages
40
Linux-Friendly Pages
50
Pages with Bias
55.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

332 issues found
Showing 251-275 of 332 flagged pages
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Terraform ...e-docs/blob/main/articles/firewall/deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively deploying Windows Server virtual machines in the example environment. There are no Linux VM examples or references, and the creation of Windows VMs is explicitly listed in the checklist. This may lead users to assume that only Windows is supported or recommended for this scenario.
Recommendations
  • Add equivalent examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside the Windows VM steps.
  • Mention Linux as a supported/tested option in the checklist and summary sections.
  • Provide sample Terraform code for both Windows and Linux VM deployments.
  • Clarify that the firewall and network setup are OS-agnostic and can be used with either Windows or Linux workloads.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Terraform ...rticles/firewall/quick-create-multiple-ip-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively deploying Windows Server 2019 virtual machines and focusing on enabling RDP connections. There are no examples or instructions for deploying Linux VMs, nor are SSH access patterns discussed. The referenced PowerShell article is mentioned before any Linux or CLI alternatives, and the checklist only covers Windows VM creation.
Recommendations
  • Add parallel examples for deploying Linux virtual machines using azurerm_linux_virtual_machine.
  • Include SSH access patterns and NAT rule examples for Linux VMs alongside RDP for Windows.
  • Reference Azure CLI and Bash-based deployment guides equally or before PowerShell articles.
  • Update the checklist to mention both Windows and Linux VM creation.
  • Ensure troubleshooting and verification steps include Linux VM scenarios.
GitHub Create Pull Request
Firewall Azure Firewall SNAT private IP address ranges ...docs/blob/main/articles/firewall/snat-private-range.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides extensive Azure PowerShell examples and instructions, with PowerShell presented before Azure CLI in both the method table and detailed sections. There are no Linux-specific shell examples (e.g., bash scripting), and the CLI examples are generic, not tailored to Linux environments. The documentation assumes familiarity with PowerShell, which is traditionally a Windows tool, and does not mention Linux-specific considerations or tools.
Recommendations
  • Add bash and shell script examples for configuring Azure Firewall SNAT private IP address ranges, especially for ARM template deployments and Azure CLI usage.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Consider reordering the method table and sections to present Azure CLI before PowerShell, or present them side-by-side to avoid implicit prioritization.
  • Include troubleshooting or configuration notes relevant to Linux environments (e.g., file permissions, environment variables, etc.).
  • If PowerShell is required on Linux, provide guidance on installing and using PowerShell Core on Linux systems.
GitHub Create Pull Request
Firewall Azure Firewall threat intelligence based filtering ...azure-docs/blob/main/articles/firewall/threat-intel.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a hosts file modification example specifically for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS systems. No Linux or cross-platform examples are given for testing or configuration steps.
Recommendations
  • Include instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
  • Provide cross-platform examples or explicitly state steps for both Windows and Linux/macOS environments.
  • Review other sections for tool or command references and ensure Linux parity where applicable.
GitHub Create Pull Request
Firewall Deploy & configure Azure Firewall using the Azure portal ...n/articles/firewall/tutorial-firewall-deploy-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively using Windows Server as the example operating system for the test virtual machine, and by providing instructions for remote desktop (RDP) and Internet Explorer, which are Windows-centric. There are no examples or guidance for deploying or testing with Linux VMs, nor instructions for SSH or Linux-based browsers. The mention of PowerShell is limited to a link, but the main walkthrough is entirely Windows-focused.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the test subnet, with example settings.
  • Provide guidance for connecting to the Linux VM via SSH, including port configuration and firewall rules.
  • Offer testing steps using a Linux browser (e.g., Firefox) or command-line tools (e.g., curl, wget) to verify firewall rules.
  • Show how to configure DNS settings on a Linux VM's network interface.
  • Ensure that references to remote access (RDP) are balanced with SSH examples for Linux.
  • Add notes or sections highlighting differences or considerations for Linux users throughout the guide.
GitHub Create Pull Request
Firewall Tutorial: Deploy & configure Azure Firewall and policy using the Azure portal ...les/firewall/tutorial-firewall-deploy-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively using Windows Server as the example operating system for the workload VM, and by instructing users to test the firewall using Remote Desktop and Microsoft Edge. There are no Linux VM deployment instructions, nor any Linux-based testing scenarios (e.g., SSH, curl, or browser usage on Linux). The tutorial assumes familiarity with Windows tools and patterns, omitting Linux equivalents.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including required configuration steps.
  • Include Linux-based testing examples, such as connecting via SSH and using curl or a Linux browser to verify firewall rules.
  • Mention Linux as a supported platform for the workload VM, and clarify that the firewall works for both Windows and Linux workloads.
  • Where remote desktop is referenced, also provide SSH instructions for Linux VMs.
  • Ensure that screenshots and step-by-step instructions do not assume Windows-only environments.
GitHub Create Pull Request
Firewall Tutorial: Filter inbound Internet or intranet traffic with Azure Firewall DNAT policy using the portal ...ain/articles/firewall/tutorial-firewall-dnat-policy.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using a Windows Server virtual machine as the example workload and instructing users to test DNAT using Remote Desktop (RDP), which is a Windows-centric protocol. There are no examples or instructions for deploying a Linux VM, nor for testing access using SSH or other Linux-relevant tools. All step-by-step instructions for VM creation and connectivity assume a Windows environment, omitting Linux alternatives.
Recommendations
  • Add parallel instructions for creating a Linux-based virtual machine (e.g., Ubuntu Server) in the 'Create a virtual machine' section.
  • Include steps for testing DNAT access to the Linux VM using SSH (port 22), alongside or instead of the RDP example.
  • When describing DNAT rule creation, provide examples for both RDP (Windows) and SSH (Linux) scenarios.
  • In the 'Test the firewall' section, show how to connect using both Remote Desktop (for Windows) and SSH clients (for Linux), including example commands.
  • Consider using neutral language such as 'workload VM' and avoid assuming the OS unless necessary for the scenario.
  • Where possible, present Windows and Linux options side by side to ensure parity and inclusivity.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Terraform ...e-docs/blob/main/articles/firewall/deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively deploys Windows Server virtual machines in its example environment and does not mention or provide equivalent Linux VM examples. The VM creation steps and resource references are all for Windows, with no discussion of Linux alternatives or parity. This creates a Windows-first bias and omits Linux-focused guidance.
Recommendations
  • Add instructions and Terraform resource examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside or instead of Windows VMs.
  • Include sample code for creating random passwords for Linux VMs and configuring SSH access.
  • Mention Linux as an option in the network topology description, and clarify that either Windows or Linux VMs can be used.
  • Provide troubleshooting and verification steps relevant to Linux VMs (such as SSH connectivity checks).
  • Balance references to Windows and Linux in all checklist and implementation steps to ensure cross-platform parity.
GitHub Create Pull Request
Firewall Deploy & configure Azure Firewall Basic and policy using the Azure portal ...ticles/firewall/deploy-firewall-basic-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server for the workload VM and only provides instructions for connecting via Remote Desktop and testing with Internet Explorer, both of which are Windows-centric. There are no Linux VM deployment examples, nor instructions for SSH access or Linux-based testing, which may disadvantage users on Linux platforms.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include examples for connecting to the Linux VM via SSH, and testing outbound connectivity using Linux tools (e.g., curl, dig).
  • Mention Linux equivalents for remote access and browser testing, such as using Firefox or Chrome.
  • Clarify that the firewall configuration applies to both Windows and Linux workloads, and provide guidance for both.
  • Where possible, use neutral language and examples that are applicable to both platforms.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Bicep ...azure-docs/blob/main/articles/firewall/deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively deploying Windows Server virtual machines in the example environment. There are no Linux VM examples or mentions, and the scenario is described as deploying 'two Windows Server virtual machines, a jump box, and a server.' While deployment and resource management instructions use both Azure CLI and PowerShell (which are cross-platform), the VM operating system choice is Windows-only, and no Linux alternatives or parity are presented.
Recommendations
  • Add examples that deploy Linux-based virtual machines (e.g., Ubuntu, CentOS) alongside or instead of Windows Server VMs.
  • Explicitly mention that the jump box and server can be Linux or Windows, and provide parameter options for either OS.
  • Include sample Bicep code snippets or parameter files for deploying Linux VMs.
  • Clarify that the Azure CLI and PowerShell instructions are cross-platform, and provide any OS-specific notes if relevant.
  • Ensure screenshots, walkthroughs, and troubleshooting steps cover both Windows and Linux scenarios.
GitHub Create Pull Request
Firewall Tutorial: Filter inbound Internet or intranet traffic with Azure Firewall DNAT policy using the portal ...ain/articles/firewall/tutorial-firewall-dnat-policy.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using a Windows Server virtual machine as the workload example and instructing users to test connectivity via Remote Desktop (RDP), which is a Windows-centric protocol. There are no examples or instructions for deploying a Linux VM, nor are there alternative test methods (such as SSH) provided for Linux users. The documentation does not mention or show parity for Linux-based scenarios.
Recommendations
  • Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet.
  • Include testing steps using SSH to connect to a Linux VM through the firewall, alongside the RDP/Windows example.
  • When describing the creation of the VM, offer both Windows and Linux options, and clarify any differences in firewall rules (e.g., port 22 for SSH).
  • In the 'Test the firewall' section, provide Linux-specific connection instructions in addition to RDP.
  • Ensure that all screenshots, code snippets, and portal steps are inclusive of both Windows and Linux scenarios.
GitHub Create Pull Request
Firewall Deploy & configure Azure Firewall using the Azure portal ...n/articles/firewall/tutorial-firewall-deploy-portal.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example operating system for the workload VM, and all testing instructions reference Windows-specific tools (Remote Desktop, Internet Explorer). There are no Linux VM deployment steps, nor are there instructions for connecting to or testing with a Linux system. This creates a Windows-first bias and omits Linux parity.
Recommendations
  • Add parallel instructions for deploying a Linux-based VM (e.g., Ubuntu) in the workload subnet.
  • Include Linux-specific connection and testing steps, such as SSH for remote access and using browsers like Firefox or Chrome for web testing.
  • Mention Linux as an option when describing VM image selection, and provide example administrator credentials and setup steps for Linux.
  • Provide guidance for configuring DNS on Linux network interfaces.
  • Ensure that all firewall rule testing steps are applicable to both Windows and Linux environments.
GitHub Create Pull Request
Firewall Tutorial: Deploy a firewall with Azure DDoS Protection ...in/articles/firewall/tutorial-protect-firewall-ddos.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a bias toward Windows by exclusively using Windows Server as the example workload VM and referencing remote desktop (RDP) for connectivity and testing. There are no Linux VM deployment or SSH connectivity examples, nor are Linux tools or patterns mentioned. The documentation assumes Windows as the default platform for testing and management, omitting Linux alternatives.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Provide examples for connecting to the Linux VM using SSH, including configuring NAT rules for port 22.
  • Show how to test firewall rules from a Linux VM (e.g., using curl or wget instead of Internet Explorer).
  • Mention Linux tools and patterns (e.g., using the Azure CLI on Linux, or testing DNS resolution with dig/nslookup).
  • Clarify that the tutorial applies to both Windows and Linux workloads, and provide links to relevant Linux documentation.
GitHub Create Pull Request
Firewall Azure Firewall features by SKU ...re-docs/blob/main/articles/firewall/features-by-sku.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows-related concepts (such as the Windows Update FQDN tag) are mentioned as the primary example for FQDN tags, and Windows tools (PowerShell) are listed first in the DevOps integration section before CLI and Terraform. There are no explicit Linux-only examples or tools highlighted, and Linux equivalents are not given equal prominence.
Recommendations
  • Provide Linux-specific examples alongside Windows ones, such as referencing Linux update services (e.g., Ubuntu or Red Hat repositories) when discussing FQDN tags.
  • List cross-platform tools (Azure CLI, Terraform) before or alongside PowerShell in DevOps integration sections to avoid implying PowerShell is the primary or preferred method.
  • Include explicit Linux management and deployment scenarios or references, such as using Bash scripts or Linux-native tools for Azure Firewall configuration.
  • When giving examples (e.g., for FQDN tags), alternate between Windows and Linux services to ensure parity.
  • Add a section or callout for Linux administrators, highlighting any considerations or best practices specific to Linux environments.
GitHub Create Pull Request
Firewall FQDN tags overview for Azure Firewall ...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows services and products (e.g., Windows Update, Windows Diagnostics, Windows Virtual Desktop, Windows365) in its examples and FQDN tags. There are no explicit examples or references to Linux-specific services or endpoints, nor are Linux equivalents mentioned alongside Windows ones. The documentation does not provide parity for Linux administrators or highlight how FQDN tags could be used for Linux-centric scenarios.
Recommendations
  • Include examples of using FQDN tags for Linux-based services, such as Azure Linux VM management endpoints or popular Linux distributions' update servers.
  • Add references to Linux equivalents where Windows services are mentioned (e.g., mention how to allow outbound traffic for Ubuntu/Debian repositories alongside Windows Update).
  • Provide guidance or examples for Linux administrators, such as configuring application rules for Linux-based workloads or endpoints.
  • Ensure that documentation tables and lists include both Windows and Linux services where applicable, or clarify the scope if FQDN tags are only available for Microsoft services.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Terraform ...rticles/firewall/quick-create-multiple-ip-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by focusing exclusively on deploying Windows Server 2019 virtual machines and enabling RDP access, with no mention or example of Linux VM deployment or SSH access. References to firewall NAT rules and password generation are tailored to Windows scenarios, and there is no parity for Linux users. Additionally, the only linked alternative deployment guide uses Azure PowerShell, which is more commonly associated with Windows environments.
Recommendations
  • Add examples for deploying Linux virtual machines using azurerm_linux_virtual_machine, including SSH key generation and access.
  • Include NAT rule collection examples for SSH (port 22) alongside RDP (port 3389) to demonstrate Linux VM connectivity.
  • Reference and link to documentation for deploying Azure Firewall with multiple public IP addresses using Azure CLI or Bash, not just PowerShell.
  • Ensure checklist and resource creation steps mention both Windows and Linux VM options.
  • Provide sample Terraform code and verification steps for Linux VM scenarios.
GitHub Create Pull Request
Firewall Azure Firewall SNAT private IP address ranges ...docs/blob/main/articles/firewall/snat-private-range.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration examples for Azure Firewall SNAT private IP address ranges using Azure PowerShell, Azure CLI, ARM templates, and the Azure portal. However, the PowerShell examples are more extensive and detailed, including step-by-step instructions and multiple scenarios (new/existing firewall, policy updates, auto-learn features). PowerShell is a Windows-centric tool, and its prominence may indicate a Windows bias. Additionally, PowerShell instructions are presented before CLI examples, suggesting a 'Windows-first' ordering. There are no Linux-specific shell (e.g., Bash) examples, nor are there references to Linux-native tools or patterns.
Recommendations
  • Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples, covering all scenarios (new/existing firewall, policy updates, auto-learn features).
  • Consider providing Bash or Linux shell script equivalents for common configuration tasks, especially for scenarios where Azure CLI is supported.
  • Where possible, present Azure CLI examples before or alongside PowerShell examples to avoid implicit prioritization of Windows tools.
  • Explicitly mention cross-platform compatibility for CLI and ARM template methods, and clarify any limitations or differences for Linux users.
  • Add a section or note highlighting best practices for Linux administrators, including links to relevant Azure CLI documentation and troubleshooting tips for Linux environments.
GitHub Create Pull Request
Firewall Azure Firewall threat intelligence based filtering ...azure-docs/blob/main/articles/firewall/threat-intel.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a hosts file modification example specifically for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS systems. This prioritizes Windows instructions and omits guidance for users on other platforms.
Recommendations
  • Include Linux and macOS hosts file modification instructions (e.g., /etc/hosts).
  • Present cross-platform examples side-by-side or in a dedicated section for each OS.
  • Avoid assuming the administrator is using Windows; use neutral language or clarify steps for all major platforms.
GitHub Create Pull Request
Firewall Tutorial: Deploy & configure Azure Firewall and policy using the Azure portal ...les/firewall/tutorial-firewall-deploy-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates deploying and testing Azure Firewall using a Windows Server virtual machine. All instructions for VM creation, remote access (RDP), and testing (Microsoft Edge, Internet Explorer) are Windows-centric, with no mention of Linux VM deployment, SSH access, or Linux-based testing. This creates a Windows-first bias and omits Linux parity in examples and guidance.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include SSH-based access instructions for Linux VMs, alongside RDP for Windows.
  • Provide Linux-specific testing steps (e.g., using curl, wget, or a browser like Firefox/Chromium) to verify firewall rules.
  • Mention how to configure DNS settings on Linux VMs (e.g., editing /etc/resolv.conf or using netplan).
  • Clarify that the firewall and policy configuration applies equally to Linux and Windows workloads.
  • Where possible, alternate or combine Windows and Linux examples throughout the tutorial.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-terraform.md ...e-docs/blob/main/articles/firewall/deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively deploying Windows Server virtual machines in the example environment. There is no mention of Linux VM deployment or examples, and the quickstart only references Windows-specific resources (azurerm_windows_virtual_machine) without Linux equivalents. This may lead users to assume that only Windows is supported or recommended for such scenarios.
Recommendations
  • Include examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside Windows examples.
  • Explicitly mention that both Windows and Linux VMs are supported and provide guidance for each.
  • Add sample Terraform code snippets for Linux VM creation and configuration.
  • Clarify in the introduction that the choice of OS for VMs is flexible and depends on user requirements.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/threat-intel.md ...azure-docs/blob/main/articles/firewall/threat-intel.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a hosts file modification example specifically for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS systems. No Linux or cross-platform examples are given for testing or configuration steps.
Recommendations
  • Include instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
  • Provide cross-platform examples for all steps, ensuring parity between Windows and Linux/macOS.
  • Explicitly state that the process applies to multiple operating systems and clarify any OS-specific differences.
  • Where possible, use generic terminology or provide parallel examples for both Windows and Linux environments.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-bicep.md ...azure-docs/blob/main/articles/firewall/deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively deploying Windows Server VMs in the example environment and not mentioning or providing Linux VM equivalents. All virtual machine examples are Windows-based, and there is no discussion of deploying Linux servers or jumpboxes, which may exclude or discourage Linux users. However, command-line instructions are provided for both Azure CLI (cross-platform) and PowerShell, so tooling bias is minimal.
Recommendations
  • Include examples of deploying Linux virtual machines (e.g., Ubuntu, CentOS) alongside or instead of Windows Server VMs in the Bicep file and documentation.
  • Explicitly mention that the jump box and server can be either Windows or Linux, and provide parameter options or guidance for both.
  • Add Linux-specific notes or troubleshooting tips where relevant (e.g., SSH access, cloud-init configuration).
  • Ensure screenshots, walkthroughs, and sample outputs reflect both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-firewall-basic-portal-policy.md ...ticles/firewall/deploy-firewall-basic-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example OS for the workload VM and only demonstrates remote desktop (RDP) access and Internet Explorer for testing. There are no Linux VM deployment steps, nor are SSH or Linux-based browser/test instructions provided. This creates a Windows-first bias and omits Linux parity in deployment and testing.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including relevant configuration steps.
  • Include SSH access examples for Linux VMs in the DNAT rule section, alongside RDP for Windows.
  • Provide Linux-based browser testing steps (e.g., using Firefox or Chrome) and DNS resolution commands (e.g., dig, nslookup) for firewall rule validation.
  • Explicitly mention that the firewall setup applies to both Windows and Linux workloads, and provide links to Linux VM creation documentation.
  • Where PowerShell or Windows-specific tools are referenced, offer equivalent CLI or Bash commands for Linux users.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/integrate-with-nat-gateway.md ...b/main/articles/firewall/integrate-with-nat-gateway.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for associating a NAT gateway with an Azure Firewall subnet using Azure PowerShell and Azure CLI, with PowerShell (commonly used on Windows) presented first and in greater detail. There are no examples for Linux-native tools (e.g., Bash scripts, REST API, Terraform), and the PowerShell example is more verbose, potentially implying a Windows-centric workflow.
Recommendations
  • Add Bash script examples using Azure CLI to demonstrate Linux-native workflows.
  • Include REST API or ARM template examples for platform-neutral automation.
  • Present Azure CLI (cross-platform) examples before PowerShell to avoid Windows-first ordering.
  • Mention that Azure CLI is available on both Windows and Linux, and clarify platform compatibility for each example.
  • Consider adding Terraform or Ansible examples for infrastructure-as-code parity.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-terraform.md ...rticles/firewall/quick-create-multiple-ip-terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by focusing exclusively on deploying Windows Server 2019 VMs and enabling RDP connections, with no mention or example of Linux VMs or SSH access. Additionally, references to related documentation (e.g., PowerShell deployment) are Windows-centric, and there are no Linux-specific instructions or parity in examples.
Recommendations
  • Include examples for deploying Linux virtual machines alongside Windows VMs, using azurerm_linux_virtual_machine.
  • Demonstrate how to configure NAT/firewall rules for SSH access to Linux VMs, not just RDP for Windows.
  • Reference Linux equivalents (e.g., Bash, SSH) in related documentation and troubleshooting sections.
  • Provide sample Terraform code and verification steps for Linux VM scenarios.
  • Ensure that links to further reading or tutorials include Linux-focused content where applicable.
GitHub Create Pull Request
← Previous Page 11 of 14 Next →