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 126-150 of 332 flagged pages
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall-reference.md ...b/main/articles/firewall/monitor-firewall-reference.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias in its operational examples and tooling. All command-line instructions for enabling/disabling and configuring logs (DNS Flow Trace, Top Flows, Flow Trace) are provided exclusively using Azure PowerShell, which is most commonly used on Windows and is not the default on Linux. There are no equivalent examples for Azure CLI, Bash, or other Linux-native tools. The documentation does not mention or prioritize Linux-compatible methods, nor does it provide parity for Linux administrators. This may hinder users who manage Azure resources from Linux environments.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or PowerShell Core, and provide guidance for both environments.
  • Add Bash script examples where appropriate, especially for tasks like log configuration and verification.
  • Include a section or notes on platform compatibility, clarifying which commands/tools work on Windows, Linux, and macOS.
  • Where GUI steps are described, clarify that the Azure Portal is accessible from any OS/browser.
  • Review and update reusable content includes to ensure they do not reinforce Windows-first patterns.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat.md .../blob/main/articles/firewall/tutorial-firewall-dnat.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the example workload VM, only referencing Remote Desktop (RDP) for connectivity testing (a Windows-centric protocol), and omitting any Linux VM deployment or SSH-based testing instructions. There are no Linux-specific tools, patterns, or examples provided, and Windows is presented as the default/only option for readers.
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 22 in the NAT rule and using an SSH client.
  • Mention Linux tools and connectivity patterns (e.g., OpenSSH, SCP) alongside Windows tools like RDP.
  • Where VM OS selection is described, present Windows and Linux options equally, or reference both in the instructions.
  • Add troubleshooting and verification steps for both Windows (RDP) and Linux (SSH) scenarios.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/service-tags.md ...azure-docs/blob/main/articles/firewall/service-tags.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for configuring Azure Firewall service tags. There are no Azure CLI (cross-platform) or Bash/Linux shell examples, and the configuration section exclusively uses PowerShell commands and patterns, which are native to Windows environments. The mention of 'devx-track-azurepowershell' in metadata further emphasizes the Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, using Bash syntax where appropriate.
  • Explicitly mention that Azure CLI can be used from Linux, macOS, and Windows, and provide links to CLI documentation.
  • Reorder or parallelize example sections so that CLI and PowerShell instructions are presented together, rather than PowerShell first.
  • Include notes or examples for configuring Azure Firewall service tags via the Azure portal, which is platform-agnostic.
  • Review metadata and custom tags to ensure cross-platform tooling is represented (e.g., 'devx-track-azurecli').
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy.md ...ure-docs/blob/main/articles/firewall/premium-deploy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM) for all deployment and testing steps. All instructions for running test commands (e.g., curl) and browser-based validation are performed on a Windows VM, with no mention of Linux alternatives. The deployment template generates and installs certificates specifically on a Windows VM, and connection instructions reference Azure Bastion for connecting to the Windows machine. There are no examples or guidance for deploying or testing with a Linux VM, nor instructions for certificate installation or browser testing on Linux.
Recommendations
  • Include parallel instructions for deploying and configuring a Linux test VM (e.g., Ubuntu) alongside the Windows VM.
  • Provide guidance for installing the derived Intermediate CA certificate on common Linux distributions, including both CLI and GUI methods.
  • Show how to run curl and browser-based tests from a Linux VM, noting any differences in command syntax or certificate handling.
  • Reference Linux-compatible remote access tools (e.g., SSH via Azure Bastion) and provide connection instructions.
  • Ensure all test scenarios (IDPS, TLS Inspection, URL filtering, Web categories) include Linux-specific steps and troubleshooting notes.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal-policy.md ...ain/articles/firewall/tutorial-hybrid-portal-policy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a strong Windows bias. All virtual machine examples use Windows Server 2019 Datacenter, with no mention of Linux alternatives. The IIS installation is performed via PowerShell, and the Cloud Shell instructions default to PowerShell. RDP (a Windows protocol) is used for connectivity tests, and all VM extension examples use Windows-centric tooling. There are no Linux VM examples, nor are SSH or Linux-based web server scenarios covered.
