Firewall

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

Bias Trend Over Time

Pages with Bias Issues

120 issues found
Showing 51-75 of 120 flagged pages
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively deploying Windows Server VMs and configuring NAT rules for RDP (a Windows protocol). There are no examples or guidance for deploying Linux VMs or configuring SSH access, which are common requirements for Linux users. Additionally, the only referenced alternative deployment guide is for Azure PowerShell, which is typically Windows-centric.
Recommendations
  • Include examples for deploying Linux virtual machines using azurerm_linux_virtual_machine.
  • Provide sample NAT rules for SSH access to Linux VMs alongside the RDP rules for Windows.
  • Reference equivalent Linux-friendly tools and guides (e.g., Azure CLI, Bash) where PowerShell is mentioned.
  • Add a section or checklist item for creating and managing Linux VM credentials.
  • Ensure that verification and troubleshooting steps include Linux scenarios.
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 06:20
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 reference Windows-specific tools (Remote Desktop, Internet Explorer). There are no Linux or macOS equivalents provided for VM creation, remote access, or browser testing, which may hinder non-Windows users from following the tutorial seamlessly.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu) alongside the Windows example, or as an alternative.
  • Provide guidance for connecting to a Linux VM (e.g., via SSH) and testing firewall rules using cross-platform browsers (e.g., Firefox, Chrome).
  • Mention Linux/macOS remote access tools (SSH, RDP clients) and browser alternatives.
  • Clarify that the firewall configuration applies to any OS, and provide OS-agnostic testing steps.
GitHub Create Pull Request
Firewall Configure customer-controlled maintenance for Azure Firewall ...n/articles/firewall/customer-controlled-maintenance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. The introductory sections and step-by-step instructions focus first on the Azure portal and PowerShell, with PowerShell examples and references appearing before Azure CLI. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, the page does provide Azure CLI instructions, which are cross-platform, and all critical tasks can be completed using CLI. There are no Windows-only tools or patterns, and Linux/macOS users are not blocked from completing the documented procedures.
Recommendations
  • Present Azure CLI examples before PowerShell, or side-by-side, to emphasize cross-platform support.
  • Explicitly mention that Azure CLI is available on Linux/macOS and link to installation guides for those platforms.
  • Add a brief note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell is retained.
  • Ensure screenshots and UI descriptions do not assume a Windows environment (e.g., avoid Windows-specific terminology).
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 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. The example deployment creates only Windows Server virtual machines, with no mention of Linux VM options or examples. While Azure CLI and PowerShell instructions are provided in parallel (which is good cross-platform practice), the exclusive use of Windows VMs in the scenario may alienate Linux/macOS users or those seeking Linux-based test environments.
Recommendations
  • Include Linux VM deployment options in the Bicep file and documentation, or provide an alternative example that uses Linux VMs.
  • Explicitly mention that the Azure CLI commands work on Linux/macOS, and clarify any platform-specific differences if relevant.
  • Add a note or section on how to adapt the scenario for Linux-based jump boxes and servers.
  • Ensure parity in examples and screenshots, showing both Windows and Linux VM configurations where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively deploys Windows Server virtual machines in the example environment, with no mention of Linux VM options or parity. All VM-related Terraform resources and password generation steps are tailored to Windows, and there are no Linux equivalents or alternatives provided. This may create friction for users who prefer or require Linux-based infrastructure.
Recommendations
  • Add instructions and Terraform resource examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
  • Include password generation steps and configuration details relevant to Linux VMs.
  • Mention that the example can be adapted for Linux and provide links or code snippets for Linux VM deployment.
  • Clarify that the firewall and network setup is OS-agnostic, and highlight any differences in configuration for Linux environments.
GitHub Create Pull Request
Firewall Azure Firewall Draft + Deployment (preview) ...azure-docs/blob/main/articles/firewall/draft-deploy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed examples for Azure Portal, Azure CLI, and Azure PowerShell. While the CLI section is cross-platform, the PowerShell section is Windows-centric and presented as a full tab, with extensive cmdlet examples. There is no mention of Linux/macOS-specific tooling (e.g., Bash scripts, automation via shell), and PowerShell is highlighted as a primary automation method, which may create friction for Linux/macOS users. The CLI examples are shown before PowerShell, but PowerShell is still given parity and prominence, and there is no explicit Linux/macOS example or troubleshooting guidance.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for automation tasks.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide troubleshooting tips for those platforms.
  • Mention cross-platform alternatives to PowerShell for users who do not have PowerShell installed.
  • Include a note about installing and using PowerShell Core on Linux/macOS if PowerShell is required.
  • Ensure that any references to downloading or manipulating files (e.g., policy files) include Linux/macOS commands (such as curl, jq, etc.).
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page contains a few instances of Windows bias. Specifically, it references Azure PowerShell cmdlets (e.g., Set-AzFirewallPolicy) as a workaround for updating firewall policy tags, without mentioning equivalent Azure CLI or REST API solutions that are cross-platform. There is also a known issue noting missing PowerShell and CLI support for ICMP, but mitigation steps only mention the portal and REST API, not Linux-specific CLI usage. No Linux/macOS-specific tools or examples are provided, and Windows tooling (PowerShell) is referenced as the primary workaround in at least one case.
Recommendations
  • For every PowerShell example or workaround, provide an equivalent Azure CLI or REST API example, which are cross-platform and work on Linux/macOS.
  • Explicitly mention that Azure CLI can be used on Linux/macOS, and provide sample commands where appropriate.
  • Where PowerShell is referenced as a workaround (e.g., updating tags), add Azure CLI and REST API alternatives.
  • Audit all mitigation steps to ensure Linux/macOS users are not left without guidance or examples.
