Firewall

170
Total Pages
125
Linux-Friendly Pages
45
Pages with Bias
26.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

120 issues found
Showing 76-100 of 120 flagged pages
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates deploying a Windows Server VM and testing DNAT using Remote Desktop Protocol (RDP), which is a Windows-centric workflow. There are no examples or guidance for deploying a Linux VM or testing access using Linux-native tools (e.g., SSH). This creates friction for Linux/macOS users who may want to use SSH or deploy Linux workloads.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Provide examples for configuring DNAT rules for SSH (port 22) in addition to RDP (port 3389).
  • Add testing steps for Linux/macOS users, such as connecting via SSH from a local terminal.
  • Clarify that the firewall DNAT configuration supports both Windows and Linux workloads, and mention relevant ports/protocols for each.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is strongly Windows-centric in its VM setup and configuration sections. Only Windows VMs are referenced, and all configuration scripts are provided as PowerShell (.ps1) files with instructions to run them in PowerShell as Administrator. There are no examples, scripts, or guidance for Linux VMs, nor any mention of Linux-compatible alternatives. The documentation assumes users are working with Windows environments, which may create friction or barriers for Linux/macOS users.
Recommendations
  • Provide equivalent setup instructions and scripts for Linux VMs (e.g., Bash scripts, cloud-init, or manual steps).
  • Explicitly mention Linux VM support and provide guidance for configuring DNAT scenarios using Linux tools.
  • Include cross-platform testing instructions (e.g., using curl, netcat, or ssh for connectivity tests).
  • Present both Windows and Linux examples side-by-side, or at least note differences in steps for each OS.
  • Reference Linux troubleshooting and monitoring tools 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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial consistently uses Windows-centric examples and instructions, such as deploying Windows Server VMs, using RDP, and providing only PowerShell commands for VM configuration. There are no Linux VM deployment steps, no Bash/Azure CLI examples, and no mention of SSH or Linux tools. This creates friction for Linux/macOS users and implies a Windows-first approach.
Recommendations
  • Include parallel instructions for deploying Linux VMs (e.g., Ubuntu) and configuring them for testing (such as installing Apache/Nginx).
  • Provide Azure CLI and Bash examples alongside PowerShell commands, especially for VM extension installation and configuration.
  • Mention SSH as an alternative to RDP for Linux VMs, and show how to test connectivity using Linux tools (curl, ssh, etc.).
  • Clarify that the tutorial is applicable to both Windows and Linux environments, and link to Linux-focused documentation where appropriate.
  • When listing VM images, show both Windows and Linux options, or make the OS selection explicit and flexible.
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-11 06:20
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 images, and all configuration steps involving VM extensions and IIS installation use PowerShell commands. There are no Linux VM examples, nor are there instructions for deploying or configuring Linux workloads or using Bash/CLI equivalents. Windows tools and patterns (RDP, PowerShell, IIS) are mentioned exclusively, with no parity for Linux users.
Recommendations
  • Include examples for creating Linux virtual machines (e.g., Ubuntu) in both the spoke and on-premises networks.
  • Provide instructions for installing and configuring a web server on Linux (e.g., Apache or Nginx) using Azure CLI or Bash commands.
  • Show how to connect to Linux VMs using SSH, and how to test connectivity (e.g., using curl or browser).
  • Offer PowerShell and Bash/CLI equivalents side-by-side for all VM extension and configuration steps.
  • Mention Linux-compatible remote access methods and tools, not just RDP.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed examples for Azure Portal, Azure CLI, and Azure PowerShell. While the CLI section uses az commands (which are cross-platform), the PowerShell section is extensive and assumes the user has access to PowerShell, a tool primarily associated with Windows. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there any Bash or shell script examples. Additionally, PowerShell is given a dedicated tab and full example set, which may suggest a Windows-centric approach. The CLI examples are cross-platform but do not explicitly mention Linux/macOS compatibility or provide shell-specific guidance. The documentation does not mention or prioritize Linux tools or patterns.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users alongside PowerShell.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary environment setup instructions for those platforms.
  • Mention cross-platform compatibility in the prerequisites and CLI sections.
  • Avoid implying PowerShell is required for non-Windows users; suggest alternatives where appropriate.
GitHub Create Pull Request
Firewall Azure Firewall preview features ...e-docs/blob/main/articles/firewall/firewall-preview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure PowerShell as a configuration method for certain features (e.g., redeploying a firewall in a secured hub), but does not mention or provide equivalent instructions for Linux/macOS users (such as Azure CLI or Bash). There are no explicit examples or instructions for Linux tools or platforms, and PowerShell is referenced as a primary method, which may create friction for non-Windows users.
Recommendations
  • Include Azure CLI examples alongside PowerShell instructions for all configuration steps.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for all supported operations.
  • Add links or references to cross-platform tools and documentation where appropriate.
  • Ensure that any portal-based instructions are clearly marked as platform-agnostic.