Recommendations
  • Include parallel instructions for deploying Linux-based virtual machines (e.g., Ubuntu) in both the spoke and on-premises networks.
  • Provide examples for installing and testing a Linux web server (e.g., Apache or Nginx) using Bash in Cloud Shell.
  • Add SSH connectivity tests alongside RDP, demonstrating firewall rules for SSH (port 22) and Linux VM access.
  • Show how to install required software (e.g., Apache) on Linux VMs using Bash scripts or Azure CLI.
  • When referencing Cloud Shell, mention both Bash and PowerShell options, and provide equivalent commands for each.
  • Ensure screenshots and walkthroughs include both Windows and Linux VM scenarios, where applicable.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/sql-fqdn-filtering.md ...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration instructions using Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the PowerShell example is Windows-centric and detailed, and there is no explicit mention or example of Linux-specific tools, shell environments, or usage patterns. The CLI section does not clarify Linux usage or provide bash-specific guidance, and the PowerShell section may imply a Windows-first approach. No Linux shell or scripting examples are given, and there is no discussion of Linux-specific considerations.
Recommendations
  • Add explicit bash/Linux shell examples for Azure CLI usage, including command syntax and environment notes.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux issues (e.g., authentication, environment variables).
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux and macOS, and provide example commands for those platforms.
  • Include a section or note on Linux-specific firewall management patterns or tools, if relevant.
  • Ensure parity in detail and troubleshooting between Windows and Linux instructions.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/protect-azure-virtual-desktop.md ...ain/articles/firewall/protect-azure-virtual-desktop.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by consistently referencing Windows-specific services, tags, and tools (e.g., 'WindowsVirtualDesktop' service tag, Microsoft Edge proxy configuration), and by omitting Linux-specific examples or guidance. All examples and terminology are tailored to Windows environments, with no mention of Linux session hosts or cross-platform considerations.
Recommendations
  • Include explicit guidance for Linux session hosts in Azure Virtual Desktop, such as required FQDNs/endpoints, firewall rules, and any differences in configuration.
  • Provide proxy configuration examples for popular Linux browsers (e.g., Firefox, Chromium) and command-line tools, not just Microsoft Edge.
  • Clarify whether the 'WindowsVirtualDesktop' service tag and related rules apply to Linux hosts, or provide equivalent tags/instructions for Linux.
  • Add notes or sections addressing cross-platform deployment scenarios, highlighting any platform-specific requirements or limitations.
  • Ensure that references to tools and configuration steps are not exclusively Windows-centric, and offer Linux alternatives where applicable.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-template.md ...articles/firewall/quick-create-multiple-ip-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows Server virtual machines (with RDP access), referencing Windows-centric tools (Remote Desktop Connection), and providing only PowerShell examples for resource cleanup. There are no Linux VM deployment examples, nor are SSH or Linux command-line tools mentioned. The documentation assumes Windows as the default platform for both deployment and management tasks.
Recommendations
  • Include examples for deploying Linux virtual machines alongside or instead of Windows Server VMs.
  • Provide instructions for connecting to Linux VMs using SSH, and mention relevant Linux tools (e.g., OpenSSH, terminal commands).
  • Add resource cleanup instructions using Azure CLI (az group delete) and Bash shell examples for Linux users.
  • Balance references to Windows and Linux tools in both deployment and management sections.
  • Explicitly state that the firewall can be used to protect both Windows and Linux workloads, and provide parity in documentation.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/secured-hub-customer-public-ip.md ...in/articles/firewall/secured-hub-customer-public-ip.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing configuration examples using Azure PowerShell cmdlets, which are most commonly used on Windows. There are no CLI (az), Bash, or Linux-native instructions, and the only automation example is PowerShell. The mention of configuration options lists 'Azure portal or Azure PowerShell', omitting Azure CLI or ARM template methods, which are platform-agnostic and widely used on Linux/macOS. This prioritizes Windows tools and patterns, leaving Linux users without direct guidance.
Recommendations
  • Add equivalent Azure CLI (az) examples for all configuration steps, as CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets where appropriate, especially for automation scenarios.
  • Mention ARM template or Bicep deployment options for infrastructure-as-code parity.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant cross-platform tooling documentation.
  • Reorder configuration options to list platform-agnostic tools (Azure CLI, ARM templates) before Windows-specific ones (PowerShell).
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/management-nic.md ...ure-docs/blob/main/articles/firewall/management-nic.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 managing the Azure Firewall Management NIC, with no mention of Azure CLI (cross-platform) or ARM/Bicep templates. All command-line automation is shown using PowerShell cmdlets, which are most familiar to Windows users. There are no Linux/Unix shell or Azure CLI equivalents, and the documentation implicitly assumes a Windows-centric workflow.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Mention that both Azure PowerShell and Azure CLI can be used, and provide links to both sets of documentation.
  • Where possible, provide ARM/Bicep template snippets for infrastructure-as-code scenarios, which are platform-agnostic.
  • Ensure screenshots and portal instructions do not assume a particular OS, and clarify that all steps can be performed from any supported OS.
  • Consider the order of presentation: introduce cross-platform tools (Azure CLI, ARM/Bicep) before or alongside PowerShell to avoid the impression that Windows tools are preferred.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/easy-upgrade.md ...azure-docs/blob/main/articles/firewall/easy-upgrade.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation mentions PowerShell as a supported automation method for upgrading/downgrading Azure Firewall SKUs, but does not mention Azure CLI or provide Linux/Unix-oriented examples. The order of mention (PowerShell before Terraform) and lack of Linux-native tooling or examples suggest a Windows-first and PowerShell-heavy bias.
