Firewall

84
Total Pages
43
Linux-Friendly Pages
41
Pages with Bias
48.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (62)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-protect-firewall-ddos.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The tutorial demonstrates a Windows bias by exclusively using Windows Server as the example OS for the workload VM and referencing Windows-specific tools (e.g., Internet Explorer, Remote Desktop) for testing. There are no Linux-based examples or instructions for deploying or testing with a Linux VM, nor are Linux-compatible tools or workflows mentioned.
Recommendations:
  • Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the workload subnet.
  • Include Linux-specific steps for connecting to the VM (e.g., using SSH instead of RDP) and for testing outbound connectivity (e.g., using curl or wget instead of Internet Explorer).
  • When describing firewall rule testing, provide both Windows and Linux command-line examples for DNS resolution and web access.
  • Explicitly mention that the tutorial applies to both Windows and Linux workloads, and provide links to relevant Linux documentation where appropriate.
  • Ensure that screenshots and UI references are not OS-specific, or provide alternatives for both platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-terraform.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively deploys Windows Server virtual machines in its example scenario, with no mention of Linux VM options or parity. All VM-related steps and resources reference only Windows, and there are no examples or guidance for deploying or managing Linux VMs in the same context.
Recommendations:
  • Include parallel examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside Windows VM examples.
  • Update the scenario description to mention both Windows and Linux VM deployment options, or provide a rationale for the Windows-only focus.
  • Add a section or note explaining how to adapt the Terraform configuration for Linux VMs, including any differences in variables or resources.
  • Ensure that any scripts, troubleshooting, or verification steps are not Windows-specific, or provide Linux equivalents where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/management-nic.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/easy-upgrade.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/explicit-proxy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-known-issues.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/threat-intel.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation provides a hosts file modification example specifically for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS systems. No Linux or cross-platform examples are given for testing or configuration steps.
Recommendations:
  • Include Linux and macOS equivalents when referencing file paths or system modifications (e.g., mention /etc/hosts for Linux/macOS alongside the Windows path).
  • Provide cross-platform instructions or clarify that the steps apply to all major operating systems.
  • When giving examples, either show both Windows and Linux/macOS commands or use neutral, platform-agnostic language where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal-policy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The tutorial demonstrates a Windows bias by exclusively using a Windows Server virtual machine for the workload example and only describing remote desktop (RDP) access and Microsoft Edge browser for testing. There are no Linux VM deployment instructions, nor are there SSH or Linux-based testing steps. The documentation assumes a Windows environment for both deployment and validation, omitting Linux alternatives.
Recommendations:
  • Provide parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including sample configuration values.
  • Include steps for connecting to the Linux VM using SSH, and for testing outbound access using Linux command-line tools (e.g., curl or wget) instead of only Microsoft Edge.
  • Demonstrate how to configure DNS settings on a Linux VM (e.g., by editing /etc/resolv.conf or using netplan), not just via the Azure portal.
  • When describing firewall rules (such as DNAT), include examples for both RDP (Windows) and SSH (Linux) to show parity.
  • In the testing section, provide both Windows and Linux validation steps, ensuring users on either platform can follow along.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/dns-settings.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/customer-controlled-maintenance.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/fqdn-tags.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-firewall-basic-portal-policy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server as the example operating system for the workload VM, and by instructing users to connect via Remote Desktop and use Internet Explorer for testing. There are no examples or instructions for deploying or testing with a Linux VM, nor are Linux tools or workflows mentioned.
Recommendations:
  • Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) in the workload subnet, including example settings.
  • Include Linux-specific testing steps, such as connecting via SSH and using curl, wget, or a Linux browser to test outbound connectivity.
  • When describing remote access, mention both RDP (for Windows) and SSH (for Linux) as options, and show how to configure DNAT rules for SSH (port 22) as well as RDP (port 3389).
  • Avoid assuming the use of Internet Explorer or Windows-specific tools for testing; instead, offer cross-platform alternatives.
  • Explicitly state that the procedure applies to both Windows and Linux workloads, and provide example commands or screenshots for both where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-preview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ftp-support.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal-policy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat-policy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall-reference.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively uses Windows Server as the example OS for the test virtual machine and only describes connecting via Remote Desktop (RDP) and using Internet Explorer for testing. There are no examples or instructions for deploying or testing with a Linux VM, nor are Linux tools or workflows mentioned. The only OS-specific instructions are for Windows, and these appear before any mention of alternatives (which are absent).
