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 201-225 of 332 flagged pages
Firewall Customer provided public IP address support in secured hubs ...in/articles/firewall/secured-hub-customer-public-ip.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides configuration instructions for customer-provided public IP addresses in Azure Firewall secured hubs using only Azure PowerShell commands, which are primarily Windows-centric. There are no CLI (az), Bash, or Linux/macOS-specific examples. The PowerShell approach is presented before any mention of cross-platform alternatives, and no Linux-native tools or patterns are referenced.
Recommendations
  • Add Azure CLI (az) examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or provide Bash script equivalents.
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are shown before or alongside PowerShell.
  • Include notes or links for Linux/macOS users on how to perform equivalent tasks.
GitHub Create Pull Request
Firewall Overview of Azure Firewall service tags ...azure-docs/blob/main/articles/firewall/service-tags.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only Azure PowerShell examples for configuring Azure Firewall service tags, with no equivalent Azure CLI or Bash examples. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not the default shell on non-Windows platforms. The configuration section is Windows-centric, and Linux users must seek out CLI documentation elsewhere.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to CLI documentation.
  • Consider showing CLI/Bash examples before or alongside PowerShell to improve parity.
  • Note any platform-specific differences in command usage or prerequisites.
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-14 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 test VM, and all testing instructions (such as remote desktop and browser usage) assume a Windows environment. There are no Linux or macOS examples or alternatives provided for deploying, configuring, or testing Azure Firewall, which may hinder non-Windows users.
Recommendations
  • Provide parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the test subnet, including SSH access setup.
  • Include testing steps for Linux users, such as using SSH to connect to the VM and using curl or wget to test outbound access.
  • Mention Linux/macOS tools and methods for DNS configuration and firewall rule verification.
  • Clarify that the procedure is not limited to Windows and provide links or references to Linux/macOS documentation where relevant.
GitHub Create Pull Request
Firewall Tutorial: Deploy and configure Azure Firewall and policy in a hybrid network using the Azure portal ...ain/articles/firewall/tutorial-hybrid-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a notable Windows bias: all virtual machine examples use Windows Server, IIS installation is shown only via PowerShell, and there are no Linux VM or shell examples. Windows tools and patterns (RDP, PowerShell, Windows Server Marketplace images) are used exclusively or presented first, with no mention of Linux alternatives or parity.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the spoke and on-premises networks.
  • Provide Linux-specific commands for installing a web server (e.g., Apache or Nginx) using Bash/Cloud Shell.
  • Include SSH connection instructions for Linux VMs, alongside RDP for Windows.
  • Show how to test firewall rules using Linux tools (e.g., curl, ssh) in addition to Windows tools.
  • Ensure all PowerShell examples have Bash/Azure CLI equivalents.
  • Present both Windows and Linux options side-by-side, rather than Windows-only or Windows-first.
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-14 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 detailed and appear first in most sections, which may indicate a Windows-first and PowerShell-heavy bias. There are no explicit Linux/macOS-specific instructions or shell script examples, but Azure CLI and ARM template methods are cross-platform. The bias is moderate, as Linux/macOS users can still follow the CLI and template instructions, but may find the PowerShell focus less relevant.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide any necessary shell-specific notes.
  • Add bash or shell script equivalents for tasks currently shown only in PowerShell.
  • Clarify that ARM template and portal methods are OS-agnostic.
  • Consider a section summarizing platform compatibility for each method.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the example workload VM and only describes connecting via Remote Desktop (RDP), which is a Windows-centric protocol. There are no Linux VM deployment instructions, nor examples for SSH access or Linux remote connectivity. This creates friction for users wanting to follow the tutorial with Linux or non-Windows workloads.
Recommendations
  • Provide parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include examples for connecting to the Linux VM using SSH through the firewall (e.g., DNAT rule for port 22).
  • Clarify that the DNAT rule can be used for protocols other than RDP, such as SSH or HTTP, and provide sample configurations.
  • When listing VM images, mention both Windows and Linux options.
  • In testing steps, show how to connect to the Linux VM using SSH from a client machine.
