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 26-50 of 120 flagged pages
Firewall FQDN tags overview for Azure Firewall ...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy Examples
Summary
The documentation page demonstrates a Windows bias by focusing examples and explanations on Windows-related services and tags. The majority of FQDN tags listed are for Windows or Microsoft services, and examples reference Windows Update, Windows Diagnostics, Windows Virtual Desktop, Windows 365, and Citrix HDX Plus for Windows 365. There are no explicit Linux/macOS-centric examples, nor is there mention of how Linux users might leverage FQDN tags for non-Windows services. The documentation does not provide parity for Linux/macOS scenarios or reference Linux-specific endpoints.
Recommendations
  • Include examples of FQDN tags relevant to Linux/macOS services, such as Azure Linux VM management, Linux-based Azure Kubernetes Service (AKS), or other open-source workloads.
  • Add a note clarifying that FQDN tags are not limited to Windows services and can be used for any supported Microsoft service, including those used in Linux environments.
  • Provide sample application rules for Linux/macOS scenarios, such as allowing outbound traffic for Linux package repositories or management endpoints.
  • Balance the documentation by mentioning cross-platform use cases and explicitly stating how Linux/macOS administrators can benefit from FQDN tags.
GitHub Create Pull Request
Firewall IP Groups in Azure Firewall ...cs/azure-docs/blob/main/articles/firewall/ip-groups.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While it mentions that IP Groups can be managed via Azure portal, CLI, REST API, and templates, the only explicit command-line tooling examples provided are Azure PowerShell cmdlets. There are no Azure CLI or Linux/macOS shell examples, and the 'devx-track-azurepowershell' custom tag further emphasizes PowerShell. The PowerShell section is the only one with direct links to command references, and it appears before any mention of CLI or REST API usage.
Recommendations
  • Add explicit Azure CLI examples and command references for creating, managing, and deleting IP Groups.
  • Include Linux/macOS shell usage patterns where relevant, especially for bulk operations or scripting.
  • Balance the 'Related Azure PowerShell cmdlets' section with an equivalent 'Related Azure CLI commands' section.
  • Ensure that cross-platform tooling is mentioned and linked with equal prominence.
  • Clarify that PowerShell is available cross-platform, but also highlight native Linux/macOS alternatives.
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-12 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 exclusively providing Azure PowerShell command examples for enabling and disabling logging features (DNS Flow Trace Logs, Top Flows Logs, Flow Trace Logs) and for resource provider registration. There are no equivalent instructions or examples for Linux/macOS users, such as Azure CLI or REST API commands. The repeated use of PowerShell commands and lack of cross-platform alternatives may create friction for users who do not have access to PowerShell or prefer other tools.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell command examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API or ARM template examples for enabling/disabling features, which are platform-agnostic.
  • Add notes or sections clarifying that all operations can be performed from any OS using CLI or API, not just PowerShell.
  • Consider reordering examples so that cross-platform tools (CLI, API) are shown first or alongside PowerShell.
  • Explicitly mention that PowerShell is available on Linux/macOS, if relevant, and provide installation guidance if PowerShell remains the only option.
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-12 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 page provides only Azure PowerShell examples for managing the Azure Firewall Management NIC, with no equivalent Azure CLI (cross-platform) or Bash examples. All command-line instructions use PowerShell cmdlets, which are native to Windows and less commonly used on Linux/macOS. There is no mention of Linux/macOS tooling or alternative workflows, and Windows-centric tools are referenced exclusively and before any cross-platform options.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line steps, ensuring Linux/macOS users can follow the instructions without needing PowerShell.
  • Explicitly mention that the Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is cross-platform, and note any platform-specific differences if applicable.
  • Consider a 'Platform Parity' section or callout to reassure non-Windows users that all steps can be completed on their OS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM) for all hands-on steps, such as running curl commands and browser tests. There are no instructions or examples for deploying or testing with a Linux VM, nor guidance for Linux-specific certificate installation or browser usage. All interactive steps assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Provide parallel instructions for deploying a Linux-based WorkerVM, including guidance on certificate installation and browser usage.
  • Include Linux/macOS-specific curl command syntax and troubleshooting tips.
  • Clarify that the firewall features and testing steps are OS-agnostic, and explicitly mention support for Linux/macOS clients.
  • Add screenshots or examples from Linux environments where applicable.