Recommendations:
  • Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the 'Create a virtual machine' section, including example settings and commands.
  • Include Linux-specific testing instructions, such as using SSH to connect to the VM and using curl, wget, or a browser like Firefox for testing outbound connectivity.
  • When describing DNS configuration, provide guidance for setting DNS servers on a Linux VM (e.g., editing /etc/resolv.conf or using netplan).
  • In the 'Test the firewall' section, include Linux-based examples for verifying connectivity and DNS resolution.
  • Where possible, present both Windows and Linux options side-by-side, or at least mention Linux alternatives to ensure cross-platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-migrate.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-bicep.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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. All VM references are to Windows, and the admin credential instructions assume a Windows context. While deployment and management commands are cross-platform (Azure CLI and PowerShell), the infrastructure example is Windows-centric, lacking Linux parity.
Recommendations:
  • Include an example or option for deploying Linux virtual machines (e.g., Ubuntu Server) alongside or instead of Windows Server VMs in the Bicep template.
  • Explicitly mention that the jump box and server VMs can be either Windows or Linux, and provide parameterization or instructions for both.
  • When describing admin credentials, clarify any differences for Linux VMs (e.g., SSH keys vs. passwords).
  • Ensure that screenshots, walkthroughs, and validation steps reference both Windows and Linux VM scenarios where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a Windows bias by focusing on RDP access to Windows Server VMs, referencing PowerShell for resource cleanup, and omitting Linux VM or SSH examples. The only command-line example uses Azure PowerShell, and the workflow assumes Windows-centric tools and patterns.
Recommendations:
  • Include examples for deploying and accessing Linux VMs (e.g., SSH access) alongside Windows examples.
  • Provide equivalent Azure CLI commands for resource management (such as deleting the resource group), not just Azure PowerShell.
  • Mention both RDP (for Windows) and SSH (for Linux) as possible ways to connect to backend servers.
  • Balance references to Windows and Linux tools and workflows throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/threat-intel.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation provides a hosts file modification example only for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS. This prioritizes Windows and omits guidance for users on other platforms.
Recommendations:
  • Include equivalent instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
  • Present cross-platform examples together, or mention all major platforms when giving file path or configuration instructions.
  • Review the documentation for other areas where platform-specific instructions may be needed to ensure parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-preview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates bias towards Windows environments by referencing Azure PowerShell as a configuration method without mentioning Azure CLI or other cross-platform tools. There are no Linux-specific or cross-platform command examples, and the only tool explicitly mentioned for configuration is Azure PowerShell, which is more commonly associated with Windows environments.
Recommendations:
  • Include Azure CLI examples alongside or instead of Azure PowerShell for configuration steps, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that configuration can be performed from Linux, macOS, or Windows environments using Azure CLI or portal.
  • Where PowerShell is referenced, provide equivalent Bash/Azure CLI commands to ensure parity for Linux users.
  • Review all instructions to ensure that no step assumes a Windows environment or toolset by default.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-cli.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server images for virtual machines, instructing users to connect via Remote Desktop (RDP), and providing only PowerShell-based test commands. There are no examples or instructions for deploying or testing with Linux VMs, nor are there Linux shell command alternatives for testing firewall rules.
Recommendations:
  • Include parallel instructions and examples for deploying Linux-based virtual machines (e.g., using Ubuntu images) alongside the Windows examples.
  • Provide SSH-based connection instructions for Linux VMs, in addition to RDP for Windows.
  • Offer Linux shell command equivalents (e.g., using dig or curl) for testing DNS resolution and HTTP access, alongside the PowerShell commands.
  • Explicitly mention that the procedure is cross-platform and clarify any differences in steps or tools between Windows and Linux environments.
  • Where possible, use neutral language and examples that apply to both Windows and Linux, or present both options side by side.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-firewall-basic-portal-policy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively uses Windows Server as the example OS for the workload VM, with no mention of Linux alternatives or instructions. The testing section assumes the use of Remote Desktop and Internet Explorer, both Windows-specific tools, and does not provide Linux equivalents or guidance. While the Azure portal is cross-platform, the step-by-step instructions and validation steps are Windows-centric.
Recommendations:
  • Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the workload subnet, including example settings.
  • Include guidance for connecting to the Linux VM (e.g., using SSH) and testing outbound connectivity (e.g., using curl or wget to access allowed FQDNs).
  • In the firewall DNAT rule section, mention SSH (port 22) as an alternative to RDP (port 3389) for Linux VMs.
  • In the testing section, add Linux-specific examples for verifying DNS and HTTP/HTTPS access (e.g., using dig, nslookup, curl, or wget).
  • Explicitly state that the procedure is applicable to both Windows and Linux VMs, and provide links to relevant Azure Linux VM documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the example template, referencing only Windows-based admin workflows (e.g., admin username/password for Windows VMs), and providing cleanup instructions solely via a PowerShell command. There are no Linux VM deployment options, nor are there CLI/bash examples for resource cleanup or management.