Recommendations
  • Explicitly mention Azure CLI as a supported method for performing upgrades/downgrades, if available.
  • Provide example commands for both PowerShell and Azure CLI to ensure parity for Linux and cross-platform users.
  • List automation options in a neutral order (e.g., Azure CLI, PowerShell, Terraform) or group them by platform.
  • Include screenshots or walkthroughs for both Windows (PowerShell) and Linux (Azure CLI) environments.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/explicit-proxy.md ...ure-docs/blob/main/articles/firewall/explicit-proxy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references Azure PowerShell for deployment guidance and does not mention or provide examples for Linux tools or CLI equivalents. There are no Linux-specific instructions or examples, and the only deployment link points to a PowerShell-based guide, suggesting a Windows-centric approach.
Recommendations
  • Include equivalent deployment instructions using Azure CLI (az) and Bash, not just Azure PowerShell.
  • Provide examples or references for configuring proxy settings on popular Linux browsers and applications.
  • Add guidance for uploading PAC files using Linux tools (e.g., azcopy, Azure CLI) in addition to any Windows-based methods.
  • Ensure that any screenshots or walkthroughs are platform-agnostic or show both Windows and Linux environments where relevant.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-known-issues.md ...s/blob/main/articles/firewall/firewall-known-issues.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell cmdlets as the primary or sole method for certain operations (e.g., updating firewall policy tags), and by mentioning PowerShell/CLI support limitations without clarifying Linux parity or providing Linux-native alternatives. There are no Linux-specific tools, commands, or examples provided, and the documentation assumes familiarity with Windows-centric tooling.
Recommendations
  • For every mention of Azure PowerShell, also provide equivalent Azure CLI commands and examples, ensuring that Linux users have clear guidance.
  • Where PowerShell is referenced as a workaround (e.g., updating tags), explicitly state if Azure CLI or REST API can also be used, and provide those examples.
  • Include Linux-specific troubleshooting steps or examples where relevant, especially in sections discussing command-line operations.
  • Review all mitigation steps and ensure that they are platform-agnostic or provide both Windows and Linux approaches.
  • Where a feature is missing in PowerShell and CLI, clarify if this affects both Windows and Linux users equally, and provide REST API examples if available.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-template.md ...ain/articles/firewall/quick-create-ipgroup-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell (Windows-centric) example for cleaning up resources, with no equivalent Bash, Azure CLI, or Linux-native instructions. The use of the Remove-AzResourceGroup cmdlet assumes a Windows or PowerShell environment, and there are no Linux or cross-platform alternatives presented. The rest of the quickstart relies on the Azure Portal, which is platform-agnostic, but the only command-line example is Windows-focused.
Recommendations
  • Add equivalent Azure CLI (az group delete) and Bash examples for deleting the resource group, ensuring Linux and macOS users are supported.
  • Wherever PowerShell cmdlets are shown, provide parallel instructions for Azure CLI and Bash.
  • Explicitly mention that the Azure Portal steps are platform-agnostic, but provide command-line options for all major platforms.
  • Review other sections for any implicit Windows tool references and ensure parity with Linux-native tools and workflows.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat.md .../blob/main/articles/firewall/tutorial-firewall-dnat.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the example workload VM, referencing RDP (port 3389) for connectivity testing, and omitting any Linux-based VM or SSH-based test scenario. No Linux equivalents or instructions are provided, and Windows is presented as the default/only platform for deployment and validation.
Recommendations
  • Include parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet.
  • Provide examples for configuring DNAT rules for SSH (port 22) access to a Linux VM, alongside the RDP/Windows example.
  • In the 'Test the firewall' section, add steps for connecting via SSH to a Linux VM using the firewall's public IP address.
  • Present both Windows and Linux options side-by-side or in separate sections, ensuring neither is prioritized over the other.
  • Mention Linux tools (e.g., SSH clients) and patterns where relevant, not just Windows/Remote Desktop.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-template.md ...re-docs/blob/main/articles/firewall/deploy-template.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the example environment, mentioning only Windows VMs (jump box and server) and omitting Linux VM options. Additionally, the only command-line example for resource cleanup uses PowerShell (`Remove-AzResourceGroup`), with no equivalent Bash/Azure CLI example provided. No Linux tools, patterns, or examples are mentioned.