GitHub Create Pull Request
Firewall Azure Firewall prescaling ...s/azure-docs/blob/main/articles/firewall/prescaling.md
Medium Priority View Details →
Scanned: 2026-01-12 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 prescaling but does not include equivalent examples for Linux/macOS users (such as Azure CLI or Bash). PowerShell is a Windows-centric tool, and its example is presented before any mention of Linux-friendly alternatives. This creates friction for users on non-Windows platforms who may not use PowerShell.
Recommendations
  • Add Azure CLI (az) example for configuring prescaling, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that ARM templates and Bicep can be deployed from any OS, and provide command-line deployment examples using Azure CLI.
  • If PowerShell is retained, clarify that Azure PowerShell is available cross-platform, but still provide CLI/Bash alternatives for parity.
  • Consider ordering examples so that cross-platform tools (Azure CLI, ARM/Bicep) are presented before or alongside PowerShell.
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-12 00:00
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, tools, and service tags (e.g., 'WindowsVirtualDesktop'), and examples such as configuring Microsoft Edge proxy settings. There are no Linux/macOS-specific instructions, examples, or references, despite Azure Virtual Desktop supporting non-Windows clients and potential Linux session hosts. Windows terminology and tools are mentioned exclusively or first, and Linux alternatives are missing.
Recommendations
  • Include examples and instructions for configuring outbound access and proxy settings on Linux/macOS session hosts and clients.
  • Reference cross-platform tools and browsers (e.g., Firefox, Chrome) and provide proxy configuration examples for those.
  • Clarify whether the guidance applies only to Windows session hosts or also to Linux/macOS hosts, and provide parity where possible.
  • Mention Linux/macOS equivalents for service tags, firewall rules, and deployment templates if available.
  • Add a section or note addressing Linux/macOS users and their specific requirements or differences.
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-12 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 deleting resources, omitting equivalent Linux/macOS CLI commands. The use of the Remove-AzResourceGroup cmdlet is Windows/PowerShell-centric, and there are no Bash/Azure CLI examples or references for Linux/macOS users. This creates friction for non-Windows users, especially in the cleanup step.
Recommendations
  • Add Azure CLI (az group delete) and Bash examples alongside PowerShell for resource group deletion.
  • Explicitly mention cross-platform options for managing resources, such as Azure CLI and Cloud Shell.
  • Ensure all command-line instructions are provided for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) environments.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on RDP connections to Windows Server VMs and referencing Windows tools (Remote Desktop Connection) for validation. There are no Linux VM deployment examples, nor are SSH or Linux remote access methods mentioned. The cleanup section only provides PowerShell commands, omitting Azure CLI equivalents for Linux/macOS users.
Recommendations
  • Include examples for deploying and connecting to Linux VMs (e.g., SSH access) alongside Windows examples.
  • Mention Linux/macOS remote access tools (e.g., SSH clients) in the validation section.
  • Provide Azure CLI commands for resource cleanup, not just PowerShell.
  • Clarify that the Bicep template can be used for both Windows and Linux VMs, or provide separate templates/examples.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits Windows bias by focusing on RDP connections to Windows Server VMs, referencing Azure PowerShell for further deployment instructions, and only providing PowerShell commands for resource cleanup. There are no Linux/macOS-specific examples or mentions of SSH connectivity, and Windows tools/patterns (RDP, PowerShell) are presented exclusively.