Recommendations:
  • Include Linux VM options in the deployment template and documentation steps, or provide a parallel example using Linux distributions (e.g., Ubuntu).
  • When describing admin credentials, clarify differences for Linux (e.g., SSH key vs. password) and provide relevant instructions.
  • Add resource cleanup instructions using Azure CLI (az group delete) and bash, not just PowerShell.
  • Where possible, present both Windows and Linux options side-by-side, or at least mention Linux alternatives.
  • Avoid assuming the user is working from a Windows environment; provide cross-platform guidance.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-terraform.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the Terraform example and referring only to Windows VMs throughout. There are no examples or mentions of deploying Linux VMs, nor are there instructions or notes for users who may wish to use Linux servers instead. This may give the impression that only Windows is supported or recommended in this scenario.
Recommendations:
  • Include parallel examples or instructions for deploying Linux virtual machines using azurerm_linux_virtual_machine alongside the Windows VM steps.
  • Update the narrative to mention that either Windows or Linux VMs can be used, and provide guidance or code samples for both.
  • Where VM credentials or configuration are discussed (such as random_password for Windows), add equivalent Linux-focused steps (e.g., SSH key generation).
  • Ensure that any troubleshooting or verification steps are not specific to Windows and clarify cross-platform applicability.
  • Consider rephrasing the description and checklist to refer to 'virtual machines' generically, or explicitly state that both Windows and Linux are supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/dns-settings.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools
Summary:
The documentation provides both Azure CLI and PowerShell examples for configuring Azure Firewall DNS settings, but it demonstrates a Windows bias by including detailed PowerShell instructions (a Windows-centric tool) and referencing Azure PowerShell modules. The PowerShell examples are given equal prominence to CLI, but there are no explicit Linux shell (bash) or cross-platform scripting examples. The documentation also uses terminology and patterns (such as PowerShell object manipulation) that are specific to Windows environments. Additionally, the custom metadata includes 'devx-track-azurepowershell', further indicating a Windows/PowerShell focus.
Recommendations:
  • Add explicit bash or shell scripting examples for Linux users, especially for tasks currently shown only in PowerShell.
  • Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
  • Where possible, provide bash scripting equivalents for multi-step PowerShell object manipulations (e.g., updating DNS server lists).
  • Balance the order of examples: sometimes show CLI or bash first, not always PowerShell.
  • Remove or balance custom metadata tags (such as 'devx-track-azurepowershell') to reflect cross-platform support.
  • Explicitly state that all configuration steps can be performed from Linux/macOS using Azure CLI, and provide troubleshooting tips for non-Windows environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/easy-upgrade.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page mentions PowerShell as a supported method for performing Azure Firewall SKU upgrades/downgrades, but does not mention or provide examples for equivalent Linux/Unix command-line tools (such as Azure CLI). The order of mention (Azure portal, then PowerShell, then Terraform) also places a Windows-centric tool before cross-platform alternatives. No Linux-specific or cross-platform command-line examples are provided.
Recommendations:
  • Include Azure CLI examples for performing upgrade/downgrade operations, as Azure CLI is cross-platform and widely used on Linux.
  • Mention Azure CLI alongside PowerShell and Terraform in the list of supported tools, ideally listing the cross-platform option first or at least equally.
  • Provide sample commands or links to documentation for both PowerShell and Azure CLI to ensure parity for Linux users.
  • Review other documentation pages for similar patterns and update them to ensure equal representation of Linux-compatible tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/explicit-proxy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the deployment method in the 'Next steps' section, without mentioning or linking to equivalent Linux/CLI instructions. No Linux or cross-platform command-line examples are provided, and the only deployment guidance is via PowerShell, which is more commonly associated with Windows environments.
Recommendations:
  • Add links or references to Azure CLI and ARM template deployment guides alongside the PowerShell example.
  • Include explicit instructions or examples for configuring and deploying the explicit proxy feature using cross-platform tools (e.g., Azure CLI, Bash scripts).
  • Ensure that all configuration steps (such as uploading PAC files, generating SAS URLs) are described in a platform-agnostic way, or provide both Windows and Linux/macOS workflows.
  • Where possible, avoid assuming the use of Windows tools or environments; mention cross-platform alternatives early and equally.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-known-issues.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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), mentioning PowerShell and CLI support together but not distinguishing or providing parity for Linux/Unix users, and omitting Linux-specific or cross-platform command-line examples. There are no explicit Linux/Unix command examples or tool references, and PowerShell is assumed as the default scripting environment for management tasks.
