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 101-125 of 332 flagged pages
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-private-ip-dnat.md ...lob/main/articles/firewall/tutorial-private-ip-dnat.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 exhibits a strong Windows bias. All VM configuration and testing instructions exclusively reference Windows virtual machines (e.g., 'win-vm-2', 'win-vm-3') and use PowerShell scripts for setup. There are no examples or instructions for Linux VMs, nor are Linux shell commands or configuration scripts provided. The documentation assumes the use of Windows tools (PowerShell, RDP) and does not mention Linux equivalents (SSH, Bash). This limits accessibility for users deploying Linux-based workloads or preferring cross-platform guidance.
Recommendations
  • Add parallel instructions for configuring Linux VMs, including example Bash scripts and SSH connection steps.
  • Provide sample configuration scripts for Linux (e.g., .sh files) alongside the PowerShell scripts.
  • Include screenshots or command-line examples for Linux environments when verifying DNAT rules and connectivity.
  • Explicitly mention that the tutorial applies to both Windows and Linux VMs, and clarify any platform-specific requirements.
  • Ensure monitoring and troubleshooting sections include guidance for Linux-based logging and diagnostic tools.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by referencing Azure PowerShell as a configuration tool without mentioning Azure CLI or other cross-platform alternatives. There are no examples or instructions for Linux users, and the only tool explicitly mentioned for configuration is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include Azure CLI instructions alongside Azure PowerShell for all configuration steps, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for configuration, and provide links or examples for both.
  • Where possible, provide bash or shell script examples in addition to PowerShell scripts.
  • Review all references to tools and ensure Linux-friendly options are presented with equal prominence to Windows tools.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/management-nic.md ...ure-docs/blob/main/articles/firewall/management-nic.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 managing the Azure Firewall Management NIC, with no equivalent Azure CLI (cross-platform) or Bash examples. This creates a bias toward Windows users and those familiar with PowerShell, while Linux users or those preferring CLI tools are not supported. The use of PowerShell-specific cmdlets and lack of mention of Linux-compatible tools or workflows further reinforces this bias.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell scripts for all management operations (stop, start, allocate IPs, etc.).
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to relevant CLI documentation.
  • Include Bash script examples for common operations, or clarify cross-platform support.
  • Where screenshots show portal steps, note that these are platform-agnostic, but for scripting, always provide both PowerShell and CLI examples.
  • Review related documentation for similar biases and update to ensure Linux parity.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/fqdn-tags.md ...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Windows Heavy
Summary
The documentation page demonstrates a Windows bias by predominantly referencing Windows-related services and FQDN tags (e.g., WindowsUpdate, WindowsDiagnostics, WindowsVirtualDesktop, Windows365), with no mention of Linux-specific services or examples. The examples and descriptions focus on Windows endpoints and use cases, and there are no Linux or cross-platform scenarios provided.
Recommendations
  • Add examples or references for Linux-based services and endpoints, such as Azure Linux VM update endpoints or Linux diagnostics.
  • Include FQDN tags relevant to popular Linux workloads (e.g., Ubuntu, Red Hat repositories, Linux-based Azure services).
  • Provide cross-platform application rule examples, demonstrating how FQDN tags can be used for both Windows and Linux environments.
  • Balance the documentation by listing non-Windows tags and use cases before or alongside Windows-specific ones.
  • Explicitly mention that FQDN tags can be used for any supported service, not just Windows-centric ones.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/dns-settings.md ...azure-docs/blob/main/articles/firewall/dns-settings.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides configuration examples using Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell examples are Windows-centric, and there are no explicit Linux shell (bash) examples or references to Linux-specific tools or workflows. The documentation does not mention or demonstrate Linux-native commands (such as bash scripting or cloud-init), nor does it address Linux-specific considerations for DNS configuration or VM restart procedures. The presence of PowerShell examples and the absence of Linux shell examples indicate a Windows bias.
