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 226-250 of 332 flagged pages
Firewall Deploy & configure Azure Firewall Basic and policy using the Azure portal ...ticles/firewall/deploy-firewall-basic-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example operating system for the workload VM, and all testing instructions assume Windows tools (Remote Desktop, Internet Explorer). There are no Linux VM deployment steps, nor guidance for connecting to or testing with Linux-based systems. This creates friction for users who prefer or require Linux workloads.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including appropriate Azure Marketplace image selection.
  • Provide Linux-specific connection guidance (e.g., SSH via DNAT, using an RDP client for Linux if needed, or using xrdp on the Linux VM).
  • Include testing steps using common Linux browsers (e.g., Firefox, Chromium) and command-line tools (e.g., curl, dig) to verify firewall rules.
  • Explicitly mention that the firewall and policy configuration applies equally to Linux VMs, and clarify any OS-specific considerations.
  • Where possible, show both Windows and Linux examples side-by-side for key steps.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Terraform ...e-docs/blob/main/articles/firewall/deploy-terraform.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively deploys Windows Server virtual machines in its example environment and only provides instructions for creating Azure Windows VMs. There are no examples or guidance for deploying Linux VMs, nor is there mention of Linux-specific patterns or parity. This creates friction for users who want to follow the quickstart with Linux-based workloads.
Recommendations
  • Add parallel instructions and Terraform code samples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
  • Include notes or sections explaining how to adapt the example for Linux environments.
  • Provide examples of generating random passwords for Linux VMs and any relevant configuration differences.
  • Ensure that both Windows and Linux VM deployment options are presented, ideally side-by-side or with clear selection guidance.
GitHub Create Pull Request
Firewall Azure Firewall FTP support .../azure-docs/blob/main/articles/firewall/ftp-support.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed instructions for enabling Active FTP on Azure Firewall using Azure PowerShell, Azure CLI, and ARM templates. However, the PowerShell examples are more prominent and detailed, with explicit code snippets and links, while the Azure CLI section is brief and lacks example commands. There are no Linux/macOS-specific instructions or examples, and PowerShell (primarily a Windows tool) is presented first and in more detail, suggesting a Windows-centric approach.
Recommendations
  • Add explicit Azure CLI example commands for enabling Active FTP, similar to the PowerShell section.
  • Clarify that Azure CLI is cross-platform and provide usage instructions for Linux/macOS environments.
  • Consider providing Bash or shell script examples for Linux users.
  • Reorder sections so that Azure CLI instructions appear before or alongside PowerShell to avoid Windows-first bias.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, and provide installation guidance.
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-13 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 only Azure PowerShell examples for stopping and starting the firewall, allocating public IPs, and configuring the Management NIC. There are no CLI (az), Bash, or Linux/macOS-specific instructions, and PowerShell is a Windows-centric tool. The examples and instructions implicitly assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Present CLI and PowerShell examples side-by-side, or at least alternate which is shown first.
  • Clarify that all steps can be performed from any OS using the Azure portal or CLI, not just PowerShell.
GitHub Create Pull Request
Firewall Azure Firewall known issues and limitations ...s/blob/main/articles/firewall/firewall-known-issues.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Firewall known issues and limitations demonstrates a moderate Windows bias. Notably, mitigation steps reference Azure PowerShell cmdlets (e.g., Set-AzFirewallPolicy) as the only example for updating firewall policy tags, with no mention of equivalent Azure CLI or REST API commands. There is also an explicit mention of missing PowerShell and CLI support for ICMP, but no Linux-specific guidance or parity discussion. The only tool-based workaround provided is PowerShell, which is most commonly used on Windows. No Linux/macOS-specific examples or alternatives are given, and the documentation does not clarify cross-platform command parity.
Recommendations
  • Provide Azure CLI and REST API examples alongside PowerShell cmdlets for all operations, especially for updating firewall policy tags.
  • Explicitly state cross-platform compatibility for all command-line tools and document any differences in usage between Windows, Linux, and macOS.
  • Add Linux/macOS-specific troubleshooting steps or notes where PowerShell is referenced, including guidance for using Azure CLI or REST API.
  • Ensure that all mitigation steps and workarounds are accessible to users on Linux/macOS, not just Windows/PowerShell users.