Recommendations:
  • For every PowerShell example or reference, provide an equivalent Azure CLI (az) example, which is cross-platform and widely used on Linux and macOS.
  • When mentioning PowerShell and CLI support, clarify which commands are available in each and provide explicit Linux/Unix usage notes where relevant.
  • Where a workaround or mitigation references a PowerShell cmdlet (e.g., Set-AzFirewallPolicy), include the equivalent Azure CLI command (e.g., az network firewall policy update) if available.
  • Avoid assuming PowerShell as the default scripting environment; instead, present both PowerShell and CLI options side by side.
  • Add a section or note addressing Linux/macOS users, highlighting any differences or limitations in tooling or support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-sftp.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation is heavily biased towards Windows and PowerShell usage. All deployment and configuration steps are provided exclusively using Azure PowerShell cmdlets, with no mention or examples for Azure CLI, Bicep, ARM templates, or Terraform, which are commonly used on Linux and cross-platform environments. The only command-line example for SFTP connection is generic, but the setup and management instructions assume a Windows/PowerShell environment throughout.
Recommendations:
  • Provide equivalent Azure CLI examples for all deployment and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bicep or ARM template snippets for infrastructure-as-code parity.
  • Add a note at the beginning clarifying that the instructions are PowerShell-specific, and link to cross-platform alternatives.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links or examples.
  • Ensure that any references to tools or commands (such as 'command prompt') are platform-neutral or include both Windows and Linux/macOS equivalents.
  • Consider including a table or section comparing PowerShell and CLI commands for each major step.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/fqdn-tags.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Heavy Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first and Windows-heavy bias. Most FQDN tags and examples focus on Windows or Microsoft-specific services (e.g., Windows Update, Windows Diagnostics, Windows 365, Windows Virtual Desktop), with no mention of Linux-specific services or scenarios. There are no examples or guidance for Linux administrators or non-Windows environments.
Recommendations:
  • Include examples of FQDN tags relevant to Linux-based workloads or popular open-source services (if supported by Azure Firewall).
  • Add a section or examples addressing how Linux administrators might use FQDN tags, or clarify if the feature is equally applicable to Linux-based environments.
  • Balance the documentation by mentioning both Windows and non-Windows scenarios where possible, or explicitly state the Windows-centric nature if it is by design.
  • If Azure Firewall supports FQDN tags for non-Microsoft or cross-platform services, provide examples and documentation for those cases.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ftp-support.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell-based deployment and update workflows first and in more detail. While Azure CLI and ARM template options are mentioned, there are no explicit Linux shell (bash) examples or guidance, and the PowerShell workflow is given prominence and more explanation. There is no mention of Linux-native tools or workflows, and the CLI section lacks example commands.
Recommendations:
  • Add explicit bash/Azure CLI command examples for both deployment and updating scenarios, similar to the PowerShell examples.
  • Present Azure CLI and ARM template instructions before or alongside PowerShell, rather than after.
  • Include notes or examples relevant to Linux users, such as using Azure CLI in bash or cloud shell.
  • Ensure parity in detail and explanation between PowerShell and CLI/ARM template sections.
  • Where possible, avoid assuming PowerShell as the default automation tool, and clarify that all examples are cross-platform unless otherwise stated.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/integrate-with-nat-gateway.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation presents Azure PowerShell examples before Azure CLI, which is more commonly used on Linux and cross-platform environments. There are no Bash or Linux-specific shell examples, and the PowerShell section is labeled and presented first, suggesting a Windows-centric approach. No mention is made of Linux tools or workflows, and all command-line examples are either PowerShell or Azure CLI, with no explicit Linux context.
Recommendations:
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include explicit Bash/Linux shell examples, especially for users working in Linux environments.
  • Add a note clarifying that Azure CLI commands can be run on Windows, Linux, and macOS, and provide guidance for Linux users if there are any differences.
  • Ensure parity in documentation by referencing both Windows and Linux environments where relevant, and avoid assuming PowerShell as the default shell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ip-groups.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a bias toward Windows environments by exclusively listing Azure PowerShell cmdlets for managing IP Groups, without providing equivalent Azure CLI (cross-platform) or Bash examples. There are no Linux-specific instructions or examples, and the only command-line tooling referenced is PowerShell, which is traditionally associated with Windows, despite its cross-platform availability. This may disadvantage Linux users or those preferring CLI/Bash workflows.