Recommendations
  • Add explicit bash shell examples for all CLI operations, showing how Linux users can perform the same tasks (e.g., using az CLI in bash, scripting VM restarts with SSH/cloud-init).
  • Include notes or sections addressing Linux VM DNS configuration, such as how to update /etc/resolv.conf or use cloud-init for DNS changes.
  • When listing CLI and PowerShell examples, present CLI (cross-platform) examples before PowerShell to avoid Windows-first ordering.
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and provide links or instructions for installing and using Azure CLI on Linux.
  • For VM restart instructions, mention Linux-specific commands (e.g., using SSH and 'sudo reboot') alongside the generic 'restart' advice.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/prescaling.md ...s/azure-docs/blob/main/articles/firewall/prescaling.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 a PowerShell example for prescaling configuration, mentioning Azure PowerShell as a primary configuration method, and omitting equivalent CLI (az CLI) or Linux shell examples. Windows-centric tools and patterns (PowerShell) are referenced before cross-platform alternatives, and there is no guidance for users who prefer or require Linux-native tools.
Recommendations
  • Add an Azure CLI example for configuring prescaling, using bash syntax, to provide parity for Linux and macOS users.
  • Explicitly mention that Azure CLI and REST API can also be used for configuration, and link to relevant documentation.
  • Reorder configuration options to present cross-platform tools (Azure CLI, ARM templates, Bicep) before or alongside PowerShell.
  • Include notes or guidance for users on Linux/macOS regarding tool availability and usage.
  • Ensure screenshots and instructions are not Windows-specific unless alternatives are provided.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-private-ip-dnat.md ...lob/main/articles/firewall/tutorial-private-ip-dnat.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in the VM setup and configuration sections. Only Windows virtual machines (win-vm-2, win-vm-3) are referenced, and all configuration instructions use PowerShell scripts. There are no examples or guidance for deploying or configuring Linux VMs, nor are Linux shell commands or tools mentioned. The tutorial assumes the use of Windows tools and patterns throughout the VM configuration and testing steps.
Recommendations
  • Include equivalent instructions for deploying and configuring Linux VMs (e.g., Ubuntu, CentOS) in the test environment.
  • Provide Bash shell script examples alongside PowerShell scripts for VM configuration.
  • Reference Linux-native tools (such as SSH, curl, iptables, etc.) for testing connectivity and DNAT functionality.
  • Clarify that the tutorial applies to both Windows and Linux environments, and provide parity in troubleshooting and monitoring steps.
  • Add screenshots or walkthroughs for Linux VM configuration in the Azure portal, similar to those for Windows 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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias toward Windows environments by exclusively providing a PowerShell example for resource cleanup (`Remove-AzResourceGroup`) and omitting equivalent instructions for Linux users (such as Azure CLI or Bash). No Linux shell commands or cross-platform alternatives are presented, and the only automation example uses a Windows-centric tool. While the template itself deploys Linux VMs, the operational instructions favor Windows tooling.
Recommendations
  • Provide equivalent Azure CLI commands (e.g., `az group delete --name <your resource group name>`) alongside PowerShell examples for resource cleanup.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and link to cross-platform installation guides.
  • Where possible, offer Bash or shell script examples for Linux/macOS users.
  • Add a note clarifying that the instructions apply to all platforms and highlight any platform-specific differences.
  • Review other operational steps to ensure parity in examples and tooling for both Windows and Linux users.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal.md .../blob/main/articles/firewall/tutorial-hybrid-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by exclusively using Windows Server virtual machines for both workload and on-premises examples, providing only PowerShell-based instructions for VM configuration (IIS installation), and omitting any Linux-based VM or shell examples. The walkthrough assumes Windows-centric tools and patterns, such as RDP for remote access and PowerShell for automation, without mentioning or prioritizing Linux alternatives.