GitHub Create Pull Request
Firewall Azure Firewall Management NIC ...ure-docs/blob/main/articles/firewall/management-nic.md
Medium Priority View Details →
Scanned: 2026-01-10 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 critical firewall management operations (stop/start, allocate IPs), with no equivalent Azure CLI or REST API instructions. PowerShell is most commonly used on Windows, and Linux/macOS users are likely to use Azure CLI or REST API. The lack of cross-platform examples creates friction for non-Windows users and may prevent them from completing tasks efficiently.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, especially for stopping/starting the firewall and assigning public IPs.
  • Mention REST API alternatives for automation and scripting on any platform.
  • Explicitly state that all operations can be performed via Azure CLI, REST API, or portal, and link to relevant documentation.
  • Where possible, show CLI examples before or alongside PowerShell to signal cross-platform parity.
GitHub Create Pull Request
Firewall Azure Firewall prescaling ...s/azure-docs/blob/main/articles/firewall/prescaling.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell example for configuring Azure Firewall prescaling, but omits equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is a Windows-centric tool, and its example is given before any cross-platform alternatives. No Linux-native tools or commands are mentioned, and the configuration section does not offer parity for non-Windows environments.
Recommendations
  • Add Azure CLI examples for configuring prescaling, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available on Linux/macOS, or provide Bash script examples.
  • Ensure that ARM template and Bicep examples are accompanied by CLI deployment instructions suitable for Linux/macOS users.
  • Present cross-platform examples (Azure CLI, Bash) before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall and IP Groups - Resource Manager template ...ain/articles/firewall/quick-create-ipgroup-template.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for resource cleanup and references the Remove-AzResourceGroup cmdlet, which is a Windows/PowerShell-centric tool. There are no equivalent CLI or Bash examples for Linux/macOS users. The deployment instructions rely on the Azure Portal, which is cross-platform, but command-line automation is only shown for Windows/PowerShell environments.
Recommendations
  • Add equivalent Azure CLI (az group delete) and Bash examples for resource group deletion.
  • Where PowerShell cmdlets are shown, also provide cross-platform alternatives (Azure CLI, Bash, etc.).
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide links to relevant documentation.
  • Review other sections for implicit Windows-centric language or assumptions.
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-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 focusing exclusively on connecting to Windows Server VMs via RDP, without mentioning Linux VM scenarios or SSH access. The validation step assumes Remote Desktop Connection, a Windows-centric tool, and does not provide Linux/macOS alternatives. While deployment instructions include both Azure CLI and PowerShell, the example workloads and connection methods are Windows-only.
Recommendations
  • Include examples for deploying and connecting to Linux VMs, such as using SSH.
  • Mention cross-platform remote access tools (e.g., SSH for Linux/macOS, RDP for Windows).
  • In the 'Validate the deployment' section, provide instructions for connecting from Linux/macOS clients.
  • Clarify that the firewall can be used for both Windows and Linux VM scenarios.
  • Add cleanup instructions using Azure CLI, not just PowerShell.
GitHub Create Pull Request
Firewall Deploy and configure Azure Firewall Premium ...ure-docs/blob/main/articles/firewall/premium-deploy.md
Medium Priority View Details →
Scanned: 2026-01-10 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 exclusively referencing a Windows test virtual machine (WorkerVM) for all testing steps, including browser and command-line usage. All examples and instructions (e.g., opening an administrator command prompt, deploying certificates, browsing to test URLs) assume a Windows environment, with no mention of Linux or macOS alternatives for VM deployment, certificate installation, or testing procedures. There are no Linux/macOS-specific instructions or examples provided.
Recommendations
  • Include instructions for deploying and configuring a Linux test VM alongside the Windows VM.
  • Provide Linux/macOS equivalents for certificate installation and curl usage.
  • Add browser testing steps for Linux/macOS environments.
  • Clarify that the testing steps can be performed on non-Windows platforms and provide any necessary platform-specific guidance.
  • Ensure that references to 'WorkerVM' are not exclusively tied to Windows, or explicitly mention support for other OS types.