Recommendations
  • Include examples for connecting to Linux VMs via SSH, alongside RDP for Windows VMs.
  • Provide equivalent Azure CLI commands for resource group deletion and other operations, not just PowerShell.
  • Reference documentation for deploying Azure Firewall with multiple public IPs using Azure CLI and/or Bash.
  • Clarify that the template can deploy Linux VMs and provide instructions for those scenarios.
  • Mention cross-platform tools and patterns (e.g., SSH, Azure CLI) in parallel with Windows-specific ones.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on deploying Windows Server VMs and enabling RDP access, with no mention of Linux VM deployment or SSH access. The only VM examples are Windows, and the NAT rules are for RDP, a Windows-specific protocol. There are no Linux VM or SSH examples, nor guidance for Linux/macOS users in the verification or usage steps.
Recommendations
  • Add parallel examples for deploying Linux VMs (e.g., using azurerm_linux_virtual_machine) alongside Windows VM examples.
  • Include NAT rule examples for SSH (port 22) access to Linux VMs, not just RDP for Windows.
  • Provide sample code and verification steps for Linux VM scenarios.
  • Mention SSH key generation and usage for Linux/macOS users.
  • Ensure troubleshooting and verification sections address both Windows and Linux VM access patterns.
GitHub Create Pull Request
Firewall Azure Firewall SNAT private IP address ranges ...docs/blob/main/articles/firewall/snat-private-range.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides configuration examples for Azure Firewall SNAT private IP address ranges using Azure PowerShell, Azure CLI, ARM templates, and the Azure portal. While Azure CLI and ARM template methods are cross-platform, the documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before CLI equivalents and provides more detailed PowerShell walkthroughs. There are no Linux/macOS-specific shell examples, and PowerShell is emphasized throughout, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell examples to emphasize cross-platform support.
  • Add explicit bash/shell script examples for Linux/macOS users where applicable.
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, while PowerShell is primarily Windows-centric (though available cross-platform).
  • Balance the level of detail between PowerShell and CLI sections, ensuring parity in explanations and troubleshooting notes.
  • Consider adding a table or section summarizing platform compatibility for each method.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed configuration steps exclusively using Azure PowerShell, which is most commonly used on Windows. There are no examples for Azure CLI (cross-platform) or Bash, and PowerShell instructions are presented first and solely. This creates friction for Linux/macOS users who may prefer or require CLI or Bash-based workflows.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps.
  • Explicitly mention that Azure CLI and portal are supported, and provide links or brief instructions.
  • Consider including Bash or shell script snippets for common tasks.
  • Reorder examples so that cross-platform tools (Azure CLI) are shown first or alongside PowerShell.
GitHub Create Pull Request
Firewall Azure Firewall threat intelligence based filtering ...azure-docs/blob/main/articles/firewall/threat-intel.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a hosts file modification example specifically for Windows, referencing the Windows file path and omitting equivalent instructions for Linux or macOS users. This creates a subtle bias by prioritizing Windows and not offering parity for other platforms.
Recommendations
  • Add instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
  • Present platform-specific examples side-by-side or note the differences explicitly.
  • Avoid referencing only Windows file paths; use generic language or include all major OSes.
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-12 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 virtual machine and only describes connecting via Remote Desktop (RDP) and using Internet Explorer for testing. There are no instructions or examples for deploying a Linux VM, connecting via SSH, or using Linux tools/browsers to test firewall rules. The documentation also refers to Windows-specific patterns (RDP, Internet Explorer) without mentioning Linux/macOS equivalents.
Recommendations
  • Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the test subnet.
  • Include examples for connecting to the Linux VM using SSH, and for testing outbound connectivity using Linux command-line tools (e.g., curl, wget, dig).
  • Show how to test firewall rules from a Linux VM, including DNS resolution and HTTP/HTTPS access.
  • Mention macOS as a supported platform for client connectivity and testing.
  • Where possible, use cross-platform terminology (e.g., 'connect to the VM using RDP or SSH depending on OS').