Recommendations
  • Include parallel examples using Linux VMs (e.g., Ubuntu) for both workload and on-premises scenarios.
  • Provide instructions for installing and testing a web server (e.g., Apache or Nginx) on Linux VMs, using Bash or Azure CLI commands.
  • Offer remote access examples using SSH for Linux VMs, alongside RDP for Windows.
  • When showing automation or scripting steps, provide both PowerShell and Bash/Azure CLI equivalents.
  • Explicitly mention that the process applies to both Windows and Linux environments, and clarify any platform-specific differences.
  • Balance the order of examples so that Linux and Windows are presented with equal prominence.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-cli.md ...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 by exclusively using Windows Server images for VM creation, referencing Remote Desktop for access, and providing only PowerShell-based test commands. There are no Linux VM deployment examples, nor are there instructions for connecting to or testing from Linux VMs (e.g., using SSH or Bash commands). Windows tools and workflows (RDP, PowerShell) are mentioned exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
  • Add parallel examples for deploying Linux-based VMs (e.g., Ubuntu) alongside Windows VMs.
  • Include instructions for connecting to Linux VMs using SSH, as well as to Windows VMs using RDP.
  • Provide test commands for Linux environments (e.g., using dig, curl, or wget in Bash) in addition to PowerShell commands.
  • Mention Linux tools and workflows (e.g., SSH, Bash, Linux CLI utilities) wherever Windows tools (RDP, PowerShell) are referenced.
  • Consider a section that discusses platform-specific differences and best practices for both Windows and Linux administrators.
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-08 00:53
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 listing PowerShell as a primary management tool and referencing REST/PowerShell/CLI/templates/Terraform for DevOps integration, with PowerShell mentioned before CLI (which is more cross-platform). There are no explicit Linux-specific examples or mentions of Linux-native tools, and no Linux command-line instructions or screenshots. The documentation does not provide parity in examples or tool references for Linux users.
Recommendations
  • Explicitly mention Azure CLI before PowerShell when listing management tools, as CLI is cross-platform and widely used on Linux.
  • Provide Linux-specific examples or instructions for deploying and managing Azure Firewall (e.g., bash commands, screenshots from Linux terminals).
  • Clarify that all listed management tools (REST, CLI, Terraform) are cross-platform and provide links to their Linux usage guides.
  • Include a note or section on best practices for Azure Firewall management from Linux environments.
  • Ensure that future documentation includes parity in examples and instructions for both Windows and Linux users.
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-08 00:53
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 only Windows in the subnet descriptions, and providing only PowerShell commands for resource cleanup. There are no Linux VM examples, nor are Linux-specific tools or commands (such as Bash or Azure CLI) referenced for management tasks.
Recommendations
  • Include examples that deploy Linux-based virtual machines alongside or instead of Windows Server VMs.
  • Mention Linux as an option in subnet descriptions and resource deployment steps.
  • Provide equivalent cleanup instructions using Azure CLI or Bash, not just PowerShell.
  • Ensure that any administrative steps (e.g., username/password creation) clarify that both Windows and Linux VM types are supported.
  • Add links or references to Linux-specific documentation where relevant.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ftp-support.md .../azure-docs/blob/main/articles/firewall/ftp-support.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 prioritizing Azure PowerShell examples and references, mentioning PowerShell before CLI and ARM templates. All code samples for updating and deploying Azure Firewall use PowerShell, with only brief mention of Azure CLI and ARM templates and no explicit Linux shell (bash) examples. There is no discussion of Linux-specific tooling or patterns, nor any parity in example depth between Windows and Linux environments.
Recommendations
  • Provide equivalent bash/Azure CLI examples with full code snippets, not just parameter references.
  • Include explicit instructions for Linux/macOS users, such as using Azure CLI in bash or shell environments.
  • Balance the order of presentation: alternate or start with CLI/bash examples before PowerShell.
  • Add notes or sections on how to perform these tasks from Linux-based systems, including any OS-specific considerations.
  • Ensure all referenced documentation links include both PowerShell and CLI/bash instructions.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/explicit-proxy.md ...ure-docs/blob/main/articles/firewall/explicit-proxy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily through its 'Next steps' section, which links only to Azure PowerShell deployment instructions and omits equivalent Linux/CLI examples. There is no mention of Linux tools, Bash, or cross-platform configuration patterns. The documentation implicitly assumes a Windows-centric workflow, especially for deployment and management tasks.
