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 51-75 of 332 flagged pages
Firewall Access a storage account using SFTP over an Azure Firewall static public IP address ...zure-docs/blob/main/articles/firewall/firewall-sftp.md
High 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 is heavily focused on Azure PowerShell for all deployment and configuration steps, with no mention of Azure CLI, Bash, or Linux-native tools. All code samples use PowerShell syntax, and setup instructions assume a Windows/PowerShell environment. There are no Linux-specific instructions or examples for deploying resources, nor is there guidance for using Azure CLI. The only cross-platform mention is the use of the generic 'sftp' client, but even here, the example is described as being run from a 'command prompt', which may imply Windows.
Recommendations
  • Add equivalent Azure CLI (az) examples for all deployment and configuration steps, alongside PowerShell.
  • Explicitly mention that both Windows and Linux users can follow the guide, and clarify how Linux users can install and use Azure CLI.
  • Provide Bash shell examples for variable setup and resource management.
  • Include instructions for running sftp from both Windows and Linux terminals, and clarify any platform-specific differences.
  • Review and update language to avoid implying Windows as the default environment (e.g., replace 'command prompt' with 'terminal').
GitHub Create Pull Request
Firewall Azure Firewall FTP support .../azure-docs/blob/main/articles/firewall/ftp-support.md
High 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 page demonstrates a Windows bias by providing detailed instructions and examples for Azure PowerShell (a Windows-centric tool) first, including code snippets, while Linux-native tools and workflows are not explicitly addressed. Although Azure CLI is mentioned, no example commands are provided, and there is no discussion of Linux-specific considerations or parity. There are no references to Linux shell scripting, nor are there examples using Bash or other Linux-native tools.
Recommendations
  • Provide explicit Azure CLI command examples, including full syntax and sample usage, to match the detail given for PowerShell.
  • Include Bash shell scripting examples for updating and deploying Azure Firewall configurations, demonstrating Linux-native workflows.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide guidance for Linux users where relevant.
  • Ensure that documentation sections for deployment and configuration do not prioritize PowerShell over CLI or ARM templates; consider presenting CLI examples before or alongside PowerShell.
  • Add troubleshooting or configuration notes relevant to Linux environments, such as differences in shell behavior or authentication methods.
GitHub Create Pull Request
Firewall Azure Firewall preview features ...e-docs/blob/main/articles/firewall/firewall-preview.md
High 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 page demonstrates Windows bias by referencing Azure PowerShell as a configuration method for firewall deployments, without mentioning equivalent Linux-friendly tools (such as Azure CLI or ARM templates). There are no Linux-specific examples or instructions, and Windows-centric tools are mentioned before any cross-platform alternatives.
Recommendations
  • Include Azure CLI examples alongside or before Azure PowerShell instructions for configuration tasks.
  • Explicitly mention that all features can be managed from Linux/macOS using Azure CLI, ARM templates, or REST API.
  • Provide step-by-step instructions or code snippets for Linux users, ensuring parity with Windows/PowerShell examples.
  • Review all procedural content to ensure cross-platform tools are referenced equally and not subordinate to Windows-centric tools.
GitHub Create Pull Request
Firewall Azure Firewall Management NIC ...ure-docs/blob/main/articles/firewall/management-nic.md
High 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 page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for firewall management operations (stop/start, IP assignment), without any equivalent Azure CLI (cross-platform) or Bash examples. The use of PowerShell commands and cmdlets assumes a Windows environment or familiarity with Windows tooling, and there is no mention of Linux-native workflows or tools. This may hinder Linux users or those working in cross-platform environments from easily following the instructions.
Recommendations
  • Add Azure CLI (az) command examples for all PowerShell steps, including stopping/starting the firewall and assigning IP addresses.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
  • Include Bash script examples or instructions for Linux users where appropriate.
  • Clarify that the Azure portal and REST API are also cross-platform options for these operations.
  • Ensure screenshots and instructions do not assume a Windows-only environment.