GitHub Create Pull Request
Firewall Deploy and configure Azure Firewall using Azure CLI ...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 using Windows-based VM images (win2016datacenter), referencing Remote Desktop for access, and providing PowerShell commands for testing. There are no examples or instructions for deploying Linux VMs, connecting via SSH, or testing with Linux tools. This may create friction for Linux/macOS users who wish to follow the tutorial using non-Windows environments.
Recommendations
  • Include parallel examples for deploying Linux VMs (e.g., using Ubuntu images) alongside Windows VM instructions.
  • Provide SSH connection instructions for Linux/macOS users instead of only Remote Desktop steps.
  • Add Linux command-line equivalents for testing firewall rules (e.g., using dig, curl, or wget instead of PowerShell's nslookup and Invoke-WebRequest).
  • Explicitly mention that the Azure CLI commands work cross-platform and highlight any OS-specific considerations.
  • Reorder or parallelize instructions so Windows and Linux approaches are presented equally.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with Availability Zones - Resource Manager template ...re-docs/blob/main/articles/firewall/deploy-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively deploying Windows Server VMs in the example environment and only providing PowerShell instructions for resource cleanup. There are no Linux VM deployment options or Linux/macOS command-line examples (e.g., Azure CLI, Bash) for managing resources, which may hinder Linux/macOS users.
Recommendations
  • Include options in the ARM template and documentation for deploying Linux VMs alongside or instead of Windows Server VMs.
  • Provide cleanup instructions using Azure CLI (az group delete) and Bash, in addition to PowerShell.
  • Explicitly mention that the template can be customized for Linux VMs and link to relevant guidance.
  • Ensure examples and instructions are platform-neutral or offer parity for Linux/macOS 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-11 06:20
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 and instructions use PowerShell syntax, which is most familiar and accessible to Windows users. There are no alternative examples or guidance for Linux/macOS users, and the prerequisite section only references PowerShell installation and usage. The only cross-platform note is the use of the generic 'sftp' command for testing, but even here, the instructions and output are presented in a Windows-centric manner.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all deployment and configuration steps.
  • Include Bash shell examples and instructions for Linux/macOS users.
  • Add a prerequisites section for Linux/macOS, including installation of Azure CLI and authentication steps.
  • Explicitly state that all steps can be performed from Linux/macOS and link to relevant cross-platform documentation.
  • Present examples for both PowerShell and CLI/Bash side-by-side, or allow users to select their preferred platform.
  • Clarify that the 'sftp' command is available on Linux/macOS by default and provide any necessary installation steps for Windows.
GitHub Create Pull Request
Firewall Azure Firewall preview features ...e-docs/blob/main/articles/firewall/firewall-preview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure PowerShell as a configuration method for certain features (e.g., deploying or configuring firewalls), but does not mention or provide equivalent instructions for Linux/macOS users (such as Azure CLI or Bash). There are no explicit examples or guidance for Linux environments, and Windows-centric tooling is referenced exclusively.
Recommendations
  • Include Azure CLI examples alongside Azure PowerShell for all configuration tasks.
  • Explicitly mention cross-platform tools (e.g., Bash, Cloud Shell) where applicable.
  • Add notes or sections clarifying that all features can be managed from Linux/macOS using Azure CLI.
  • Ensure that portal-based instructions do not assume Windows-only environments.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and code samples for enabling Active FTP on Azure Firewall using Azure PowerShell, with PowerShell examples shown first and in greatest detail. While Azure CLI and ARM template methods are mentioned, only PowerShell receives a full code sample, and there are no explicit Linux/macOS shell examples or guidance for non-Windows environments. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Provide equivalent Bash/Azure CLI code samples for all operations currently shown in PowerShell.
  • Explicitly mention that Azure CLI commands work cross-platform and provide sample CLI commands for updating existing firewalls (not just creation).
  • Clarify that ARM template deployment is platform-agnostic and provide instructions for deploying ARM templates from Linux/macOS.
  • Reorder sections so CLI and ARM template instructions are presented before or alongside PowerShell, not after.
  • Add a note that PowerShell is available on Linux/macOS, but CLI is often preferred in those 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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Azure Firewall monitoring data is heavily biased toward Windows environments, particularly in sections about enabling and disabling DNS Flow Trace Logs, Top Flows logs, and Flow Trace logs. All example commands use Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. There are no Linux/macOS-specific instructions or parity examples, and PowerShell is presented as the default tool for configuration tasks.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that configuration can be performed from any OS using Azure CLI, REST API, or portal, and link to relevant guides.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Add notes clarifying that PowerShell examples are not limited to Windows, but also provide installation and usage guidance for PowerShell on Linux/macOS if PowerShell must be used.
  • Include Bash script examples where appropriate, especially for log verification and automation tasks.
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-11 06:20
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, with no equivalent Azure CLI or REST API commands. PowerShell is primarily a Windows tool, and its usage is shown exclusively and first. There are no Linux/macOS-specific instructions or parity for command-line management, which may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (e.g., stopping/starting firewalls, allocating public IPs).
  • Mention that Azure CLI is cross-platform and provide guidance for Linux/macOS users.
  • Consider including REST API or ARM template examples for automation scenarios.
  • Where screenshots are shown, clarify that the Azure portal is web-based and platform-agnostic.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently refers to Windows-centric concepts and tools, such as 'WindowsVirtualDesktop' service tags, Windows 365, Intune, and Microsoft Edge proxy configuration. There are no examples or guidance for Linux/macOS session hosts or alternative browsers. The architecture diagram and terminology reinforce a Windows-first perspective, and proxy configuration is only illustrated with Microsoft Edge, which is primarily a Windows browser.
Recommendations
  • Include explicit guidance and examples for Linux/macOS session hosts, if supported by Azure Virtual Desktop.
  • Provide proxy configuration instructions for common Linux browsers (e.g., Firefox, Chrome) and macOS equivalents.
  • Clarify whether the firewall rules and FQDN tags apply to non-Windows session hosts, or note any limitations.
  • Add references to cross-platform management tools (e.g., Azure CLI, Bash scripts) alongside PowerShell or Windows-specific tools.
  • Ensure terminology and diagrams reflect cross-platform scenarios if Azure Virtual Desktop supports them.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for resource cleanup, omitting equivalent Linux/macOS CLI instructions. The use of the Remove-AzResourceGroup cmdlet is specific to PowerShell, which is primarily a Windows tool, and no az CLI or Bash example is given. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add equivalent az CLI or Bash examples for deleting the resource group, such as 'az group delete --name <your resource group name>'.
  • Where PowerShell is used, provide cross-platform alternatives or clarify platform requirements.
  • Review other steps for implicit Windows assumptions and ensure parity in instructions for Linux/macOS users.
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-11 06:20
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 focusing on RDP connections to Windows Server VMs, referencing Windows-specific tools (Remote Desktop Connection), and omitting Linux/macOS remote access examples. While deployment instructions include both Azure CLI and PowerShell, post-deployment validation and usage are Windows-centric, with no mention of SSH or Linux VM scenarios.
Recommendations
  • Include examples for connecting to Linux VMs via SSH, alongside RDP for Windows VMs.
  • Mention cross-platform remote access tools (e.g., SSH clients, Remmina) in the validation section.
  • Provide sample NAT rules for Linux VM access, not just Windows RDP.
  • Add instructions for cleaning up resources using Azure CLI, not just PowerShell.
GitHub Create Pull Request
Firewall Deploy and configure Azure Firewall Premium ...ure-docs/blob/main/articles/firewall/premium-deploy.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM), instructing users to open an 'administrator command prompt window', and describing browser-based testing only on Windows. There are no examples or instructions for deploying or testing with Linux or macOS VMs, nor guidance for using Linux tools or terminals. The certificate deployment process is described only for Windows, and all interactive steps assume a Windows environment.
Recommendations
  • Add instructions and examples for deploying a Linux-based WorkerVM, including certificate installation steps for Linux.
  • Provide equivalent Linux/macOS command-line instructions (e.g., using bash, terminal, or Linux curl usage).
  • Include browser-based testing steps for Linux/macOS environments.
  • Clarify that the firewall and policy configuration steps are OS-agnostic, and highlight any OS-specific requirements.
  • Offer guidance for users who wish to use Linux or macOS for testing, including troubleshooting tips.