GitHub Create Pull Request
Firewall Access a storage account using SFTP over an Azure Firewall static public IP address ...zure-docs/blob/main/articles/firewall/firewall-sftp.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 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 tooling. All code samples use PowerShell syntax, and instructions for installing and running Azure PowerShell are given without alternatives for Linux/macOS users. The only SFTP client example is generic, but the workflow assumes familiarity with Windows/PowerShell environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all deployment and configuration steps, with Bash syntax examples.
  • Include installation instructions for Azure CLI and note cross-platform compatibility.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links to relevant documentation.
  • Where PowerShell is required (e.g., for certain Azure features), clarify if Azure CLI is not supported and suggest workarounds or alternatives.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps.
GitHub Create Pull Request
Firewall FQDN tags overview for Azure Firewall ...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by prioritizing Windows-related services and examples (e.g., WindowsUpdate, WindowsDiagnostics, Windows365, WindowsVirtualDesktop) in both explanations and the FQDN tag table. The majority of examples and tags are focused on Microsoft Windows services, with little mention of Linux/macOS-specific scenarios or cross-platform considerations. There are no Linux/macOS-specific FQDN tags or examples provided.
Recommendations
  • Include examples or references for Linux/macOS scenarios, such as allowing outbound access for popular Linux repositories, package managers, or services.
  • Add FQDN tags or guidance relevant to cross-platform or non-Windows services (e.g., GitHub, Docker registries, Linux update mirrors) if supported.
  • Balance the documentation by mentioning both Windows and Linux/macOS use cases where possible.
  • Explicitly state if FQDN tags are only available for Microsoft services, and suggest alternative approaches for non-Windows environments.
GitHub Create Pull Request
Firewall Monitoring data reference for Azure Firewall ...b/main/articles/firewall/monitor-firewall-reference.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by providing only Azure PowerShell command examples for enabling and disabling key logging features (DNS Flow Trace Logs, Top Flows logs, Flow Trace logs). There are no equivalent CLI (az), Bash, or cross-platform instructions, nor are Linux/macOS-specific considerations mentioned. This creates friction for users who do not use Windows or PowerShell as their primary environment.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state whether features can be enabled via the Azure portal, REST API, or ARM templates, and provide those instructions if available.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI or PowerShell Core.
  • Reorder or parallelize examples so that CLI and PowerShell instructions are presented together, not PowerShell-only.
  • Clarify any platform limitations (e.g., if a feature truly requires PowerShell, explain why and suggest alternatives if possible).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. The test environment exclusively deploys a Windows virtual machine (WorkerVM), and all instructions for testing (e.g., opening a command prompt, using a browser) are given for Windows. There are no Linux/macOS equivalents or examples for deploying a Linux VM, running curl from a Linux shell, or using Linux browsers. The certificate deployment step is described only for Windows, and the Bastion host is suggested solely for connecting to the Windows VM.
Recommendations
  • Provide instructions and examples for deploying a Linux test VM alongside or instead of the Windows VM.
  • Include Linux/macOS-specific steps for running curl and browser-based tests (e.g., using GNOME Terminal, Firefox, Chrome).
  • Describe how to install and use the Intermediate CA certificate on Linux/macOS clients.
  • Clarify that the firewall features and testing steps are OS-agnostic, and provide parity in examples.
  • Mention how to connect to Linux VMs via Bastion or SSH, not just Windows.
  • Consider showing both Windows and Linux command-line examples side-by-side.