GitHub Create Pull Request
Firewall Azure Firewall IDPS signature rule categories ...ob/main/articles/firewall/idps-signature-categories.md
High 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 demonstrates a mild Windows bias. Several categories (ActiveX, Exploit, Web Server) mention Microsoft-specific technologies (ActiveX, Windows, IIS) before or alongside other platforms. Windows technologies are referenced explicitly, while Linux equivalents (such as Linux-specific exploits, Apache, NGINX) are mentioned but not given equal prominence or detail. There are no code examples, but the pattern of mentioning Windows technologies first or exclusively is present. No PowerShell or Windows-only command-line examples are given, but the overall framing leans toward Windows-centric terminology and threat models.
Recommendations
  • Ensure equal prominence for Linux and open-source technologies when listing examples (e.g., mention Apache, NGINX, Tomcat before or alongside IIS).
  • Provide more detail on non-Windows exploits and threat categories, including references to Linux, macOS, and open-source software vulnerabilities.
  • Avoid listing Microsoft technologies first unless contextually justified; alternate ordering or group by platform.
  • Add explicit examples or references for Linux-specific threats and detection logic where relevant.
  • Review category descriptions to ensure they do not implicitly prioritize Windows environments over cross-platform scenarios.
GitHub Create Pull Request
Firewall Monitor Azure Firewall ...e-docs/blob/main/articles/firewall/monitor-firewall.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: it references Windows-centric tools (Excel, Power BI, Visual Studio, C#), provides instructions specifically for Azure PowerShell without mentioning CLI or Linux alternatives, and omits Linux-specific or cross-platform examples for log conversion and configuration. Windows tools and workflows are mentioned before or instead of Linux equivalents, and there are no Bash, Azure CLI, or open-source tool examples for common tasks.
Recommendations
  • Add Azure CLI examples for configuring diagnostic settings and enabling features, alongside PowerShell instructions.
  • Include references to open-source or cross-platform log conversion tools (e.g., jq, csvkit, Python scripts) for processing JSON logs.
  • Mention Linux-compatible visualization tools (e.g., Grafana) in addition to Excel and Power BI.
  • Provide sample scripts or commands for Linux environments (Bash, shell, etc.) for downloading, converting, and analyzing logs.
  • Reference editors and development environments available on Linux (e.g., VS Code, JetBrains IDEs) when discussing log converter tools.
  • Ensure that any tool or workflow described is either cross-platform or that Linux/macOS alternatives are clearly documented.
GitHub Create Pull Request
Firewall Deploy and configure Enterprise CA certificates for Azure Firewall Premium .../firewall/premium-deploy-certificates-enterprise-ca.md
High 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 is heavily oriented towards Windows environments, with exclusive references to Windows tools (certtmpl.msc, Internet Explorer, Internet Options), Active Directory, and Windows Server workflows. There are no examples or guidance for Linux-based certificate management, nor are cross-platform alternatives mentioned. The prerequisites and steps assume a Windows-centric enterprise PKI and omit Linux equivalents.
Recommendations
  • Add instructions for generating and managing CA certificates using Linux-based tools (e.g., OpenSSL, certtool, or Dogtag).
  • Include examples for certificate requests and exports using Linux command-line utilities.
  • Mention cross-platform alternatives to Active Directory Certification Services, such as FreeIPA or OpenLDAP.
  • Provide guidance for accessing and exporting certificates via Linux browsers or command-line, not just Internet Explorer.
  • Reorder sections or add parallel workflows so Linux and Windows approaches are presented with equal prominence.
GitHub Create Pull Request
Firewall Use Azure Firewall to protect Azure Virtual Desktop ...ain/articles/firewall/protect-azure-virtual-desktop.md
High 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 Windows-based virtual desktops, using Windows-specific service tags (e.g., WindowsVirtualDesktop), and providing examples and links that focus on Windows tools (such as Microsoft Edge proxy configuration). There are no examples or guidance for Linux-based Azure Virtual Desktop session hosts, nor are Linux tools or patterns mentioned for proxy configuration or outbound access.
Recommendations
  • Include explicit guidance and examples for Linux-based Azure Virtual Desktop session hosts, such as required FQDNs, firewall rules, and configuration steps.
  • Add Linux equivalents for proxy configuration (e.g., how to configure proxy settings in Firefox or Chrome on Linux, or using environment variables).
  • Reference Linux-specific documentation and tools where appropriate, such as iptables, nftables, or Linux-based DNS configurations.
  • Clarify whether the Azure Firewall configuration applies equally to Linux session hosts, and note any differences.
  • Provide sample scripts or templates for both Windows and Linux environments when automating firewall policy deployment.
GitHub Create Pull Request
Firewall Monitoring data reference for Azure Firewall ...b/main/articles/firewall/monitor-firewall-reference.md
High Priority View Details →
Scanned: 2026-01-10 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 for Azure Firewall monitoring data is heavily biased towards Windows environments. All command-line examples use Azure PowerShell, which is most commonly used on Windows and lacks parity with Bash/CLI or Linux-native tools. There are no examples using Azure CLI, Bash, or Linux shell scripting, nor are there instructions for enabling features via REST API, ARM templates, or portal-only workflows. The documentation assumes PowerShell as the primary automation tool, which may alienate Linux users or those using cross-platform automation.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for all PowerShell commands, ensuring Linux and macOS users can follow along without installing PowerShell.
  • Include Bash script snippets or instructions for using the Azure CLI in shell environments.
  • Mention both PowerShell and CLI options side-by-side, or indicate which commands are cross-platform.
  • Clarify that PowerShell commands can be run on Linux/macOS, but highlight CLI alternatives for native Linux workflows.
  • For feature enablement, provide REST API or ARM template examples where possible, as these are platform-neutral.
  • Review the order of presentation so that CLI or platform-neutral methods are not always listed after PowerShell, or only as an afterthought.
GitHub Create Pull Request
Firewall Deploy and configure Azure Firewall Premium ...ure-docs/blob/main/articles/firewall/premium-deploy.md
High 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 Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM) for all deployment and testing steps. All instructions for testing (e.g., using curl, opening browsers) are given in the context of Windows, with no mention of Linux equivalents or guidance for deploying/testing on Linux VMs. The process for installing certificates is described only for Windows, and connection instructions reference Azure Bastion for accessing a Windows VM. There are no Linux-specific examples, tools, or parity in deployment or testing steps.
Recommendations
  • Provide parallel instructions for deploying and configuring a Linux-based WorkerVM, including certificate installation steps for common Linux distributions.
  • Include Linux-specific examples for testing (e.g., using curl from a Linux terminal, opening browsers such as Firefox or Chrome on Linux).
  • Mention how to connect to Linux VMs (e.g., via SSH) in addition to Azure Bastion for Windows.
  • Clarify any differences in certificate handling or firewall testing between Windows and Linux environments.
  • Ensure that all steps (deployment, testing, diagnostics) are covered for both Windows and Linux platforms to improve parity and inclusivity.
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
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias by focusing exclusively on Windows Server VMs as deployment targets, referencing RDP (a Windows-specific protocol), and providing only PowerShell-based cleanup instructions. There are no examples or guidance for Linux VMs, SSH access, or use of cross-platform tools such as Azure CLI. The documentation also references a PowerShell-specific guide for further reading.
Recommendations
  • Include examples and instructions for deploying and connecting to Linux virtual machines, such as using SSH instead of RDP.
  • Provide cleanup instructions using Azure CLI (az group delete) alongside PowerShell to support cross-platform users.
  • Reference documentation for deploying Azure Firewall with multiple public IPs using Azure CLI or ARM templates directly, not just PowerShell.
  • Clarify that the template can be used for both Windows and Linux VMs, or provide separate templates/examples for each.
  • When mentioning remote connection, include both RDP (for Windows) and SSH (for Linux) scenarios.