GitHub Create Pull Request
Firewall Filter inbound Internet or intranet traffic with Azure Firewall DNAT using the portal .../blob/main/articles/firewall/tutorial-firewall-dnat.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates the creation and testing of a Windows Server 2019 VM, and the only connectivity test described is via Remote Desktop Protocol (RDP) to port 3389, which is a Windows-specific scenario. There are no examples or instructions for deploying a Linux VM, nor for testing DNAT with Linux-compatible protocols (such as SSH on port 22). This creates friction for Linux/macOS users who may wish to deploy and test with Linux workloads.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the spoke subnet.
  • Include DNAT rule examples for Linux scenarios, such as forwarding port 22 for SSH access.
  • Provide testing steps for Linux users, such as connecting via SSH from a remote client.
  • Clarify that the procedure applies to both Windows and Linux workloads, and highlight any OS-specific considerations.
  • Consider presenting both Windows and Linux examples side-by-side, or alternate which is shown first.
GitHub Create Pull Request
Firewall Tutorial: Deploy Azure Firewall private IP DNAT for overlapped and nonroutable networks ...lob/main/articles/firewall/tutorial-private-ip-dnat.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the VM setup and configuration sections. All example scripts and instructions for configuring and testing virtual machines use PowerShell and target Windows VMs (e.g., win-vm-2, win-vm-3). There are no Linux VM configuration or testing instructions, nor are there Bash or Linux shell script equivalents. The tutorial implicitly assumes users are working with Windows environments, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Linux VM setup instructions, including Bash scripts for configuration.
  • Include examples for connecting to and configuring Linux VMs (e.g., via SSH and shell scripts).
  • Offer parity in testing steps, showing how to test DNAT functionality from Linux clients.
  • Present both Windows and Linux examples side-by-side, or clarify OS requirements early in the tutorial.
  • Reference cross-platform tools (e.g., Azure CLI, SSH) where possible, not just Windows-specific ones.
GitHub Create Pull Request
Firewall Deploy and configure Azure Firewall in a hybrid network by using the Azure portal .../blob/main/articles/firewall/tutorial-hybrid-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias. All virtual machine creation examples use Windows Server 2019 Datacenter images, with no mention of Linux alternatives. The IIS installation step is performed exclusively via Azure PowerShell, with no Bash or Linux equivalent provided. Testing and remote access instructions rely on RDP and Windows-based workflows. There are no examples or guidance for deploying Linux VMs, installing Apache/Nginx, or using SSH for connectivity and testing.
Recommendations
  • Include parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu, CentOS) in both the spoke and on-premises networks.
  • Provide examples for installing and testing with Apache or Nginx on Linux VMs, using Bash or Azure CLI commands.
  • Add SSH-based connectivity and testing steps for Linux VMs, alongside RDP for Windows.
  • Offer both PowerShell and Bash/Azure CLI examples for VM extension installation and configuration.
  • Explicitly mention that the firewall and network setup applies equally to Linux workloads, and link to relevant Linux documentation.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates deployment and testing using a Windows Server virtual machine, with instructions for remote desktop (RDP) and Internet Explorer. There are no examples or guidance for deploying a Linux VM, connecting via SSH, or testing with Linux tools/browsers. The only alternative mentioned is a link to an Azure PowerShell version, which is also Windows-centric.