Recommendations:
  • Add Azure CLI examples for all IP Group management tasks alongside PowerShell cmdlets.
  • Explicitly mention that Azure CLI and REST API can be used, and provide links or code snippets.
  • Include Bash shell examples for common operations, especially for tasks like exporting/importing CSVs.
  • Balance the 'Related Azure PowerShell cmdlets' section with a 'Related Azure CLI commands' section.
  • Clarify that PowerShell is available cross-platform, but highlight CLI/Bash parity for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/management-nic.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for managing the Azure Firewall Management NIC, with no mention of Azure CLI (cross-platform) or Bash/shell equivalents. The only automation examples use PowerShell cmdlets, which are primarily associated with Windows environments. There is no guidance or parity for Linux/macOS users, and the documentation implicitly assumes a Windows-centric workflow.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide side-by-side examples where possible.
  • Include Bash/shell script snippets for common tasks, or at least reference how to perform the same actions from non-Windows environments.
  • Review the documentation for other Windows-centric terminology or assumptions, and ensure instructions are inclusive of all supported platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall-reference.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for enabling and disabling diagnostic logs (Top flows and Flow trace), with no equivalent Azure CLI, Bash, or Linux-native instructions. The only command-line tooling referenced is PowerShell, which is most commonly associated with Windows environments, and there is no mention of cross-platform or Linux-first alternatives.
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, or Windows, and clarify any platform-specific requirements.
  • Where possible, include Bash script examples alongside PowerShell, especially for enabling/disabling diagnostic settings.
  • Reference Azure Portal UI steps as an alternative for users who may not use PowerShell or CLI.
  • Add a note or table summarizing all available tooling (PowerShell, Azure CLI, REST API, Portal) for each operation, with links to relevant documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Missing Linux Example