GitHub Create Pull Request
Firewall Overview of Azure Firewall service tags ...azure-docs/blob/main/articles/firewall/service-tags.md
High 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 demonstrates a Windows bias by providing only Azure PowerShell examples for configuring Azure Firewall service tags. While it mentions Azure CLI and the Azure portal as configuration options, no CLI or portal examples are given. The use of PowerShell commands and variables is specific to Windows environments, and there is no guidance for Linux users or cross-platform command-line usage.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, using bash syntax and Linux-friendly patterns.
  • Provide guidance or screenshots for configuring service tags via the Azure portal.
  • Explicitly mention cross-platform compatibility and clarify which tools are available on Linux and macOS.
  • Ensure that examples are presented in parallel (e.g., PowerShell and CLI side-by-side) or alternate the order to avoid Windows-first bias.
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
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by focusing on RDP connections to Windows Server VMs, referencing Azure PowerShell before Linux alternatives, and providing PowerShell-specific cleanup instructions. There are no Linux VM examples, nor are SSH or Linux-native tools/patterns mentioned for deployment or validation. The quickstart assumes Windows-centric workflows and tools.
Recommendations
  • Include examples for deploying Linux VMs alongside Windows VMs, and demonstrate firewall NAT rules for SSH connections.
  • Provide cleanup instructions using Azure CLI in addition to PowerShell, and present both options equally.
  • Mention Linux-native tools (e.g., SSH) for validation steps, not just Remote Desktop Connection.
  • Reference documentation for deploying Azure Firewall with multiple public IP addresses using Azure CLI and Linux workflows.
  • Ensure examples and instructions are presented in parallel for both Windows and Linux users, avoiding Windows-first ordering.