Recommendations
  • Add instructions for creating a Linux virtual machine (e.g., Ubuntu) in the same subnet, including username/password/SSH key setup.
  • Provide guidance for connecting to the Linux VM via SSH, including firewall DNAT rule examples for port 22.
  • Include Linux-based testing steps, such as using curl/wget or Firefox/Chrome to verify outbound access.
  • Show how to configure DNS on a Linux VM (e.g., editing /etc/resolv.conf or using netplan).
  • Ensure parity in examples and screenshots, showing both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Firewall Configure customer-controlled maintenance for Azure Firewall ...n/articles/firewall/customer-controlled-maintenance.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The Azure portal instructions (which are most detailed and illustrated) implicitly assume a Windows environment, as the Azure portal is most commonly accessed from Windows and the screenshots are likely Windows-based. The PowerShell section is presented before the CLI section, and PowerShell is a Windows-native tool (though available on Linux, it's less commonly used there). The CLI section is present and provides parity, but is listed after PowerShell, and the introductory text and examples favor PowerShell. There are no explicit Linux/macOS examples, nor are Linux-specific considerations mentioned.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, and provide installation links.
  • Include screenshots or notes that the Azure portal is accessible from any OS/browser, not just Windows.
  • Add a brief section or callout for Linux/macOS users, confirming that all steps are OS-agnostic except for tool choice.
  • Where possible, provide Bash shell examples for scripting tasks.
  • Ensure that references to time zones or file paths do not assume Windows conventions.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Bicep ...in/articles/firewall/quick-create-multiple-ip-bicep.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows Server 2019 virtual machines for RDP access, referencing Remote Desktop Connection (a Windows tool), and omitting Linux VM deployment or SSH connectivity examples. The cleanup instructions use only Azure PowerShell, with no Bash or CLI alternatives. While Azure CLI is mentioned for deployment, the overall workflow and validation steps are tailored to Windows environments.
Recommendations
  • Include examples for deploying and connecting to Linux virtual machines (e.g., SSH access).
  • Mention and demonstrate Linux/macOS tools for remote access, such as SSH clients.
  • Provide cleanup instructions using Azure CLI (az group delete) alongside PowerShell.
  • Clarify that the Bicep template can be used for both Windows and Linux VMs, or provide a Linux-focused template variant.
  • Add notes or sections for macOS/Linux users, especially for validation and connection steps.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by focusing on deploying Windows Server VMs and enabling RDP, with no mention of Linux VM deployment or SSH access. Additionally, the only referenced scenario for connecting to VMs is RDP to Windows, and there are no Linux-specific instructions or examples provided.
Recommendations
  • Include parallel examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside Windows VM examples.
  • Demonstrate NAT/firewall rules for SSH (port 22) access to Linux VMs, not just RDP for Windows.
  • Reference documentation or tutorials for deploying and connecting to Linux VMs in Azure Firewall scenarios.
  • Ensure that any troubleshooting or verification steps include Linux-compatible commands and scenarios.
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-14 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, referencing the Windows file path. There is no mention of how to perform the same action on Linux or macOS, nor are alternative file paths or commands provided for those platforms.
Recommendations
  • Include instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
  • Provide example commands for editing the hosts file using common Linux/macOS tools (e.g., nano, vi, sudo).
  • Present platform-specific instructions in parallel, or use a tabbed format for Windows, Linux, and macOS.
  • Clarify that the hosts file modification step applies to all platforms, not just Windows.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Resource Manager template ...articles/firewall/quick-create-multiple-ip-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a Windows bias by focusing on RDP connections to Windows Server VMs, referencing Azure PowerShell for further deployment information, and providing only PowerShell commands for resource cleanup. There are no Linux/macOS-specific examples, nor are SSH or Linux VM scenarios mentioned.
Recommendations
  • Include examples for connecting to Linux VMs using SSH, alongside RDP for Windows.
  • Provide equivalent Azure CLI commands for resource cleanup and deployment steps.
  • Reference documentation for deploying Azure Firewall with Linux VM backends.
  • Ensure that Linux/macOS users are guided on how to validate deployments using their native tools.
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-13 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, referencing the Windows file path and omitting equivalent instructions for Linux or macOS systems. This creates friction for non-Windows users attempting to follow the testing steps.
Recommendations
  • Include hosts file modification instructions for Linux (e.g., /etc/hosts) and macOS.
  • Present cross-platform examples side-by-side or note platform differences explicitly.
  • Avoid referencing only Windows paths; use generic language or provide all major OS equivalents.
GitHub Create Pull Request
Firewall Azure Firewall Draft + Deployment (preview) ...azure-docs/blob/main/articles/firewall/draft-deploy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed examples for Azure Portal, Azure CLI, and Azure PowerShell. PowerShell, a Windows-centric tool, is given its own section with extensive example coverage. The CLI section uses Azure CLI, which is cross-platform, but PowerShell is presented as an equal or primary automation method, and no Linux/macOS-specific shell examples (e.g., Bash scripts) are provided. There is no mention of Linux-native tools or patterns, nor any guidance for Linux/macOS users who may not have PowerShell available.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users where automation is discussed.
  • Clarify that Azure CLI is cross-platform and provide guidance for installing and using it on Linux/macOS.
  • If PowerShell is required for certain advanced tasks, mention PowerShell Core (pwsh) and its availability on Linux/macOS.
  • Reorder sections so that cross-platform tools (CLI) are presented before Windows-specific tools (PowerShell).
  • Add a note or table summarizing tool compatibility across Windows, Linux, and macOS.
GitHub Create Pull Request
Firewall IP Groups in Azure Firewall ...cs/azure-docs/blob/main/articles/firewall/ip-groups.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows a moderate Windows bias, primarily through the exclusive mention of Azure PowerShell cmdlets for managing IP Groups and the use of Windows-centric terminology (e.g., 'ellipses', 'left pane') in UI instructions. While Azure CLI and REST API are mentioned as alternatives for creating IP Groups, no CLI or REST examples or references are provided. The PowerShell section is detailed and prominent, while Linux/macOS equivalents (CLI commands, Bash scripts) are missing.
Recommendations
  • Add equivalent Azure CLI commands and examples for all major operations (create, remove, get, set IP Groups, manage rules).
  • Include REST API references or sample payloads for IP Group management.
  • Balance the 'Related Azure PowerShell cmdlets' section with a parallel 'Related Azure CLI commands' section.
  • Clarify UI instructions to avoid Windows-centric terminology (e.g., 'left pane', 'ellipses') or provide screenshots for all platforms.
  • Consider adding Bash scripting examples for automation scenarios.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Resource Manager template ...re-docs/blob/main/articles/firewall/deploy-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively deploying Windows Server virtual machines in the example environment, referencing Windows-specific tools (PowerShell) for resource cleanup, and omitting Linux VM deployment or Linux command-line alternatives. No Linux/macOS-specific instructions or parity are provided.
Recommendations
  • Include options in the ARM template and documentation to deploy Linux VMs (e.g., Ubuntu) alongside or instead of Windows Server VMs.
  • Provide equivalent resource cleanup instructions using Azure CLI (az group delete) for Linux/macOS users.
  • Mention cross-platform management tools and clarify that the template can be customized for different OS types.
  • Present examples for both Windows and Linux environments, or note how users can adapt the template for their preferred OS.
GitHub Create Pull Request
Firewall Tutorial: Deploy and configure Azure Firewall and policy in a hybrid network using the Azure portal ...ain/articles/firewall/tutorial-hybrid-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a notable Windows bias: all virtual machine creation steps use Windows Server images, and the only example for installing IIS uses PowerShell and Windows-specific tooling. There are no instructions or examples for deploying Linux VMs or configuring equivalent Linux services (e.g., Apache/Nginx), nor are there Bash or CLI alternatives to the PowerShell commands. Windows terminology and tools are used exclusively throughout the tutorial, making it less accessible for Linux/macOS users.
Recommendations
  • Provide parallel instructions for deploying Linux VMs (e.g., Ubuntu) in both the spoke and on-premises networks.
  • Include examples for installing and configuring a web server (e.g., Apache or Nginx) on Linux VMs using Bash/CLI.
  • Offer Azure CLI or Bash alternatives for VM extension installation and other configuration steps.
  • Explicitly mention that Linux/macOS users can use the Azure portal and Azure CLI for all steps, and link to relevant documentation.
  • Reorder examples so that Linux and Windows options are presented equally, or at least not always Windows-first.
GitHub Create Pull Request
Firewall Tutorial: Deploy Azure Firewall private IP DNAT for overlapped and nonroutable networks ...lob/main/articles/firewall/tutorial-private-ip-dnat.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits a notable Windows bias, especially in the VM setup and configuration sections. Only Windows virtual machines are referenced, and all configuration instructions use PowerShell scripts executed via RDP or Azure Bastion. There are no Linux VM examples, nor are equivalent Bash or Linux shell commands provided. The tutorial implicitly assumes the use of Windows tools and patterns throughout the configuration and testing steps.
Recommendations
  • Add instructions and scripts for configuring Linux VMs (e.g., Ubuntu) in both scenarios.
  • Provide equivalent Bash scripts or shell commands for Linux VM setup and configuration.
  • Include examples of connecting to Linux VMs using SSH, and demonstrate DNAT rule testing from Linux clients.
  • Present both Windows and Linux examples side-by-side, or clearly indicate platform-specific steps.
  • Reference cross-platform tools (e.g., Azure CLI) for deployment and configuration where possible.
GitHub Create Pull Request
Firewall Deploy Azure Firewall with Availability Zones ...ticles/firewall/deploy-availability-zone-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only Azure PowerShell examples for configuring Azure Firewall with Availability Zones, with no equivalent CLI (az), Bash, or Linux/macOS instructions. The focus on PowerShell and lack of cross-platform examples creates friction for Linux and macOS users.
Recommendations
  • Add Azure CLI (az) examples for all deployment steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, if relevant, and provide installation instructions.
  • Where possible, provide Bash or shell script equivalents for command-line operations.
  • Reorder examples to present CLI and PowerShell side-by-side, or lead with CLI for broader accessibility.
GitHub Create Pull Request
Firewall Deploy and configure Azure Firewall using Azure CLI ...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All virtual machine examples use Windows images (win2016datacenter), and the testing instructions exclusively reference connecting via Remote Desktop and using PowerShell commands. There are no Linux VM deployment examples, nor instructions for SSH access or Linux command-line equivalents for testing firewall rules. Windows tools and workflows (RDP, PowerShell) are mentioned exclusively and before any Linux alternatives, which are absent.
Recommendations
  • Include examples for deploying Linux-based VMs (e.g., Ubuntu) alongside Windows VMs.
  • Provide instructions for connecting to Linux VMs using SSH, and for running equivalent Linux commands (e.g., dig, curl, wget) to test DNS and HTTP connectivity.
  • Add notes or sections clarifying how Linux/macOS users can adapt the procedures, especially in the 'Test the firewall' section.
  • Mention Linux tools and workflows (SSH, Bash, Linux CLI utilities) alongside Windows tools.
  • Consider presenting examples for both platforms in parallel, or at least alternating which platform is shown first.
GitHub Create Pull Request
Firewall Configure customer-controlled maintenance for Azure Firewall ...n/articles/firewall/customer-controlled-maintenance.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. The introduction and main configuration sections focus on the Azure portal and PowerShell, with PowerShell examples and references presented before Azure CLI. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux/macOS users. While Azure CLI examples are provided, they appear after PowerShell and are not referenced in the initial overview, potentially causing friction for non-Windows users.
Recommendations
  • Mention Azure CLI as an equal alternative to PowerShell in the introduction and overview sections.
  • Present Azure CLI examples before or alongside PowerShell examples, not after.
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash or shell script snippets for common tasks, if relevant.
  • Ensure that all steps described for PowerShell have direct CLI equivalents and are clearly documented.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively deploying Windows Server virtual machines in the example Bicep template and mentioning only Windows VMs in the network description. There are no Linux VM examples or references, and the deployment instructions do not address Linux-specific considerations. However, the Azure CLI and PowerShell instructions are both provided, which mitigates some bias in deployment tooling.
Recommendations
  • Include Linux VM deployment examples alongside Windows Server VMs in the Bicep template and documentation narrative.
  • Mention that the Bicep template can be adapted for Linux VMs and provide sample parameters or code snippets for common Linux distributions (e.g., Ubuntu, CentOS).
  • Clarify that adminUsername/adminPassword can be used for both Windows and Linux VMs, and note any differences (e.g., SSH keys for Linux).
  • Add a note or section on how to connect to Linux VMs after deployment, including SSH instructions.
  • Ensure parity in troubleshooting and validation steps for both Windows and Linux environments.
GitHub Create Pull Request
← Previous Page 9 of 14 Next →