Summary:
The documentation displays a subtle Windows bias. It references Windows-centric tools (Excel, Power BI, Visual Studio, C#) and specifically calls out Azure PowerShell for enabling certain features (e.g., Fat Flow Log), without mentioning or providing parity for Linux or cross-platform alternatives (such as Azure CLI, Linux-compatible log viewers, or editors). There are no explicit Linux or cross-platform command-line examples, and the only tooling guidance for log conversion is for Visual Studio/C# users.
Recommendations:
  • Provide Azure CLI examples alongside or instead of Azure PowerShell for configuration steps, especially for enabling features like Fat Flow Log.
  • Mention and provide examples for Linux-compatible tools for viewing and analyzing logs (e.g., jq, csvkit, LibreOffice Calc, or open-source BI tools).
  • If referencing Visual Studio/C# tools, also mention scripting or conversion options in Python or Bash that are platform-agnostic.
  • Ensure that any references to downloading and converting logs (e.g., JSON to CSV) include command-line examples that work on Linux/macOS (such as using jq or csvkit).
  • Explicitly state that all features and steps can be performed from Linux/macOS environments, and provide links or examples where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy-certificates-enterprise-ca.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation is heavily biased towards Windows environments. All certificate management steps rely on Windows-specific tools (certtmpl.msc, Internet Explorer, Windows Certificate Export Wizard), and prerequisites assume Active Directory and Windows CA infrastructure. There are no Linux or cross-platform alternatives or examples provided for certificate creation, request, or export. The workflow is not accessible to administrators using Linux or non-Windows PKI solutions.
Recommendations:
  • Provide equivalent instructions for Linux environments, such as using OpenSSL for certificate requests and exports.
  • Include examples for managing certificates with non-Windows CAs (e.g., OpenSSL, EJBCA, or HashiCorp Vault).
  • Describe how to interact with Azure Key Vault and import certificates using CLI tools available on Linux (e.g., Azure CLI, REST API).
  • Avoid assuming the use of Internet Explorer or Windows Certificate Export Wizard; offer browser-agnostic or command-line alternatives.
  • Clarify which steps are Windows-specific and provide cross-platform alternatives wherever possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 opening browsers. There are no Linux VM deployment instructions or examples, and the process for installing certificates is only described for Windows. The use of 'administrator command prompt' and browser-based testing is also presented only in a Windows context.
Recommendations:
  • Provide parallel instructions for deploying and configuring a Linux-based WorkerVM, including certificate installation steps for common distributions (e.g., Ubuntu).
  • Include Linux-specific command-line examples (e.g., using bash or terminal) alongside Windows examples.
  • Clarify that curl and browser-based tests can be performed on both Windows and Linux, and provide any necessary Linux-specific guidance (such as installing curl or updating CA certificates).
  • When describing certificate deployment, include steps for both Windows and Linux VMs.
  • Use neutral language (e.g., 'open a terminal') instead of 'administrator command prompt' where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-migrate.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily biased toward Windows and PowerShell usage. All code examples and automation scripts are provided exclusively in PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. The instructions for module installation and validation are PowerShell-specific, and there are no Linux or cross-platform alternatives presented. Even though Azure PowerShell is technically cross-platform, the documentation assumes a Windows/PowerShell environment and does not address Linux users' needs or workflows.
Recommendations:
  • Provide equivalent Azure CLI (az) commands for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash script examples or at least command-line snippets for Linux users.
  • Clearly state that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
  • When referencing tooling (such as module installation), include both PowerShell and Azure CLI alternatives.
  • Where possible, add screenshots or walkthroughs using the Azure Portal, which is platform-agnostic.
  • Review the order of presentation so that cross-platform methods (Azure CLI, Portal) are mentioned before or alongside PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-terraform.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation lists the creation of a random password for a Windows VM before mentioning the creation of a Linux VM, and references a Windows VM specifically in the checklist of resources. However, the main implementation steps and code samples are platform-agnostic, and the verification and CLI instructions use Azure CLI, which is cross-platform. There are no PowerShell-specific examples, and both Windows and Linux VMs are mentioned, though Windows is listed first.
Recommendations:
  • List the creation of Linux and Windows VMs together or mention Linux first to avoid implicit prioritization of Windows.
  • Provide equivalent detail for both Linux and Windows VM creation steps, or clarify that both are optional and can be created as needed.
  • Ensure that any references to OS-specific resources or steps are balanced and that neither platform is implied as the default.
  • If possible, add explicit notes that the instructions and code samples are cross-platform and work on both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/protect-azure-virtual-desktop.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based Azure Virtual Desktop deployments, referencing Windows-specific service tags, and providing proxy configuration examples only for Microsoft Edge. There are no examples or guidance for Linux-based session hosts or cross-platform scenarios, and Linux tools or patterns are not mentioned.
Recommendations:
  • Include explicit guidance and examples for Linux-based Azure Virtual Desktop session hosts, such as required FQDNs, endpoints, and firewall rules.
  • When discussing proxy configuration, provide examples for popular Linux browsers (e.g., Firefox, Chromium) and command-line tools.
  • Mention and link to documentation about deploying and managing Azure Virtual Desktop on Linux, if available.
  • Use neutral terminology (e.g., 'session host' instead of 'Windows session host') where possible, and clarify when instructions are Windows-specific.
  • If certain features are Windows-only, clearly state this and provide alternative recommendations for Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example
Summary:
The documentation provides a PowerShell example (Remove-AzResourceGroup) for resource cleanup but does not offer equivalent CLI or Bash commands for Linux/macOS users. No Linux-specific or cross-platform command-line instructions are given, despite the ARM template including a Linux jumpbox.
Recommendations:
  • Add Azure CLI and/or Bash examples for resource group deletion (e.g., az group delete --name <your resource group name>).
  • Wherever PowerShell is used, provide equivalent cross-platform commands or clearly indicate alternatives for Linux/macOS users.
  • Consider including a table or section summarizing common operations (deploy, delete, review) with both PowerShell and Azure CLI/Bash commands.
  • Review other steps for implicit Windows assumptions and clarify that all steps can be performed from any OS using the Azure CLI or portal.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-bicep.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a Windows bias by focusing on RDP access to Windows Server VMs, referencing Azure PowerShell as a primary tool, and omitting Linux-specific examples or scenarios (such as SSH access to Linux VMs). The clean-up instructions use only PowerShell, and there is no mention of Linux tools or workflows.
Recommendations:
  • Include examples for accessing Linux VMs (e.g., SSH) alongside RDP/Windows examples.
  • Provide clean-up instructions using Azure CLI, not just PowerShell.
  • Mention both Azure CLI and PowerShell equally when describing deployment and management steps.
  • Reference documentation for deploying and accessing both Windows and Linux VMs through the firewall.
  • Balance the use of Windows and Linux terminology and tools throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-terraform.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by focusing exclusively on deploying and accessing Windows Server virtual machines (with RDP), without mentioning or providing examples for Linux VMs or SSH access. The only VM example is Windows, and the NAT rules are described as enabling RDP to Windows Server 2019 VMs. There are no Linux VM deployment steps or verification instructions for Linux users.
Recommendations:
  • Include parallel examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside the Windows VM steps.
  • Describe how to configure NAT rules for SSH access to Linux VMs, in addition to RDP for Windows.
  • In the checklist and resource creation steps, mention both Windows and Linux VM options, or provide a choice.
  • In the verification section, add instructions for verifying access to Linux VMs (e.g., using SSH) as well as Windows VMs.
  • Reference documentation for both Windows and Linux VM management in Azure, not just Windows/PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/remote-work-support.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page focuses exclusively on Windows-based virtual desktop infrastructure, specifically Azure Virtual Desktop (which is Windows-centric), and does not mention or provide guidance for Linux-based virtual desktop solutions or clients. All examples and descriptions assume a Windows environment, with no reference to Linux equivalents or cross-platform scenarios.
Recommendations:
  • Include references to Linux-based virtual desktop solutions that can be protected by Azure Firewall, such as Linux VDI or third-party Linux desktop virtualization tools.
  • Provide examples or guidance for securing outbound/inbound connections for Linux virtual machines or Linux-based remote desktop clients.
  • Mention that Azure Firewall can protect both Windows and Linux workloads, and provide parity in documentation for both operating systems.
  • If possible, add links or references to documentation on securing Linux remote work environments with Azure Firewall.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/secured-hub-customer-public-ip.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing configuration instructions and examples exclusively for the Azure portal and Azure PowerShell, both of which are Windows-centric tools. There are no equivalent examples or guidance for Linux users, such as Azure CLI or ARM templates. The PowerShell example is given as the only command-line method, and there is no mention of cross-platform alternatives.
Recommendations:
  • Add Azure CLI examples for all configuration steps to ensure Linux and macOS users have clear, supported instructions.
  • Mention ARM template or Bicep deployment options for infrastructure-as-code parity.
  • When listing configuration methods, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools (e.g., PowerShell).
  • Explicitly state that the instructions apply to all platforms, or clarify any platform-specific limitations.
  • Include screenshots or walkthroughs from non-Windows environments where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/service-tags.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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 examples using Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there references to Linux-native tools or shell environments. The configuration section leads with and exclusively details PowerShell commands, reinforcing a Windows-centric approach.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell commands shown, ensuring Linux/macOS users can follow along without needing PowerShell.
  • Explicitly mention that Azure CLI can be used from any platform and provide links to relevant CLI documentation.
  • Consider including Bash shell examples where appropriate, especially for scripting or automation scenarios.
  • Reorder the configuration section to present Azure CLI and PowerShell examples side by side, or start with the more cross-platform Azure CLI.
  • Review and update any references or links that are PowerShell-specific to include CLI alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/snat-private-range.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing detailed Azure PowerShell (Windows-centric) examples before Azure CLI, and by not including any Linux-specific shell or scripting examples (e.g., Bash). The PowerShell examples are more extensive and detailed than the CLI ones. There are no references to Linux tools, shell environments, or considerations for Linux users. The documentation assumes familiarity with PowerShell, which is traditionally a Windows tool, and does not offer parity for Linux-native workflows.
Recommendations:
  • Provide Bash shell examples alongside Azure CLI commands to demonstrate Linux-native workflows.
  • Ensure that Azure CLI examples are as detailed and comprehensive as the PowerShell examples, including notes on prerequisites and environment setup for Linux users.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any OS-specific considerations if applicable.
  • Where PowerShell is referenced, clarify that PowerShell Core is cross-platform, or provide alternative scripts for Bash/zsh users.
  • Add a section or notes addressing Linux users, including any differences in command syntax, environment variables, or deployment steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/sql-fqdn-filtering.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First
Summary:
The documentation provides configuration steps using Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric and still most commonly used on Windows) and the absence of Linux-native tools or explicit Linux shell examples (such as Bash scripts) indicate a Windows bias. Additionally, the PowerShell section is given equal prominence to the CLI, and there are no Linux-specific troubleshooting or environment notes. There are no examples or guidance tailored for Linux users beyond the CLI, and no mention of Linux-specific considerations.
Recommendations:
  • Add explicit Bash shell examples for Azure CLI commands, including any necessary environment setup or differences for Linux users.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if applicable (e.g., line continuation differences, authentication nuances).
  • If PowerShell is included, consider also including Bash or shell script equivalents for parity.
  • Mention that Azure PowerShell is available cross-platform, but note any differences or prerequisites for Linux users.
  • Include troubleshooting steps or references for common issues on Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal-policy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The tutorial demonstrates a Windows bias by exclusively using a Windows Server virtual machine for the workload and providing only instructions for connecting via Remote Desktop (RDP) and using Microsoft Edge. There are no examples or guidance for deploying or testing with a Linux VM, nor are there instructions for connecting via SSH or using Linux-based tools to test firewall rules.