Recommendations
  • Add links and examples for deploying and configuring Azure Firewall using Azure CLI (cross-platform) and Bash scripts.
  • Include explicit instructions or references for Linux and macOS users, such as configuring proxy settings in browsers or applications on those platforms.
  • Mention platform-agnostic tools and workflows, ensuring parity between Windows and Linux environments.
  • Where PowerShell is referenced, also provide Azure CLI or REST API equivalents.
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-08 00:53
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 deploying Azure Firewall with Availability Zones, with no equivalent examples for Linux-native tools such as Azure CLI or ARM templates. The use of PowerShell is highlighted as the primary scripting method, and there is no mention of Linux shell commands or cross-platform deployment patterns. This may hinder Linux users or those preferring non-Windows environments from following the guidance easily.
Recommendations
  • Add equivalent Azure CLI examples for configuring Availability Zones during Azure Firewall deployment.
  • Include ARM/Bicep template snippets to demonstrate infrastructure-as-code approaches that are platform-agnostic.
  • Explicitly mention that Azure CLI and ARM templates can be used from Linux, macOS, and Windows environments.
  • Reorder sections so that cross-platform tools (e.g., Azure CLI, ARM templates) are presented before or alongside PowerShell examples.
  • Clarify any platform-specific limitations or considerations for each method.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ip-groups.md ...cs/azure-docs/blob/main/articles/firewall/ip-groups.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by listing only Azure PowerShell cmdlets for managing IP Groups, referencing PowerShell in the metadata, and omitting equivalent Azure CLI or REST API commands. The 'Related Azure PowerShell cmdlets' section is prominent, while Linux-friendly tools and examples (such as Azure CLI) are not provided or mentioned in detail. The ordering and emphasis suggest a preference for Windows/PowerShell tooling.