GitHub Create Pull Request
Firewall Customer provided public IP address support in secured hubs ...in/articles/firewall/secured-hub-customer-public-ip.md
High 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 demonstrates a Windows bias by providing only Azure PowerShell examples for command-line configuration, with no equivalent instructions for Linux users (e.g., Azure CLI or Bash). The PowerShell examples are given as the sole scripting option, and there is no mention of Linux-native tools or cross-platform alternatives. The portal instructions are platform-neutral, but all automation and scripting guidance is Windows-centric.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration steps, ensuring Linux users have clear, supported instructions.
  • Explicitly mention that both PowerShell and Azure CLI are supported, and provide links to relevant CLI documentation.
  • Where possible, include Bash script snippets or cross-platform automation guidance.
  • Clarify that the Azure portal is accessible from any OS, and highlight parity in management capabilities.
  • Review terminology to avoid implying PowerShell is the default or preferred method; present options equally.
GitHub Create Pull Request
Firewall Configure Azure Firewall application rules with SQL FQDNs ...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
High 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 configuration instructions using Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the PowerShell section is Windows-centric and detailed, and there are no explicit Linux shell (bash) examples or references to Linux-specific tools or patterns. The order of presentation places PowerShell immediately after CLI, and the portal instructions reference CLI deployment, but there is no mention of Linux environments or shell scripting alternatives.
Recommendations
  • Add explicit bash shell examples for Azure CLI usage, demonstrating commands in a Linux environment.
  • Clarify that Azure CLI is cross-platform and provide guidance for both Windows (CMD/PowerShell) and Linux/macOS (bash/zsh) users.
  • Include notes or examples for deploying and validating from Linux-based VMs, not just generic 'virtual machines'.
  • If PowerShell is mentioned, also mention bash or other Linux-native scripting options for parity.
  • Ensure that references to deployment steps do not assume Windows tools or environments unless necessary.
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
High Priority View Details →
Scanned: 2026-01-10 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 exhibits a Windows bias in several ways: all virtual machine creation examples use Windows Server images, and installation/configuration steps (such as IIS setup) are provided only for Windows using PowerShell. There are no equivalent Linux VM examples, nor instructions for deploying or configuring Linux workloads (e.g., Apache on Ubuntu). The only scripting example uses PowerShell, and Azure Cloud Shell is explicitly set to PowerShell, with no Bash or CLI alternatives. The documentation does not mention Linux tools or patterns, and Windows-centric terminology (RDP, Windows Server) is used throughout.
Recommendations
  • Include parallel instructions for deploying a Linux-based workload VM (e.g., Ubuntu Server), including steps for installing a web server such as Apache or Nginx.
  • Provide Azure CLI and/or Bash examples alongside PowerShell for VM extension installation and other automation steps.
  • Mention SSH as a remote access method for Linux VMs, and provide examples for connecting via SSH.
  • When describing firewall rules, include examples for Linux-based protocols and ports (e.g., SSH port 22).
  • Use more neutral terminology when referring to remote access (e.g., 'remote desktop or SSH'), and avoid assuming Windows-only scenarios.
  • Add notes or links to Linux-specific documentation for users who prefer or require Linux workloads.
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
High 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 demonstrates a Windows bias by exclusively using Windows Server as the example workload VM and guiding users to test DNAT using Remote Desktop (RDP), which is a Windows-centric protocol. There are no Linux VM deployment instructions, nor are SSH or Linux-based connectivity tests mentioned. The documentation does not provide parity for Linux users, omitting Linux-specific guidance and examples.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet alongside or instead of Windows Server.
  • Provide example NAT rules for SSH (port 22) in addition to RDP (port 3389).
  • Add testing steps for Linux users, such as connecting via SSH to the firewall's public IP address.
  • Mention Linux tools and commands (e.g., ssh, scp) when describing connectivity and testing.
  • Ensure that both Windows and Linux examples are presented in parallel throughout the documentation.
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
High Priority View Details →
Scanned: 2026-01-10 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 clear Windows bias throughout. All virtual machine creation steps use Windows Server images exclusively, with no mention of Linux alternatives. The IIS installation is performed using PowerShell, and the only provided automation example is a PowerShell script. There are no Linux VM examples, nor are there instructions for deploying a Linux-based web server or using Bash/CLI for configuration. Windows-centric tools and patterns (RDP, PowerShell, Windows Server) are used and referenced first and exclusively.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) in both the spoke and on-premises networks.
  • Provide examples for installing a web server (e.g., Apache or Nginx) on Linux VMs, using Bash or Azure CLI.
  • Include Linux-based connection methods (e.g., SSH) alongside RDP for remote access testing.
  • Offer equivalent Azure CLI or Bash scripts for VM extension installation and configuration, not just PowerShell.
  • Explicitly mention that the tutorial works with both Windows and Linux workloads, and provide guidance for both.
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
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a strong Windows bias, particularly in the VM configuration and testing sections. All example scripts and instructions use PowerShell and reference Windows VMs (e.g., 'win-vm-2', 'win-vm-3'), with no mention of Linux VMs or equivalent Bash/SSH commands. The guidance for configuring and testing the environment is exclusively Windows-centric, and Windows tools (PowerShell, RDP) are referenced without Linux alternatives. This limits accessibility for users deploying Linux-based environments or preferring cross-platform solutions.
Recommendations
  • Provide equivalent Linux VM setup instructions, including Bash scripts and SSH usage.
  • Include examples for configuring and testing DNAT functionality from Linux clients (e.g., using curl, netcat, or ssh).
  • Reference both Windows and Linux VM images in deployment steps, or clarify how to adapt the ARM template for Linux.
  • Offer troubleshooting and monitoring guidance for Linux environments (e.g., using syslog, journalctl, or Linux firewall logs).
  • Ensure parity in documentation by presenting Windows and Linux examples side-by-side where possible.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-template.md ...re-docs/blob/main/articles/firewall/deploy-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively deploying Windows Server virtual machines in the example template, mentioning Windows VMs as the only option for the jump box and server. There are no references to Linux VM deployment, nor are Linux-specific cleanup instructions (such as Azure CLI or Bash) provided. The cleanup section only provides a PowerShell command, with no Linux or cross-platform alternatives.