Recommendations:
  • Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including appropriate configuration steps.
  • Include examples for connecting to the Linux VM using SSH, and provide Linux-based testing steps (e.g., using curl or wget to test outbound access, dig or nslookup for DNS testing).
  • When describing the test phase, offer both Windows (RDP, Edge) and Linux (SSH, browser or command-line tools) options.
  • Consider mentioning both Windows and Linux options side-by-side throughout the tutorial, rather than only referencing Windows tools and patterns.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively demonstrates deploying and testing Azure Firewall using a Windows Server virtual machine, with no mention or example of Linux-based VMs. The test instructions (e.g., using Remote Desktop and Internet Explorer) are Windows-specific, and there are no Linux alternatives or parity in the walkthrough. The only OS option presented for the test VM is Windows, and the testing steps assume a Windows environment.
Recommendations:
  • Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the test subnet, including example configuration values.
  • Include Linux-specific testing steps, such as connecting via SSH and using a browser like Firefox or Chrome to test outbound access.
  • Provide guidance on configuring DNS settings for Linux VMs (e.g., editing /etc/resolv.conf or using cloud-init).
  • Wherever possible, present both Windows and Linux options side-by-side, or at least mention Linux as an alternative.
  • Avoid assuming the use of Windows-only tools (e.g., Remote Desktop, Internet Explorer) in testing steps; suggest cross-platform or Linux-native alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat-policy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The tutorial exclusively uses a Windows Server virtual machine as the workload example and instructs users to test connectivity using Remote Desktop (RDP), which is a Windows-centric protocol. There are no Linux VM deployment instructions or SSH-based testing examples, and the only OS option explicitly mentioned is Windows Server. This creates a Windows-first impression and omits Linux parity in both deployment and testing steps.