GitHub Create Pull Request
Firewall Tutorial: Deploy Azure Firewall private IP DNAT for overlapped and nonroutable networks ...lob/main/articles/firewall/tutorial-private-ip-dnat.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides PowerShell scripts for configuring virtual machines, assumes Windows-based VMs (e.g., win-vm-2, win-vm-3), and does not mention or provide equivalent instructions for Linux VMs. All configuration and testing steps are shown using Windows tools and patterns, with no Linux or cross-platform alternatives. This creates friction for users deploying Linux-based workloads or managing Linux VMs in Azure.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux VMs, including download and execution instructions.
  • Explicitly mention support for Linux VMs and clarify any differences in DNAT rule testing or configuration.
  • Include cross-platform guidance for connecting to VMs (e.g., SSH for Linux, RDP for Windows).
  • List both Windows and Linux VM setup steps in parallel, or provide a table comparing commands.
  • Reference Linux troubleshooting tools (e.g., tcpdump, netcat) for DNAT validation.
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-12 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. All instructions for VM creation, remote access, and firewall rule testing are tailored to Windows (e.g., using RDP and Internet Explorer), with no mention of Linux or macOS alternatives. There are no examples for deploying a Linux VM, connecting via SSH, or testing with Linux tools.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include guidance for connecting to the Linux VM using SSH, including firewall rule configuration for port 22.
  • Provide Linux/macOS-specific testing steps, such as using curl or wget to verify outbound access.
  • Mention cross-platform browsers (e.g., Firefox, Chrome) for testing, rather than only Internet Explorer.
  • Clarify that the firewall and DDoS protection features are OS-agnostic, and provide examples for both Windows and Linux environments.
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-12 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, with no mention of Linux or macOS alternatives. All testing instructions (e.g., remote desktop, browser usage) assume Windows tools and workflows, and there are no Linux VM creation steps or SSH-based access examples. While the main configuration is via the Azure portal (which is cross-platform), the practical validation and VM setup are Windows-centric.
Recommendations
  • Include instructions for creating a Linux VM (e.g., Ubuntu) in the workload subnet, alongside or instead of Windows Server.
  • Provide testing steps using SSH (for Linux/macOS) and browser access from Linux VMs.
  • Mention alternative remote access methods (e.g., SSH, RDP clients for Linux/macOS) and clarify how to test firewall rules from non-Windows environments.
  • Add screenshots or CLI snippets for Linux VM creation and access.
  • Explicitly state that the tutorial is applicable to both Windows and Linux workloads, and highlight any OS-specific considerations.
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-12 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 only describes connecting via Remote Desktop (RDP), a Windows-centric protocol. There are no instructions or examples for deploying a Linux VM, nor for connecting via SSH or other Linux/macOS-friendly methods. 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.
  • Include steps for configuring DNAT rules for SSH (port 22) access to a Linux VM.
  • Provide testing instructions for connecting to the Linux VM via SSH from a remote client (including command-line examples for Windows, Linux, and macOS).
  • Clarify that the firewall DNAT configuration supports both RDP and SSH (and other protocols), and show examples for each.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively uses Windows Server as the example workload VM and tests DNAT using Remote Desktop Protocol (RDP) to port 3389, which is a Windows-centric scenario. There are no Linux VM deployment instructions, nor examples of connecting to a Linux VM (e.g., via SSH). This creates friction for Linux/macOS users who may want to use Linux workloads or test DNAT with non-Windows protocols.
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) to a Linux VM.
  • Provide testing steps for connecting to a Linux VM using SSH from a Linux/macOS client.
  • Clarify that the procedure applies to both Windows and Linux workloads, and mention protocol/port differences.
  • Consider showing both Windows and Linux examples side-by-side where relevant.
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-12 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 instructions for configuring the workload (IIS installation) use PowerShell commands. There are no examples or guidance for deploying Linux VMs, nor for configuring equivalent Linux services (such as Apache or Nginx). The Cloud Shell instructions default to PowerShell, and all remote access examples use RDP, which is Windows-specific. No Linux/macOS alternatives (e.g., SSH, Bash, Linux VM images) are mentioned.
Recommendations
  • Include parallel instructions for creating Linux-based virtual machines (e.g., Ubuntu, CentOS) in both spoke and on-premises roles.
  • Provide examples for installing and configuring a web server on Linux (e.g., using Bash to install Apache or Nginx).
  • Add guidance for connecting to Linux VMs using SSH, and for testing connectivity via Linux-native tools.
  • Ensure Cloud Shell instructions mention Bash as an alternative to PowerShell.
  • When listing VM images, present both Windows and Linux options, or offer a choice.
  • Clarify that RDP is for Windows and suggest SSH for Linux remote access.
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 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 workload VM and only describes connecting via Remote Desktop (RDP) and testing with Internet Explorer. There are no Linux VM deployment instructions, nor any Linux/macOS client testing steps (e.g., SSH, browser alternatives). This creates friction for 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 (e.g., SSH via DNAT rule for port 22) and testing outbound connectivity using Linux tools (curl, wget, Firefox, etc.).
  • Mention browser alternatives for testing (e.g., Firefox, Chrome) and clarify that the firewall rules apply regardless of OS.
  • Explicitly state that the procedure works for both Windows and Linux VMs, and provide links to relevant Azure Linux VM documentation.