GitHub Create Pull Request
Firewall Use Azure Firewall to protect Azure Virtual Desktop ...ain/articles/firewall/protect-azure-virtual-desktop.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses on Azure Virtual Desktop, which is inherently Windows-centric, but it further reinforces Windows bias by referencing Windows-specific service tags, tools, and examples (such as Microsoft Edge proxy configuration). There are no Linux/macOS-specific instructions, examples, or tool references, and Windows terminology and endpoints are mentioned exclusively or first throughout the page.
Recommendations
  • Include examples or guidance for configuring Azure Firewall for Linux/macOS session hosts, if supported.
  • Mention whether Linux/macOS clients or session hosts are supported and provide relevant documentation links.
  • Provide proxy configuration examples for browsers commonly used on Linux/macOS (e.g., Firefox, Chrome) in addition to Microsoft Edge.
  • Clarify whether the 'WindowsVirtualDesktop' service tag applies to non-Windows session hosts, or provide equivalent tags/instructions for Linux/macOS.
  • Add a note about cross-platform compatibility and any limitations for non-Windows environments.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is notably Windows-centric: it only references RDP to Windows Server VMs, links to PowerShell deployment guides, and provides a PowerShell-only example for resource cleanup. There are no Linux/macOS-specific instructions, examples, or SSH-based scenarios, which may hinder non-Windows users.
Recommendations
  • Include examples for connecting to Linux VMs via SSH, not just RDP to Windows Server.
  • Provide equivalent Azure CLI or Bash commands for resource cleanup alongside PowerShell.
  • Reference documentation for deploying Azure Firewall using Linux/macOS tools (e.g., Azure CLI, Bash scripts).
  • Clarify that the template can deploy Linux VMs and provide sample parameters for such deployments.
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 is notably Windows-centric: it only demonstrates deploying Windows Server VMs and configuring RDP access, with no mention of Linux VM deployment or SSH access. The referenced PowerShell article is highlighted before any Linux/CLI alternatives, and all VM examples are Windows-only. There are no Linux VM or SSH rule examples, which may hinder Linux/macOS users seeking parity.
Recommendations
  • Add examples for deploying Linux VMs (e.g., using azurerm_linux_virtual_machine).
  • Include NAT rule examples for SSH access to Linux VMs alongside RDP for Windows.
  • Reference equivalent Linux-focused documentation (e.g., CLI or Bash guides) alongside PowerShell articles.
  • Clarify that the process is similar for Linux VMs and provide links or code samples.
  • Ensure troubleshooting and verification steps mention Linux scenarios where relevant.
GitHub Create Pull Request
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-10 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 primarily through Azure PowerShell examples, which are Windows-centric. There are no CLI (az), Bash, or Linux/macOS-specific instructions. The PowerShell approach is presented as the main automation method, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer using the Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all configuration steps, including creating, associating, and reconfiguring public IP addresses with Azure Firewall.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Reorder or parallelize examples so that CLI and PowerShell instructions are presented side-by-side or with equal prominence.
  • Clarify any platform-specific requirements for PowerShell, and suggest alternatives for non-Windows users.
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 extensive Azure PowerShell examples, which are typically used on Windows, and presents PowerShell instructions before Azure CLI equivalents. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are there any references to Linux-native tools or considerations. While Azure CLI is cross-platform, the emphasis and ordering favor Windows/PowerShell users.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands to demonstrate usage on Linux/macOS.
  • Clarify that Azure CLI commands work on all platforms and provide platform-specific notes where relevant.
  • Consider including screenshots or step-by-step instructions for Linux/macOS users in portal sections.
  • Ensure parity in troubleshooting and deployment notes for non-Windows environments.
  • If PowerShell is required, mention PowerShell Core compatibility on Linux/macOS.
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 the deployment and testing of Azure Firewall using a Windows Server 2019 virtual machine. All instructions for creating and accessing the test workload VM are Windows-centric, with no mention of Linux or macOS alternatives. The remote desktop testing step assumes RDP and Windows tools, and there are no examples or guidance for Linux VM creation, SSH access, or browser testing from non-Windows platforms.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including steps for SSH access and browser installation.
  • Include testing steps for Linux users, such as using SSH to connect to the VM and using Firefox/Chrome to verify firewall rules.
  • Mention that the firewall and policy configuration applies equally to Linux workloads, and provide guidance for Linux/macOS users where steps differ (e.g., remote access methods).
  • Present both Windows and Linux VM creation options side-by-side to improve parity.
  • Clarify that the tutorial is not limited to Windows workloads and that Azure Firewall supports any OS.
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 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 examples or instructions for deploying a Linux VM, nor for connecting to a Linux workload (e.g., via SSH). This creates friction for users who wish to follow the tutorial with Linux or macOS workloads.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide examples for configuring DNAT rules for SSH (port 22) access to a Linux VM.
  • Add testing steps for connecting to a Linux VM using SSH from Linux/macOS clients.
  • Present both Windows and Linux examples in parallel, or alternate which is shown first.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for deploying Azure Firewall DNAT, but when creating the test workload virtual machine, it exclusively uses Windows Server 2019 Datacenter as the example OS. The only connectivity test described is via Remote Desktop Protocol (RDP), which is Windows-specific. There are no examples or guidance for deploying a Linux VM, nor for testing connectivity using SSH or other Linux-friendly methods.