Recommendations
  • Add a 'Related Azure CLI commands' section with equivalent az network ip-group commands for Linux/macOS users.
  • Provide example workflows using Azure CLI and REST API, not just PowerShell.
  • Ensure that references to PowerShell are balanced with CLI and REST API throughout the documentation.
  • Review metadata and custom tags to avoid exclusive tracking of PowerShell (e.g., devx-track-azurepowershell) unless CLI is also tracked.
  • When listing tools or commands, present Azure CLI and REST API before or alongside PowerShell to avoid 'windows_first' ordering.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias, primarily by providing extensive PowerShell-based instructions and scripts for Azure Firewall SKU changes and migrations. All command-line examples are given in PowerShell syntax, with no equivalent examples for Bash, Azure CLI, or Linux-native tooling. The prerequisites and troubleshooting sections also reference PowerShell modules and patterns exclusively, and the order of presentation consistently places PowerShell and portal methods before Terraform, with no mention of Azure CLI or Linux shell alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands and scripts, ensuring Linux/macOS users have clear instructions.
  • Include Bash shell script samples for common migration and SKU change tasks.
  • Explicitly mention cross-platform tools (e.g., Azure CLI) in prerequisites and troubleshooting sections, not just PowerShell.
  • Reorder sections or provide parallel instructions so that Linux-friendly methods (Azure CLI, Bash) are presented alongside or before Windows/PowerShell examples.
  • Clarify that all methods (portal, PowerShell, Terraform, Azure CLI) are supported and provide links to relevant cross-platform documentation.
  • Add notes or tables comparing PowerShell and Azure CLI syntax for key operations.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/customer-controlled-maintenance.md ...n/articles/firewall/customer-controlled-maintenance.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples and references before Azure CLI equivalents, and by introducing PowerShell as the primary scripting interface for automation. The initial example for registering the resource provider uses PowerShell, and the PowerShell section precedes the CLI section in the tab order. There is no mention of Linux-specific tools, shell environments, or scripting patterns, and screenshots and UI descriptions are generic but implicitly Windows-oriented due to the PowerShell focus. The CLI section is present, but is secondary and lacks parity in introductory emphasis.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, especially for common tasks like resource provider registration.
  • Explicitly mention Linux and macOS compatibility in CLI sections, and provide guidance for Bash/Zsh environments.
  • Add notes or examples for scripting with Bash or other Linux shells where automation is discussed.
  • Balance introductory language to avoid implying PowerShell is the default or preferred automation tool.
  • Where screenshots are used, clarify that the Azure portal is cross-platform and accessible from any OS/browser.
  • Consider adding a section or sidebar on cross-platform automation best practices for Azure Firewall maintenance.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-sftp.md ...zure-docs/blob/main/articles/firewall/firewall-sftp.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments, as all deployment and configuration steps use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tools. The setup instructions, variable initialization, and resource management are exclusively shown using PowerShell syntax, which is most familiar to Windows users. There are no Linux-specific or cross-platform examples for infrastructure deployment, nor guidance for users who may prefer Bash or Azure CLI. The only cross-platform nod is the use of the generic 'sftp' client for connection testing, but even this is described as being run from a 'command prompt', which typically implies Windows.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all resource creation, configuration, and cleanup steps.
  • Explicitly mention that the instructions can be followed on Linux and macOS, and provide guidance for installing and using Azure CLI on those platforms.
  • Clarify that 'command prompt' could refer to Windows Command Prompt, PowerShell, or a Linux/macOS terminal, and provide explicit instructions for each.
  • Include links to cross-platform tooling documentation (e.g., Azure CLI install and usage guides).
  • Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., SSH key formats, SFTP client differences).
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/integrate-with-nat-gateway.md ...b/main/articles/firewall/integrate-with-nat-gateway.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 presenting Azure PowerShell examples first, followed by Azure CLI. There are no Linux-specific shell examples (e.g., Bash scripts), nor are there references to Linux-native tools or patterns. The use of PowerShell as the primary example and the absence of explicit Linux context or troubleshooting guidance suggests a preference for Windows environments.
Recommendations
  • Add Bash shell script examples for Linux users, especially for common deployment scenarios.
  • Include notes or sections on Linux-specific considerations, such as file permissions, environment variables, or troubleshooting steps relevant to Linux.
  • Ensure parity in example ordering by alternating or randomizing the order of PowerShell and CLI examples, or by explicitly stating that both Windows and Linux are supported equally.
  • Reference Linux-native tools or patterns where applicable, such as using cloud-init or other automation tools popular in Linux environments.
  • Clarify that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide links to installation guides for each platform.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/features-by-sku.md ...re-docs/blob/main/articles/firewall/features-by-sku.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-specific features and tools before their Linux equivalents. For example, the 'FQDN tags' section highlights the Windows Update tag as the primary example, and management/integration options consistently list 'PowerShell' before 'CLI', which is more commonly used on Linux. There are no explicit Linux-centric examples (e.g., allowing traffic for Linux package repositories), and no Linux-specific tools or patterns are mentioned.
Recommendations
  • Provide Linux-centric examples alongside Windows ones, such as allowing traffic for Ubuntu/Debian/Red Hat package repositories (e.g., apt, yum, or dnf).
  • When listing management/integration options, alternate or balance the order (e.g., 'CLI/PowerShell/REST/templates/Terraform') or explicitly mention Bash/CLI for Linux users.
  • In sections like FQDN tags, include examples relevant to Linux environments (e.g., allowing traffic for 'Ubuntu Updates', 'Debian Security', or 'Red Hat CDN').
  • Add notes or links to Linux-specific guidance where appropriate, such as configuring Azure Firewall rules for Linux-based workloads.
  • Ensure that diagrams and screenshots, if any, are platform-neutral or include both Windows and Linux scenarios.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall.md ...e-docs/blob/main/articles/firewall/monitor-firewall.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Azure PowerShell is mentioned as the required method for enabling certain features (e.g., Fat Flow Log), with no mention of Azure CLI or Bash alternatives. The log converter tool is referenced as a Visual Studio/C# solution, which is Windows-centric, and there are no Linux or cross-platform equivalents suggested. Data visualization examples focus on Excel and Power BI, which are primarily Windows tools, and Linux-friendly options are not highlighted. Throughout, Windows-specific tools and patterns are mentioned exclusively or before any Linux alternatives, and there are no explicit Linux command-line or tool examples provided.