GitHub Create Pull Request
Firewall Azure Firewall prescaling ...s/azure-docs/blob/main/articles/firewall/prescaling.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell example for configuring Azure Firewall prescaling, but does not include equivalent CLI (az), Bash, or Linux/macOS-specific instructions. PowerShell is a Windows-centric tool, and its example is presented before mentioning Bicep or ARM templates. There is no mention of Azure CLI or cross-platform scripting options, which may create friction for Linux/macOS users.
Recommendations
  • Add an Azure CLI (az) example for configuring prescaling, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell examples can be run on Linux/macOS via PowerShell Core, or provide Bash script equivalents.
  • Present examples in a more platform-neutral order (e.g., Portal, CLI, PowerShell, Bicep), or group them together with clear platform applicability notes.
  • Include links or references to documentation for ARM template usage, which is platform-agnostic.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a Windows PowerShell example for resource cleanup, omitting equivalent Linux/macOS CLI commands. The use of the Remove-AzResourceGroup cmdlet is Windows/PowerShell-centric, and there is no mention of Azure CLI or Bash alternatives for Linux/macOS users. This creates friction for non-Windows users, especially in the cleanup step.
Recommendations
  • Include Azure CLI (az group delete) examples alongside PowerShell for resource group deletion.
  • Explicitly mention that both PowerShell and Azure CLI can be used on any platform, and provide cross-platform instructions.
  • Where possible, show both Windows and Linux/macOS command examples for operational steps.
  • Add a note or section clarifying platform compatibility for deployment and management tasks.
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-13 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 Windows bias by focusing exclusively on Azure Virtual Desktop, which is inherently Windows-based, and referencing Windows-specific service tags, endpoints, and tools (such as Microsoft Edge proxy configuration). There are no examples or guidance for Linux or macOS session hosts, nor for configuring proxies or firewall rules for non-Windows environments. The documentation assumes the use of Windows tools and patterns throughout.
Recommendations
  • Clarify whether Azure Virtual Desktop supports Linux/macOS session hosts and, if so, provide equivalent guidance for those platforms.
  • Include examples of configuring outbound access, firewall rules, and proxy settings for Linux/macOS environments (e.g., using iptables, ufw, or Linux browser proxy settings).
  • Reference cross-platform tools and methods for proxy configuration, not just Microsoft Edge or Windows-specific approaches.
  • Explicitly state any platform limitations or requirements so non-Windows users understand the scope.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by focusing exclusively on deploying Windows Server VMs and enabling RDP access, with no mention of Linux VM deployment or SSH access. Additionally, the only referenced alternative deployment guide is for Azure PowerShell, a tool more commonly associated with Windows environments. However, the Terraform and Azure CLI instructions themselves are cross-platform.
Recommendations
  • Include parallel instructions or notes for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) and enabling SSH access.
  • Reference Linux/macOS-friendly tools and guides (such as Bash or Azure CLI) alongside or before Windows/PowerShell alternatives.
  • Provide example NAT/firewall rules for SSH (port 22) to Linux VMs in addition to RDP for Windows.
  • When linking to further reading, include both PowerShell and Azure CLI/Bash-based guides.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for configuring service tags in Azure Firewall. There are no Azure CLI or Bash examples, and PowerShell is presented as the primary method, which is most commonly used on Windows. This creates friction for Linux/macOS users who typically use Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps shown in PowerShell.
  • Explicitly mention that Azure CLI and the Azure portal are supported, and provide links or examples for those workflows.
  • Consider presenting CLI or portal instructions before or alongside PowerShell to avoid Windows-first bias.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively demonstrates deploying and testing Azure Firewall DNAT with a Windows Server 2019 virtual machine and only provides instructions for testing via Remote Desktop (RDP), which is Windows-specific. There are no Linux VM deployment instructions, nor are SSH or Linux-based connectivity examples provided. This creates friction for users wishing to use Linux workloads or test with Linux tools.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Provide examples for testing DNAT using SSH to a Linux VM, including port configuration and connectivity steps.
  • Mention both RDP (Windows) and SSH (Linux/macOS) as valid test methods, with step-by-step guidance for each.
  • Ensure screenshots and portal steps reference both OS types where relevant.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by focusing exclusively on RDP connections to Windows Server VMs, referencing Windows tools (Remote Desktop Connection), and omitting Linux/macOS connection examples. The clean-up instructions use PowerShell only, and there is no mention of SSH or Linux VM scenarios.