Recommendations
  • Include parallel instructions for creating a Linux-based virtual machine (e.g., Ubuntu Server) in the 'Create a virtual machine' section.
  • Provide examples for testing connectivity to the Linux VM using SSH (port 22), including how to configure the DNAT rule for SSH.
  • When describing the test step, mention both RDP (for Windows) and SSH (for Linux) as valid methods, and provide sample commands for each.
  • Consider alternating or randomizing the order of OS examples, or presenting both side-by-side, to avoid implicit prioritization of Windows.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only Azure PowerShell examples for configuring Azure Firewall service tags, with no equivalent Azure CLI or portal instructions. PowerShell is primarily a Windows tool, and its exclusive use here creates friction for Linux/macOS users. The mention of Azure CLI and portal as supported options is not followed by any examples or guidance, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Provide step-by-step instructions or screenshots for configuring service tags via the Azure portal.
  • Consider listing CLI and portal methods before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly state that PowerShell Core is available cross-platform, if relevant, or clarify any limitations.
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 explicitly for Windows, referencing the Windows file path and omitting equivalent instructions for Linux or macOS. No Linux/macOS hosts file location or syntax is mentioned, and the example is Windows-centric.
Recommendations
  • Include hosts file modification instructions for Linux (e.g., /etc/hosts) and macOS.
  • Provide example commands for editing the hosts file on Linux/macOS (e.g., using sudo nano /etc/hosts).
  • Present cross-platform instructions together or in parallel, not just Windows-first.
  • Clarify that the procedure applies to all OSes and specify differences where relevant.
GitHub Create Pull Request
Firewall Azure Firewall known issues and limitations ...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation is generally platform-neutral, focusing on Azure Firewall service issues and limitations. However, there is a minor instance of Windows bias: in the mitigation for FTP server configuration issues, the documentation links to an IIS (Windows-only) example, without providing a Linux equivalent or mentioning cross-platform alternatives.
Recommendations
  • Add links or examples for configuring FTP servers on popular Linux platforms (e.g., vsftpd, ProFTPD, Pure-FTPd) alongside the IIS example.
  • Explicitly state that the FTP configuration guidance applies to both Windows and Linux servers, and provide parity in troubleshooting steps.
  • Where platform-specific examples are given, ensure Linux/macOS equivalents are referenced or linked.
GitHub Create Pull Request
Firewall Azure Firewall known issues and limitations ...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation for Azure Firewall known issues and limitations is largely platform-neutral, focusing on Azure service behaviors and limitations. However, there is a minor instance of Windows bias: in the mitigation for Passive FTP issues, the documentation links to an IIS-specific (Windows-only) configuration example, without mentioning Linux FTP server equivalents. No PowerShell-heavy, Windows-first, or missing Linux example biases are present, and the page does not assume Windows usage elsewhere.
Recommendations
  • When referencing FTP server configuration for Passive FTP, provide equivalent guidance or links for popular Linux FTP servers (e.g., vsftpd, ProFTPD, Pure-FTPd) alongside the IIS example.
  • Clarify that the IIS link is for Windows users, and suggest Linux alternatives for cross-platform parity.
  • Review other mitigation steps to ensure that any tool or command references are not Windows-exclusive, or that Linux/macOS equivalents are provided where relevant.
GitHub Create Pull Request
Firewall Azure Firewall known issues and limitations ...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation is generally platform-neutral, but there are a few instances where Windows-centric tools (PowerShell) are referenced as the primary or only method for certain operations, such as updating Azure Firewall Policy tags. There are no Linux/macOS-specific examples or CLI parity recommendations in these cases.
Recommendations
  • Where PowerShell is referenced as the only workaround (e.g., updating tags), add equivalent Azure CLI commands and examples, which are cross-platform.
  • Explicitly mention REST API or ARM template alternatives when PowerShell is not available or supported.
  • Ensure that mitigation steps and workarounds do not assume the user is on Windows; provide CLI and portal instructions where possible.
  • Review all tool references and ensure parity between PowerShell and Azure CLI in documentation examples.
GitHub Create Pull Request
Firewall Scale SNAT ports with Azure NAT Gateway ...b/main/articles/firewall/integrate-with-nat-gateway.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step examples for associating a NAT gateway with an Azure Firewall subnet using both Azure PowerShell and Azure CLI. However, the PowerShell example is presented first, which may suggest a Windows-centric approach. PowerShell is traditionally associated with Windows environments, although it is now cross-platform. There are no explicit Linux/macOS-only tools or examples (e.g., Bash scripts), but the ordering and emphasis may subtly favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is natively available on Linux/macOS and is more platform-agnostic.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and provide guidance for installation on Linux/macOS.
  • Include a Bash script example or note for Linux users, especially for automation scenarios.
  • Clarify that the steps are identical across platforms, and highlight any platform-specific considerations if they exist.
GitHub Create Pull Request
← Previous Page 4 of 5 Next →