Recommendations
  • Provide Azure CLI and Bash examples alongside or instead of PowerShell for configuration tasks, especially for enabling features like Fat Flow Log.
  • Reference cross-platform log converter tools (e.g., Python scripts) or provide instructions for converting logs using Linux utilities (jq, csvkit, etc.).
  • Include Linux-friendly data visualization options (e.g., LibreOffice Calc, Grafana, Kibana) when discussing CSV/JSON log analysis.
  • When mentioning Visual Studio/C#, also suggest cross-platform development environments (e.g., VS Code, JetBrains Rider) and alternative languages (Python, Go).
  • Explicitly state that all log download, conversion, and analysis steps can be performed on Linux and macOS, and provide sample commands.
  • Ensure that screenshots and walkthroughs are not exclusively from Windows environments; include Azure Portal views from browsers on Linux/macOS.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-known-issues.md ...s/blob/main/articles/firewall/firewall-known-issues.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. Several mitigation steps and workarounds reference PowerShell cmdlets (e.g., Set-AzFirewallPolicy) without providing equivalent Azure CLI or REST API examples, which are more platform-neutral and commonly used on Linux/macOS. There is also mention of IIS as an FTP server example, a Windows-centric technology, without Linux alternatives. No explicit Linux or cross-platform command-line examples are provided, and references to CLI support are limited to noting feature gaps rather than offering parity.
Recommendations
  • For every PowerShell example or cmdlet mentioned, provide an equivalent Azure CLI and/or REST API example.
  • When referencing FTP server configuration, include examples for popular Linux FTP servers (e.g., vsftpd, proftpd) alongside IIS.
  • Where mitigation steps involve command-line operations, ensure both Windows (PowerShell) and Linux/macOS (Azure CLI, bash) workflows are documented.
  • Explicitly state platform support and limitations for all tools and commands mentioned.
  • Review all troubleshooting steps and ensure Linux users are not left without guidance or examples.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy-certificates-enterprise-ca.md .../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. All certificate management steps rely on Windows-specific tools (certtmpl.msc, Internet Explorer, Windows Server), and prerequisites assume Active Directory and AD CS. There are no examples or guidance for Linux-based PKI solutions, certificate requests, or exports using OpenSSL or other cross-platform tools. The workflow is inaccessible to users operating in Linux-only or mixed environments.
Recommendations
  • Add equivalent instructions for Linux environments, including how to generate and manage subordinate CA certificates using OpenSSL or other Linux PKI tools.
  • Provide examples for requesting and exporting certificates on Linux, such as using OpenSSL commands or web-based CA interfaces compatible with Linux.
  • Mention alternatives to Active Directory Certification Services, such as EJBCA, Dogtag, or OpenSSL-based CA setups.
  • Clarify that the process can be performed on non-Windows platforms and provide parity in step-by-step guidance.
  • Include screenshots or command-line examples for Linux alongside Windows instructions.
  • Avoid assuming Internet Explorer or Windows Server as the only platforms for certificate management.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-bicep.md ...in/articles/firewall/quick-create-multiple-ip-bicep.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows bias by focusing exclusively on deploying and connecting to Windows Server 2019 VMs, referencing Remote Desktop Connection (a Windows tool) as the validation method, and providing PowerShell examples for resource cleanup without equivalent Bash or Linux instructions. There are no Linux VM deployment or SSH connection examples, and Windows terminology/tools are mentioned before or instead of Linux alternatives.
Recommendations
  • Include examples for deploying Linux virtual machines alongside Windows VMs in the Bicep template.
  • Add instructions for connecting to Linux VMs using SSH, including sample SSH commands.
  • Provide resource cleanup instructions using Azure CLI (Bash) in addition to PowerShell.
  • Mention Linux-compatible remote access tools (e.g., SSH clients) in the validation section.
  • Ensure parity in documentation by presenting both Windows and Linux scenarios and tools equally.
GitHub Create Pull Request
← Previous Page 5 of 14 Next →