GitHub Create Pull Request
Firewall Azure Firewall prescaling ...s/azure-docs/blob/main/articles/firewall/prescaling.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples for Azure Firewall prescaling using the Azure portal and PowerShell, but omits equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is featured as the only command-line example, and is presented before template-based options (Bicep/ARM), reinforcing a Windows-centric approach.
Recommendations
  • Add Azure CLI examples for prescaling configuration, as CLI is cross-platform and widely used on Linux/macOS.
  • Present command-line examples in parallel (PowerShell and CLI) or lead with CLI for broader accessibility.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS (if true), or clarify platform requirements.
  • Include Bash scripting examples where relevant.
  • Ensure template-based options (Bicep/ARM) are given equal prominence and detail.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell examples for configuring Azure Firewall service tags, with no equivalent Azure CLI or Bash examples. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not the default shell on non-Windows platforms. The configuration section leads with and exclusively uses PowerShell, despite mentioning Azure CLI as a supported option.
Recommendations
  • Add Azure CLI examples for all configuration steps shown in PowerShell.
  • Include Bash or shell script snippets where relevant.
  • Clearly indicate platform-agnostic options and tools.
  • If PowerShell is required, provide installation guidance for Linux/macOS users.
GitHub Create Pull Request
Firewall Quickstart: Create an Azure Firewall with multiple public IP addresses - Resource Manager template ...articles/firewall/quick-create-multiple-ip-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on RDP connections to Windows Server VMs, referencing Azure PowerShell for further deployment instructions, and providing only PowerShell commands for resource cleanup. There are no Linux/macOS-specific examples or guidance, and Linux connection methods (e.g., SSH) are not mentioned.
Recommendations
  • Include examples for connecting to Linux VMs (e.g., SSH) alongside RDP/Windows instructions.
  • Provide equivalent Azure CLI commands for resource group deletion and other operations, not just PowerShell.
  • Reference Linux/macOS tools and workflows where appropriate, such as SSH clients and Azure CLI.
  • Balance examples and terminology to address both Windows and Linux users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides configuration instructions for Azure Firewall with customer-provided public IPs using the Azure Portal and Azure PowerShell only. All CLI examples are in PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-specific workflows. The PowerShell examples are detailed and cover both new and existing deployments, while Linux-friendly alternatives are absent. The documentation implicitly assumes users are on Windows or have access to PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure CLI can be used for these operations and provide links to relevant Azure CLI documentation.
  • Include Bash script examples or guidance for Linux/macOS users where appropriate.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Clarify any platform-specific requirements for the Portal and scripting tools.
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-11 06:20
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 describes testing via Remote Desktop and Internet Explorer, both Windows-specific tools. There are no Linux or macOS examples, nor any mention of deploying a Linux VM or using SSH for connectivity. Windows patterns and tools are presented as the default, with no Linux parity.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Provide SSH-based connectivity examples for Linux/macOS users instead of only RDP.
  • Show how to test firewall rules using Linux tools (e.g., curl, dig) in addition to Internet Explorer.
  • Mention that the procedure works for both Windows and Linux VMs, and clarify any OS-specific steps.
  • Add screenshots or CLI commands relevant to Linux environments where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates the deployment and testing of Azure Firewall using a Windows Server 2019 virtual machine, with instructions for connecting via Remote Desktop and using Microsoft Edge/Internet Explorer. There are no examples or guidance for deploying or testing with Linux or macOS VMs, nor are SSH or Linux-specific connectivity methods mentioned. The only alternative mentioned is a link to a PowerShell-based tutorial, which is also Windows-centric.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet, including relevant configuration steps.
  • Provide examples for connecting to the Linux VM using SSH, including how to test outbound connectivity from a Linux shell.
  • Include browser testing steps for Linux (e.g., using Firefox or Chrome) and command-line tools (e.g., curl, dig) to verify firewall rules.
  • Mention macOS as a supported client for testing, with instructions for connecting to the test VM and verifying firewall behavior.
  • Ensure parity in screenshots and step-by-step instructions for both Windows and Linux/macOS environments.
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-11 06:20
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 demonstrates remote desktop (RDP) connectivity for testing the DNAT rule. There are no instructions or examples for deploying a Linux VM, nor for testing DNAT using Linux-native tools (e.g., SSH). This creates friction for Linux/macOS users who may wish to follow the tutorial with a Linux workload or test connectivity from non-Windows clients.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include examples of configuring DNAT rules for SSH (port 22) in addition to RDP (port 3389).
  • Provide testing steps for Linux/macOS users, such as connecting via SSH from a Linux or macOS client.
  • Clarify that the tutorial is applicable to both Windows and Linux workloads, and highlight any OS-specific considerations.
GitHub Create Pull Request
← Previous Page 3 of 5 Next →