GitHub Create Pull Request
Firewall Deploy Azure Firewall with Availability Zones ...ticles/firewall/deploy-availability-zone-powershell.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 only Azure PowerShell examples for deploying Azure Firewall with Availability Zones, with no equivalent CLI (az), Bash, or Linux-native instructions. The use of PowerShell as the sole example and the lack of cross-platform command-line alternatives creates friction for Linux/macOS users.
Recommendations
  • Add Azure CLI (az) examples for deploying Azure Firewall with Availability Zones.
  • Include Bash or shell script equivalents where possible.
  • Explicitly mention that Azure PowerShell is available cross-platform, but provide CLI alternatives for users who prefer native Linux/macOS tools.
  • Reorder examples to present CLI and PowerShell side-by-side or in parallel sections.
GitHub Create Pull Request
Firewall IP Groups in Azure Firewall ...cs/azure-docs/blob/main/articles/firewall/ip-groups.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 page demonstrates a moderate Windows bias, primarily through its emphasis on Azure PowerShell cmdlets and references to PowerShell as a management tool. The 'Related Azure PowerShell cmdlets' section lists only PowerShell commands, with no equivalent Azure CLI or REST API examples provided. Additionally, metadata and custom tags reference Azure PowerShell, suggesting a Windows-centric approach. While the page mentions that IP Groups can be managed via Azure CLI and REST API, it does not provide examples or links for these methods, nor does it mention Linux/macOS-specific guidance.
Recommendations
  • Add equivalent Azure CLI examples for creating, managing, and deleting IP Groups.
  • Include REST API sample requests for IP Group operations.
  • Present CLI and REST API options before or alongside PowerShell to avoid Windows-first ordering.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users.
  • Update metadata and custom tags to reflect CLI and REST API parity.
GitHub Create Pull Request
Firewall Azure Firewall threat intelligence based filtering ...azure-docs/blob/main/articles/firewall/threat-intel.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a hosts file modification example only for Windows (specifically referencing the Windows file path), with no mention of how to perform the equivalent operation on Linux or macOS. This creates friction for non-Windows users attempting to follow the testing instructions.
Recommendations
  • Include equivalent hosts file modification instructions for Linux (e.g., /etc/hosts) and macOS.
  • Present platform-agnostic instructions or mention all major OSes when giving file path examples.
  • Add notes clarifying any OS-specific steps or differences.
GitHub Create Pull Request
← Previous Page 2 of 5 Next →