Recommendations
  • Include examples that deploy both Windows and Linux virtual machines, or provide an option to select the OS type in the template or instructions.
  • When providing command-line instructions (such as for resource cleanup), include both PowerShell and Bash/Azure CLI equivalents.
  • Mention Linux as a supported platform for jump box/server VMs, and provide guidance or links for deploying and managing Linux VMs in Azure.
  • Ensure that any references to tools or scripts (e.g., PowerShell) are accompanied by cross-platform alternatives where possible.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/dns-settings.md ...azure-docs/blob/main/articles/firewall/dns-settings.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Azure Firewall DNS settings, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. There are no Linux shell-specific examples (e.g., Bash scripts), and PowerShell is referenced as a primary automation tool, which may bias the documentation toward Windows users. The use of 'devx-track-azurepowershell' in metadata and the explicit PowerShell tabs reinforce this bias. No Linux-specific tools or guidance are provided.
Recommendations
  • Add Bash shell script examples alongside PowerShell, especially for common Linux automation scenarios.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide explicit Bash usage examples where appropriate.
  • Include references to Linux-native tools (such as curl, dig, or resolvectl) for DNS troubleshooting or verification.
  • Ensure that PowerShell is not presented as the default or primary automation tool; instead, present CLI and Bash examples first or in parallel.
  • Review metadata and custom tags to ensure they do not overemphasize PowerShell or Windows-specific tooling.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/customer-controlled-maintenance.md ...n/articles/firewall/customer-controlled-maintenance.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting PowerShell instructions before Azure CLI, emphasizing PowerShell (a Windows-centric tool), and omitting any Linux-specific guidance or examples. The Azure portal and PowerShell are highlighted as primary configuration methods, with no mention of Linux shell scripting, Bash, or cross-platform automation patterns. The CLI section is present, but only after PowerShell, and there is no discussion of Linux-specific considerations or troubleshooting.
Recommendations
  • Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any relevant Linux-specific notes (e.g., shell syntax, environment variables).
  • Include Bash scripting examples for automation, or reference how to use these commands in Linux shell scripts.
  • If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, but also highlight that Azure CLI is the preferred tool for Linux environments.
  • Add troubleshooting tips or environment setup notes for Linux users (e.g., installing Azure CLI on Ubuntu, handling authentication).
  • Avoid phrasing that implies PowerShell is the default or primary automation tool for all users.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/fqdn-tags.md ...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing heavily on Windows-related FQDN tags (e.g., WindowsUpdate, WindowsDiagnostics, WindowsVirtualDesktop, Windows365, citrixHdxPlusForWindows365) and providing examples and descriptions that are almost exclusively centered on Windows or Microsoft-specific services. There are no Linux-specific examples, tags, or references to non-Windows environments, and the documentation does not mention how FQDN tags might be used for Linux-based services or scenarios.
Recommendations
  • Include examples or references for Linux-based services that might benefit from FQDN tags, such as popular Linux distributions' update servers or open-source cloud services.
  • Add FQDN tags or documentation for non-Windows Microsoft services (e.g., Azure Linux VM management endpoints, Azure Container Instances, etc.).
  • Provide parity in documentation by mentioning both Windows and Linux scenarios where relevant, or clarify if FQDN tags are only applicable to Microsoft/Windows services.
  • If possible, add a note explaining the scope of FQDN tags and whether support for Linux/open-source services is planned or available.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-preview.md ...e-docs/blob/main/articles/firewall/firewall-preview.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Azure PowerShell as a configuration method for certain features (e.g., associating public IP addresses in secured hubs) without mentioning Azure CLI or providing Linux/Unix-specific instructions. There are no Linux-specific tools or examples, and the only command-line tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Include Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and commonly used on Linux.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for configuration, and provide links or examples for both.
  • Where possible, avoid referencing only Windows-centric tools (like PowerShell) and ensure parity by including Linux-friendly alternatives.
  • Add a note clarifying that all features can be managed from Linux, macOS, and Windows using the Azure CLI, and provide relevant documentation links.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ftp-support.md .../azure-docs/blob/main/articles/firewall/ftp-support.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and references before Azure CLI or ARM template instructions. There are no explicit Linux shell or cross-platform examples, and the PowerShell workflow is described in more detail, including update steps, while the CLI and ARM template sections are brief. The focus on PowerShell as the primary example and lack of Linux-native command-line (e.g., Bash) or cross-platform scripting guidance may disadvantage Linux users.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for all operations, including updating an existing Azure Firewall (not just deployment).
  • Ensure that Azure CLI instructions are as detailed as the PowerShell ones, including update scenarios.
  • Present CLI and ARM template examples before or alongside PowerShell to avoid the perception of Windows-first bias.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample shell commands.
  • Where possible, include screenshots or code blocks that demonstrate the use of CLI in a Linux shell environment.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal-policy.md ...ain/articles/firewall/tutorial-hybrid-portal-policy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server for all virtual machine examples, providing only PowerShell commands for configuration (specifically for IIS installation), and omitting any Linux-based examples or CLI alternatives. The workflow assumes Windows administrative patterns and tools, such as RDP and PowerShell, without mentioning or providing parity for Linux users (e.g., SSH, Bash, Linux VMs, or Azure CLI).