Recommendations
  • Include examples and instructions for deploying Linux virtual machines alongside or instead of Windows Server VMs in the ARM template.
  • Provide cleanup instructions using Azure CLI (az group delete) and Bash, in addition to PowerShell, to ensure cross-platform parity.
  • Mention both Windows and Linux options when describing the jump box and server VM roles.
  • Add notes or links to documentation for Linux VM configuration and management in Azure.
  • Review and update template parameters to allow users to select the OS type (Windows or Linux) for the deployed VMs.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-template.md ...ain/articles/firewall/quick-create-ipgroup-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias towards Windows by providing only a PowerShell example for resource cleanup (`Remove-AzResourceGroup`) and omitting equivalent Linux/CLI commands. The use of Azure PowerShell is a Windows-centric pattern, and there are no Bash, Azure CLI, or cross-platform instructions for deleting resources. No Linux shell or cross-platform examples are given for resource management tasks.
Recommendations
  • Include Azure CLI (az group delete) examples alongside PowerShell for resource cleanup.
  • Add Bash shell command examples for Linux users.
  • Explicitly mention that both Azure PowerShell and Azure CLI are cross-platform, and provide links to installation guides for both.
  • Where possible, present CLI and PowerShell examples together, or default to CLI for parity.
  • Review other resource management steps to ensure Linux and macOS users are equally supported.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-preview.md ...e-docs/blob/main/articles/firewall/firewall-preview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by referencing Azure PowerShell as a configuration tool without mentioning Azure CLI or Bash alternatives. There are no Linux-specific examples or instructions, and the only command-line tool mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include Azure CLI (az) command examples alongside or instead of PowerShell instructions for feature configuration.
  • Explicitly mention that configuration can be performed from Linux/macOS environments using Azure CLI or Bash scripts.
  • Provide parity in tooling references, ensuring both PowerShell and CLI/Bash options are documented.
  • Where possible, add screenshots or walkthroughs for Linux-based workflows in addition to Windows/PowerShell.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/change-sku.md ...s/azure-docs/blob/main/articles/firewall/change-sku.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias, primarily through the exclusive use of PowerShell for command-line examples and migration scripts. All CLI instructions and automation scripts are written in PowerShell, with no Bash, Azure CLI, or Linux-native alternatives provided. The prerequisites and troubleshooting sections also reference PowerShell modules and patterns, and Windows/PowerShell tooling is mentioned before Terraform. There are no Linux or cross-platform command-line examples, and no mention of Azure CLI or Bash scripting for these operations.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell commands and scripts, ensuring Linux and macOS users can follow along without needing PowerShell.
  • Include Bash script samples for migration and validation steps, or at least show how to use Azure CLI in shell scripts.
  • Explicitly mention cross-platform support for all command-line operations, clarifying which methods work on Linux/macOS.
  • Reorder sections to present cross-platform or neutral tooling (e.g., Azure portal, Azure CLI, Terraform) before Windows-specific tools like PowerShell.
  • Add troubleshooting steps using Azure CLI, not just PowerShell.
  • Update prerequisites to mention Azure CLI as an alternative to PowerShell for users on Linux/macOS.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-availability-zone-powershell.md ...ticles/firewall/deploy-availability-zone-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for deploying Azure Firewall with Availability Zones. There are no CLI or Linux-native examples (such as Azure CLI or ARM template snippets), and PowerShell is mentioned as the primary scripting method. The use of PowerShell and lack of Linux/Unix-friendly alternatives may hinder accessibility for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all deployment steps, ensuring Linux and macOS users can follow along.
  • Include ARM/Bicep template snippets for declarative deployments, which are platform-neutral.
  • Mention Azure CLI and template-based deployment methods before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify that PowerShell is not required and highlight cross-platform options for managing Azure resources.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/choose-firewall-sku.md ...ocs/blob/main/articles/firewall/choose-firewall-sku.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing PowerShell as the first example in the management integration section ('Easy DevOps integration using REST/PowerShell/CLI/templates/Terraform'), implying a Windows-first approach. There is no mention of Linux-specific tools or shell examples (such as Bash), and no explicit Linux command-line instructions or references. The lack of Linux-specific guidance and examples may make it less accessible for Linux users.
Recommendations
  • List CLI (az CLI) and REST before PowerShell when describing management integration options to avoid implying PowerShell/Windows primacy.
  • Explicitly mention Bash or Linux shell usage alongside PowerShell in DevOps integration examples.
  • Provide example commands for both PowerShell and Bash/az CLI in relevant sections.
  • Reference Linux-friendly deployment and configuration guides, or clarify that all features/tools are cross-platform where applicable.
GitHub Create Pull Request
← Previous Page 3 of 14 Next →