Recommendations
  • Include examples for connecting to Linux VMs using SSH, alongside RDP for Windows.
  • Mention cross-platform tools (e.g., SSH, native RDP clients for macOS/Linux) for remote access.
  • Provide clean-up instructions using Azure CLI, which is cross-platform, in addition to PowerShell.
  • Clarify that the firewall NAT rules can support both RDP and SSH, and show how to configure rules for Linux VM access.
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-13 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 detailed configuration steps exclusively using Azure PowerShell cmdlets, which are native to Windows environments. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The PowerShell approach is presented as the only code-based method, and it appears before any mention of alternatives. This creates friction for Linux/macOS users who typically use Azure CLI or REST API, and may not have access to PowerShell or prefer not to use it.
Recommendations
  • Add equivalent Azure CLI (az) examples for all configuration steps, including new and existing firewall setups.
  • Explicitly mention that Azure CLI and REST API can be used, and provide links or code samples.
  • Reorder examples so that cross-platform tools (CLI, portal) are presented before or alongside PowerShell.
  • Clarify any limitations or differences between PowerShell and CLI approaches, if any.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates deployment and testing using a Windows Server virtual machine and remote desktop (RDP) access, with no mention of Linux VM options or SSH connectivity. All testing instructions assume Windows tools (RDP, Edge, Internet Explorer), and there are no Linux/macOS-specific steps or alternatives provided. The only reference to alternatives is a link to a PowerShell-based tutorial, which is also Windows-centric.
Recommendations
  • Add instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including relevant configuration steps.
  • Provide testing steps for Linux/macOS users, such as connecting via SSH and using curl or wget to verify outbound access.
  • Include examples for configuring DNAT rules for SSH (port 22) in addition to RDP (port 3389).
  • Mention cross-platform browser options and clarify that firewall rules apply regardless of OS.
  • Ensure parity in screenshots and walkthroughs for both Windows and Linux VM scenarios.
GitHub Create Pull Request
Firewall Tutorial: Filter inbound Internet or intranet traffic with Azure Firewall DNAT policy using the portal ...ain/articles/firewall/tutorial-firewall-dnat-policy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates deploying and testing Azure Firewall DNAT with a Windows Server virtual machine and remote desktop (RDP) connectivity. There are no examples or instructions for creating a Linux VM, nor for testing access using Linux-native tools (e.g., SSH). The only operating system mentioned for the workload is Windows, and the test scenario is RDP, which is Windows-specific.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include examples for testing DNAT access using SSH to a Linux VM, alongside the RDP example.
  • Mention Linux/macOS-compatible tools for remote access (e.g., SSH clients) in the 'Test the firewall' section.
  • Clarify that the DNAT configuration works for both Windows and Linux workloads, and provide guidance for each.
GitHub Create Pull Request
Firewall Deploy & configure Azure Firewall using the Azure portal ...n/articles/firewall/tutorial-firewall-deploy-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example operating system for the test VM, and all testing instructions (such as remote desktop and browser usage) are Windows-centric. There are no Linux or macOS equivalents provided for VM creation, connectivity, or firewall rule testing, which may hinder non-Windows users from following the tutorial seamlessly.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the test subnet, including required settings.
  • Provide guidance for connecting to a Linux VM (using SSH instead of RDP) and testing outbound connectivity (e.g., using curl or wget to test application rules, dig/nslookup for DNS rules).
  • Explicitly mention that the firewall configuration applies to any OS and clarify which steps are OS-specific.
  • Include screenshots or command-line examples for Linux/macOS users where appropriate.
  • Reorder or parallelize example sections so that Windows and Linux instructions are presented together, rather than Windows-only or Windows-first.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All virtual machine creation examples use Windows Server images, and the only provided method for installing IIS on the VM uses PowerShell via Azure Cloud Shell. There are no Linux VM examples, nor instructions for deploying or configuring Linux workloads. The documentation assumes RDP (Windows remote desktop) for connectivity and does not mention SSH or Linux equivalents. Windows tools and patterns (PowerShell, RDP, Windows Server) are referenced exclusively and/or before any Linux alternatives.