Recommendations:
  • Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including specifying username, authentication, and any required inbound ports (e.g., 22 for SSH).
  • Include testing steps for Linux VMs, such as connecting via SSH to the firewall public IP address and verifying access to the Linux VM.
  • When listing OS choices for the VM, mention both Windows and Linux options, or provide a choice step.
  • If using RDP as an example, also provide an SSH example for Linux, including the necessary DNAT rule for port 22.
  • Ensure that screenshots or UI steps do not assume only Windows Server images are being used.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively uses Windows Server as the example workload VM and only demonstrates testing via Remote Desktop (RDP) to port 3389, which is specific to Windows environments. There are no Linux VM deployment instructions, nor are there examples for Linux-based access (such as SSH on port 22). This presents a Windows-first bias and omits Linux parity in both deployment and testing steps.
Recommendations:
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu Server) in the 'Create a virtual machine' section.
  • Provide an example NAT rule for SSH (port 22) to a Linux VM, alongside the RDP example.
  • In the 'Test the firewall' section, add steps for connecting via SSH to the Linux VM using its public IP and port 22.
  • When referencing operating system-specific steps, present both Windows and Linux options, or clarify that the process is OS-agnostic where possible.
  • Consider mentioning cross-platform remote access tools or protocols, or provide a note about how to adapt the instructions for Linux workloads.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal-policy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a clear Windows bias. All virtual machine creation examples use Windows Server images, and all configuration and extension installation steps use PowerShell commands. There are no Linux VM examples, no Bash/Azure CLI commands, and no mention of Linux tools or patterns. The only method shown for installing IIS is via a PowerShell script, and the test scenarios exclusively use RDP and Windows-based workflows.
Recommendations:
  • Add parallel Linux examples for VM creation, such as using Ubuntu or other popular Linux distributions.
  • Provide Bash/Azure CLI equivalents for all PowerShell commands, especially for VM extension installation and configuration.
  • Include instructions for installing and testing with Apache or Nginx on Linux VMs, not just IIS on Windows.
  • Demonstrate SSH access and Linux-native tools for connectivity and firewall testing, in addition to RDP.
  • Ensure screenshots and walkthroughs are not exclusively Windows-centric; show Linux VM portal configuration where appropriate.
  • Explicitly mention that the tutorial is applicable to both Windows and Linux environments, and provide guidance for both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias in several ways: it exclusively uses Windows Server virtual machines for all examples, provides only PowerShell-based automation (no Bash or CLI), and omits any Linux VM or Linux-based configuration steps. The installation of IIS and remote access instructions are all Windows-centric, and there are no parallel instructions or notes for Linux users. The only scripting example is PowerShell, and the Cloud Shell is set to PowerShell by default. No mention is made of deploying or testing with Linux VMs, nor are there examples using Azure CLI/Bash.
Recommendations:
  • Provide parallel examples for deploying and configuring Linux virtual machines (e.g., Ubuntu) in both the spoke and on-premises subnets.
  • Include Azure CLI (Bash) commands alongside PowerShell for automation steps, such as installing web servers or configuring resources.
  • Demonstrate how to install and test with a Linux web server (e.g., Apache or Nginx) as an alternative to IIS.
  • Add instructions for connecting to Linux VMs (e.g., using SSH) and testing firewall rules with Linux tools (curl, wget, etc.).
  • Explicitly mention that the steps apply to both Windows and Linux, and highlight any OS-specific differences.
  • When referencing Cloud Shell, note that both Bash and PowerShell are available, and provide command examples for both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-protect-firewall-ddos.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The tutorial exclusively uses Windows Server as the example operating system for the workload VM, with no mention of Linux alternatives or instructions. The testing steps assume the use of Remote Desktop and Internet Explorer, both Windows-specific tools, and there are no Linux command-line or desktop environment equivalents provided. The only alternative workflow mentioned is Azure PowerShell, with no reference to Azure CLI or Bash scripting.
Recommendations:
  • Include parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) alongside the Windows Server example.
  • Provide Linux-compatible testing steps, such as using SSH for remote access and browsers like Firefox or Chrome for validation.
  • Reference Azure CLI and Bash scripting alternatives for users who prefer or require non-Windows environments.
  • Explicitly mention that the tutorial is applicable to both Windows and Linux VMs, and provide guidance for both where steps differ.
  • When suggesting remote access, offer both RDP (for Windows) and SSH (for Linux) instructions.