Recommendations
  • Provide parallel instructions for deploying and configuring Linux-based virtual machines (e.g., Ubuntu Server) in both the spoke and on-premises roles.
  • Include Azure CLI and/or Bash script examples for tasks such as installing web servers (e.g., using apt to install nginx or apache2) in addition to the PowerShell/IIS example.
  • Demonstrate how to connect to Linux VMs using SSH, and how to test connectivity (e.g., using curl or wget) instead of only RDP and browser-based testing.
  • When referencing remote desktop access, mention alternatives for Linux (e.g., SSH, xrdp, or other remote access tools).
  • Ensure that all code snippets and configuration steps have both Windows and Linux equivalents, and present them side-by-side or with clear toggles.
  • Avoid assuming the administrator is using Windows or PowerShell by default; introduce both Windows and Linux options at the start of the tutorial.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat-policy.md ...ain/articles/firewall/tutorial-firewall-dnat-policy.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial exclusively demonstrates deploying and testing Azure Firewall DNAT using a Windows Server virtual machine and Remote Desktop (RDP) for connectivity testing. There are no examples or instructions for deploying a Linux VM, nor for testing connectivity using SSH or Linux-native tools. The only operating system mentioned for the workload VM is Windows, and the only connectivity test described is via RDP, a Windows-specific protocol.
Recommendations
  • Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet.
  • Include steps for testing DNAT access using SSH (port 22) to a Linux VM, alongside or instead of RDP.
  • Provide example NAT rules for both RDP (Windows) and SSH (Linux) scenarios.
  • When listing OS options for the VM, mention both Windows and Linux images, and show how to select either in the portal.
  • Generalize connectivity testing steps to cover both Windows (RDP) and Linux (SSH) use cases, ensuring parity.
  • Where possible, avoid assuming the administrator is using Windows, and provide cross-platform guidance.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall-reference.md ...b/main/articles/firewall/monitor-firewall-reference.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command examples for enabling and disabling diagnostic logs (Top flows and Flow trace), with no equivalent examples for Linux-native tools or Azure CLI. All command-line instructions use PowerShell cmdlets, which are most familiar and accessible to Windows users. There is no mention of Bash, Azure CLI, or cross-platform scripting, and the documentation assumes the use of PowerShell and Windows-centric workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command sequences, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that the operations can be performed using Azure CLI, ARM templates, or the Azure Portal, and provide links or references.
  • Where possible, provide Bash shell examples or note any differences in command syntax for Linux users.
  • Clarify that PowerShell can be used on Linux and macOS, but highlight Azure CLI as the preferred cross-platform tool.
  • Ensure that screenshots and navigation instructions are not specific to Windows-only tools or interfaces.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-migrate.md ...re-docs/blob/main/articles/firewall/premium-migrate.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell scripts and instructions for migration tasks, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code samples and tooling references are PowerShell-centric, which is most commonly associated with Windows environments. There are no Linux-specific or cross-platform migration examples, and PowerShell is presented as the default and only automation method.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used, and provide installation instructions for those platforms.
  • Include Bash script examples or guidance for users who prefer shell scripting on Linux.
  • Reorder sections or add notes to clarify that all steps can be performed from any OS, not just Windows, and avoid implying PowerShell is the only or primary method.
  • Where possible, use neutral language such as 'using Azure PowerShell or Azure CLI' instead of only referencing PowerShell.
  • Add a table or section comparing migration steps using both PowerShell and CLI to improve parity and user choice.
GitHub Create Pull Request
← Previous Page 6 of 14 Next →