Recommendations
  • Include parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu, CentOS) in both spoke and on-premises roles.
  • Provide Linux-specific examples for installing a web server (e.g., Apache or Nginx) using Bash or cloud-init scripts.
  • Add SSH connectivity instructions for Linux VMs, alongside RDP for Windows.
  • Show how to use Azure CLI (cross-platform) for deployment steps, not just PowerShell.
  • Mention Linux firewall and networking considerations where relevant.
GitHub Create Pull Request
Firewall Tutorial: Deploy a firewall with Azure DDoS Protection ...in/articles/firewall/tutorial-protect-firewall-ddos.md
Medium Priority View Details →
Scanned: 2026-01-13 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 operating system for the workload VM and only describes remote desktop (RDP) access and Internet Explorer for testing. There are no instructions or examples for deploying a Linux VM, connecting via SSH, or using Linux-native tools/browsers. This creates a bias toward Windows users and may cause friction for Linux/macOS users following the tutorial.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include SSH access setup and DNAT rule examples for port 22, alongside RDP for Windows.
  • Provide testing steps using Linux tools (e.g., curl, wget, Firefox/Chrome) to verify firewall rules.
  • Mention that the tutorial applies to both Windows and Linux workloads, and clarify any OS-specific steps.
  • Show both Windows and Linux examples for DNS configuration and connectivity testing.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Bicep ...azure-docs/blob/main/articles/firewall/deploy-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively deploying Windows Server virtual machines in the example environment and not mentioning or providing Linux VM equivalents. All deployment and management instructions are cross-platform (Azure CLI and PowerShell), but the infrastructure created is Windows-centric, which may alienate Linux users or suggest that Windows is the default or preferred OS for such scenarios.
Recommendations
  • Include examples that deploy both Windows and Linux virtual machines, or provide an option to choose the OS type in the Bicep template.
  • Explicitly mention that Linux VMs can be used in place of Windows VMs and provide sample parameters or code snippets for Linux VM deployment.
  • Clarify that the jump box and server roles are not limited to Windows and can be fulfilled by Linux VMs.
  • Add a note or section discussing considerations for Linux environments, such as SSH access and Linux-specific configuration steps.
GitHub Create Pull Request
Firewall Deploy & configure Azure Firewall Basic and policy using the Azure portal ...ticles/firewall/deploy-firewall-basic-portal-policy.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides instructions for deploying a Windows Server 2019 Datacenter VM as the workload server and only describes remote desktop (RDP) access for testing. There are no examples or guidance for deploying a Linux VM, connecting via SSH, or testing with Linux tools. Windows is the default and only example given, which may exclude or inconvenience users who prefer or require Linux environments.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include examples for connecting to the Linux VM using SSH, and testing outbound access using Linux command-line tools (e.g., curl, dig).
  • Provide guidance for configuring DNAT rules for SSH (port 22) in addition to RDP.
  • Mention both Windows and Linux options when describing VM creation, testing, and rule configuration.
  • Ensure screenshots and step-by-step instructions are available for both platforms.
GitHub Create Pull Request
Firewall Tutorial: Deploy a firewall with Azure DDoS Protection ...in/articles/firewall/tutorial-protect-firewall-ddos.md
Medium Priority View Details →
Scanned: 2026-01-11 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 operating system for the workload VM, and all testing instructions assume a Windows environment (e.g., using Remote Desktop and Internet Explorer). There are no Linux VM deployment instructions, nor are there examples for connecting to or testing from a Linux machine. Additionally, Windows tools and patterns (RDP, IE) are mentioned without Linux equivalents.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include steps for connecting to the Linux VM (e.g., SSH) and testing firewall rules using Linux tools (such as curl or wget for HTTP/S, dig or nslookup for DNS).
  • Mention Linux-friendly browsers (e.g., Firefox, Chromium) for testing outbound access.
  • Where Windows-specific tools or terminology are used, provide Linux alternatives or note cross-platform options.
  • Ensure that screenshots and portal instructions are not OS-specific, or clarify when steps differ for Linux.
GitHub Create Pull Request
← Previous Page 10 of 14 Next →