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 26-50 of 332 flagged pages
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides configuration examples for Azure Firewall prescaling using the Azure portal (GUI), Azure PowerShell, and Bicep templates. The only command-line example is given in PowerShell, which is primarily a Windows tool, with no equivalent example for Linux users (such as Azure CLI or Bash). PowerShell is mentioned before Bicep, and there is no reference to Linux-native tools or patterns, resulting in a Windows-centric bias.
Recommendations
- Add an Azure CLI example for configuring prescaling, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell examples are for Windows users, and provide parity for Linux/Mac users.
- Consider including Bash script snippets or references to automation via REST API for broader platform coverage.
- Order examples so that cross-platform tools (Azure CLI, REST API) appear before or alongside Windows-specific tools (PowerShell).
Create Pull Request
Firewall
Quickstart: Create an Azure Firewall and IP Groups - Resource Manager template
...ain/articles/firewall/quick-create-ipgroup-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides only a PowerShell example (Remove-AzResourceGroup) for cleaning up resources, with no equivalent Linux (Azure CLI, Bash) command. The use of PowerShell cmdlets and lack of cross-platform instructions suggests a bias toward Windows environments and tools. No Linux or cross-platform alternatives are mentioned for resource group deletion, and the documentation does not provide parity for users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI (az group delete) and Bash examples for resource group deletion.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to relevant cross-platform documentation.
- Wherever a PowerShell cmdlet is shown, also show the Azure CLI equivalent, ideally side-by-side.
- Review the documentation for other steps that may implicitly assume Windows usage and ensure Linux/macOS parity.
- Include a note or table summarizing command options for different platforms (Windows, Linux, macOS).
Firewall
Deploy and configure Azure Firewall Premium
...ure-docs/blob/main/articles/firewall/premium-deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM) for all deployment and testing steps. All instructions for running commands (such as curl) and browser-based tests are performed on the Windows VM, with no mention of Linux alternatives or guidance for deploying/testing on Linux VMs. The certificate deployment step specifically targets Windows, and there is no parity for Linux environments.
Recommendations
- Include instructions for deploying and configuring a Linux test VM alongside or instead of the Windows VM.
- Provide Linux-specific steps for installing certificates, running curl commands, and performing browser-based tests.
- Clarify that both Windows and Linux VMs can be used for testing Azure Firewall Premium features, and provide examples for each.
- Mention Linux tools and command-line patterns where appropriate, such as using bash or terminal on Linux VMs.
- Ensure screenshots and UI instructions are not Windows-centric, or provide Linux equivalents where relevant.
Firewall
Deploy and configure Enterprise CA certificates for Azure Firewall Premium
.../firewall/premium-deploy-certificates-enterprise-ca.md
High Priority
View Details →
Detected Bias Types
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, Internet Options, Windows certificate export wizard) and Active Directory Certification Services. There are no Linux or cross-platform alternatives provided for certificate creation, request, or export. The prerequisites and workflow assume a Windows-based PKI and client environment, with no mention of Linux-compatible CA solutions or command-line tools.
Recommendations
- Provide equivalent instructions for Linux environments, such as using OpenSSL or certtool for certificate creation and management.
- Include examples of requesting and exporting certificates using Linux command-line tools.
- Mention Linux-compatible PKI solutions (e.g., Dogtag, EJBCA) as alternatives to Active Directory Certification Services.
- Clarify which steps are Windows-specific and offer cross-platform guidance where possible.
- Add screenshots and walkthroughs for Linux-based certificate management workflows.
- Ensure that validation steps (such as viewing certificates in browsers) include guidance for Linux browsers (e.g., Firefox, Chrome on Linux).
Firewall
Use Azure Firewall to protect Azure Virtual Desktop
...ain/articles/firewall/protect-azure-virtual-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Azure Virtual Desktop, which is primarily associated with Windows environments. It references Windows-specific service tags (WindowsVirtualDesktop), endpoints, and tools (such as Microsoft Edge proxy configuration), without providing equivalent guidance or examples for Linux-based virtual desktop solutions or clients. There are no Linux-specific instructions, examples, or mentions of Linux-compatible tools or patterns for configuring outbound access, proxies, or firewall rules.
Recommendations
- Include examples and instructions for Linux-based virtual desktop environments (e.g., using Linux session hosts with Azure Virtual Desktop, if supported).
- Provide Linux-specific guidance for configuring outbound access, such as using iptables, firewalld, or ufw on Linux hosts.
- Add proxy configuration examples for popular Linux browsers (e.g., Firefox, Chromium) and command-line tools.
- Mention Linux service tags or endpoints if available, or clarify platform applicability for the documented steps.
- Ensure that references to tools and configuration patterns are cross-platform or provide parity for both Windows and Linux environments.
Firewall
Quickstart: Create an Azure Firewall with multiple public IP addresses - Resource Manager template
...articles/firewall/quick-create-multiple-ip-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a Windows bias by focusing exclusively on Windows-based scenarios and tools. It only references RDP connections to Windows Server VMs, provides PowerShell cmdlets for resource cleanup, and does not mention or provide examples for Linux VMs, SSH access, or equivalent Linux command-line tools. There are no Linux-specific instructions or parity in the deployment or validation steps.
Recommendations
- Include examples for deploying and connecting to Linux virtual machines (e.g., SSH access) alongside Windows examples.
- Provide equivalent cleanup instructions using Azure CLI (az group delete) and Bash shell commands, not just PowerShell.
- Mention both RDP (for Windows) and SSH (for Linux) in the NAT rule collection and validation steps.
- Balance references to Windows and Linux tools and patterns throughout the documentation to ensure cross-platform parity.
- Consider adding a section or note for users who prefer Linux environments, with relevant links and guidance.
Firewall
Quickstart: Create an Azure Firewall with multiple public IP addresses - Bicep
...in/articles/firewall/quick-create-multiple-ip-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates Windows bias by focusing exclusively on Windows Server 2019 virtual machines for deployment and remote access (RDP), mentioning Azure PowerShell before Azure CLI, and providing only PowerShell examples for resource cleanup. There are no Linux VM deployment examples, nor are Linux remote access methods (such as SSH) discussed. The page also references a PowerShell-specific guide for further information.
Recommendations
- Include examples for deploying Linux virtual machines alongside Windows VMs in the Bicep template.
- Provide instructions for connecting to Linux VMs using SSH, in addition to RDP for Windows VMs.
- Offer resource cleanup commands using Azure CLI (e.g., 'az group delete') alongside PowerShell.
- Reference documentation for deploying Azure Firewall with multiple public IPs using Azure CLI and/or ARM templates, not just PowerShell.
- Ensure that both Windows and Linux scenarios are covered equally in diagrams, explanations, and step-by-step instructions.
Firewall
Overview of Azure Firewall service tags
...azure-docs/blob/main/articles/firewall/service-tags.md
High Priority
View Details →
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. Although it mentions Azure CLI and the Azure portal as configuration options, no examples or instructions are given for these, which are more commonly used on Linux and cross-platform environments. The use of PowerShell and Windows-centric tools is prioritized, and Linux users are left without guidance.
Recommendations
- Add equivalent Azure CLI examples for all configuration steps shown in PowerShell.
- Provide instructions or screenshots for using the Azure portal to configure service tags.
- Explicitly mention cross-platform compatibility and clarify which tools are available on Linux.
- Ensure that Linux and macOS users are not required to use PowerShell for basic configuration tasks.
Firewall
Configure Azure Firewall application rules with SQL FQDNs
...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
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 are no explicit Linux shell (bash) examples or references to Linux-specific patterns or tools. The order of presentation places Azure CLI first, but the PowerShell section is equally prominent and detailed, with no mention of Linux shell alternatives. There is no discussion of Linux-specific considerations or troubleshooting.
Recommendations
- Add explicit bash shell examples for configuring Azure Firewall application rules, demonstrating usage on Linux systems.
- Include notes or sections addressing Linux-specific considerations, such as environment setup or differences in CLI usage.
- Clarify that Azure CLI is cross-platform and provide example commands run in a Linux shell (e.g., bash), possibly with screenshots or terminal output.
- If PowerShell is mentioned, also mention PowerShell Core's cross-platform support, or provide parity with bash examples.
- Review and update links or references to ensure Linux users are equally supported in troubleshooting and advanced configuration.
Firewall
Tutorial: Deploy and configure Azure Firewall and policy in a hybrid network using the Azure portal
...ain/articles/firewall/tutorial-hybrid-portal-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All virtual machine creation examples use Windows Server images, and the only provided automation example for installing IIS uses PowerShell. There are no Linux VM examples, nor are there Bash or CLI equivalents for VM setup or IIS installation. The workflow assumes familiarity with Windows tools and patterns, and Linux alternatives are not mentioned or suggested.
Recommendations
- Include parallel examples for creating Linux-based virtual machines (e.g., Ubuntu) in both the spoke and on-premises networks.
- Provide Bash/Azure CLI commands for automating VM configuration and software installation, such as installing Apache or Nginx on Linux VMs.
- When demonstrating firewall rules, include examples for common Linux services (SSH, HTTP) and show how to test connectivity from Linux clients.
- Explicitly mention that the tutorial works with both Windows and Linux VMs, and provide links to relevant Linux documentation.
- Where PowerShell is used, offer equivalent Bash or Azure CLI scripts for Linux users.
- Balance screenshots and walkthroughs to show both Windows and Linux environments where applicable.
Firewall
Tutorial: Deploy Azure Firewall private IP DNAT for overlapped and nonroutable networks
...lob/main/articles/firewall/tutorial-private-ip-dnat.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a clear Windows bias in its VM configuration and testing sections. Only Windows virtual machines (win-vm-2, win-vm-3) are referenced, and all configuration scripts are provided exclusively as PowerShell scripts. There are no examples or instructions for deploying or configuring Linux VMs, nor are there Bash or Linux shell script equivalents. The documentation assumes the use of Windows tools (PowerShell, RDP) and does not mention SSH or Linux-native approaches. This may limit accessibility and parity for users operating Linux environments.
Recommendations
- Add equivalent instructions and scripts for configuring Linux VMs, including Bash shell scripts.
- Provide examples using SSH for Linux VM access, alongside RDP/Bastion for Windows.
- Explicitly mention that both Windows and Linux VMs can be used for testing DNAT scenarios, and provide guidance for both.
- Include troubleshooting and monitoring steps relevant to Linux environments (e.g., using syslog, Linux firewall logs).
- Ensure that all code samples and configuration steps are available for both Windows and Linux platforms.
Firewall
Filter inbound Internet or intranet traffic with Azure Firewall DNAT using the portal
.../blob/main/articles/firewall/tutorial-firewall-dnat.md
High Priority
View Details →
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, guiding users to test DNAT with Remote Desktop (RDP, port 3389), and omitting any Linux VM deployment or SSH (port 22) testing instructions. No Linux-specific tools, patterns, or parity examples are provided, and Windows is presented as the default/only option for workload and connectivity.
Recommendations
- Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
- Include NAT rule examples for SSH (port 22) and describe how to connect via SSH from a Linux or Windows client.
- Provide guidance for both RDP (Windows) and SSH (Linux) connectivity testing.
- Mention Linux equivalents for any Windows-specific tools or patterns referenced.
- Ensure that screenshots, code snippets, and step-by-step instructions are provided for both platforms, or clarify platform-specific differences where relevant.
Firewall
Quickstart: Create an Azure Firewall with Availability Zones - Resource Manager template
...re-docs/blob/main/articles/firewall/deploy-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively deploying Windows Server virtual machines in the example template, mentioning only Windows-based VMs (jump box and server), and providing cleanup instructions solely via PowerShell (Remove-AzResourceGroup). There are no references to Linux VM deployment, nor are there CLI/bash alternatives for resource cleanup.
Recommendations
- Include options in the ARM template and documentation to deploy Linux-based VMs (e.g., Ubuntu, CentOS) alongside or instead of Windows Server VMs.
- Provide resource cleanup instructions using Azure CLI (az group delete) and Bash, not just PowerShell.
- Mention Linux as a supported OS for jump box and server roles, and provide guidance/examples for configuring Linux VMs in this scenario.
- Ensure that examples and instructions are presented in a cross-platform manner, or explicitly offer both Windows and Linux alternatives.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias. All command-line examples and scripts are provided exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native instructions. The manual migration steps, troubleshooting, and validation procedures rely entirely on PowerShell cmdlets and modules, which are primarily used on Windows. There is no mention of Linux or cross-platform alternatives, and PowerShell is referenced before Terraform in all relevant sections. The prerequisites and troubleshooting also assume PowerShell usage, further reinforcing the Windows-centric approach.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Provide Bash script examples for migration and validation steps to support Linux administrators.
- Explicitly mention that PowerShell Core is available on Linux and macOS, and clarify any differences in usage or installation.
- Reorder sections to present cross-platform tools (Azure CLI, Terraform) before or alongside PowerShell.
- Include troubleshooting steps using Azure CLI and Bash, not just PowerShell.
- Update prerequisites to mention Azure CLI as an alternative to PowerShell for command-line operations.
Firewall
Choose the right Azure Firewall SKU to meet your needs
...ocs/blob/main/articles/firewall/choose-firewall-sku.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing 'PowerShell' as a primary management interface for Azure Firewall, grouping it with REST, CLI, templates, and Terraform, but not specifying or providing parity for Linux-native tools or shell environments. There are no explicit Linux/Bash examples or references, and Windows-centric tooling (PowerShell) is mentioned before cross-platform or Linux-first options (CLI, Terraform).
Recommendations
- Explicitly mention Bash/Cloud Shell and provide Linux CLI examples alongside PowerShell.
- Clarify that Azure CLI and Terraform are cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash).
- Avoid listing PowerShell before CLI or Bash unless contextually relevant; consider alphabetical or platform-neutral ordering.
- Add links or references to Linux-specific deployment and management guides for Azure Firewall.
Firewall
Configure customer-controlled maintenance for Azure Firewall
...n/articles/firewall/customer-controlled-maintenance.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples and references before CLI (cross-platform) examples, and by emphasizing PowerShell as a primary automation method. The initial example for registering the resource provider is given in PowerShell, and the portal instructions implicitly assume a Windows-centric workflow. There is no mention of Linux-specific shell usage, nor are there any Bash or Linux-native tool examples. The CLI section is present but appears after PowerShell, reinforcing the Windows-first approach.
Recommendations
- Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid implying Windows as the default platform.
- Include explicit Bash or Linux shell examples where relevant, especially for scripting scenarios.
- Clarify that Azure CLI works natively on Linux, macOS, and Windows, and provide links to installation guides for all platforms.
- Avoid referring to PowerShell as the default or primary automation tool; instead, present both PowerShell and CLI as equal options.
- Add notes or sections for Linux users, such as troubleshooting tips or environment setup guidance.
Firewall
Deploy Azure Firewall with Availability Zones
...ticles/firewall/deploy-availability-zone-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for configuring Azure Firewall with Availability Zones, with no equivalent examples for Linux-oriented tools such as Azure CLI or ARM templates. The use of PowerShell commands and the absence of Linux-native instructions or parity in example order may hinder accessibility for users on Linux or macOS platforms.
Recommendations
- Add Azure CLI examples for all PowerShell instructions, ensuring Linux users have direct guidance.
- Include ARM template snippets for declarative deployments, which are platform-agnostic.
- Present CLI and template examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Explicitly mention cross-platform support and provide links to relevant Linux/macOS setup guides.
- Review and update documentation to ensure all referenced tools and patterns are accessible from non-Windows environments.
Firewall
Deploy and configure Azure Firewall using Azure CLI
...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server images for virtual machines, referencing Remote Desktop for connectivity, and providing only PowerShell-based test commands. There are no Linux VM deployment examples, no SSH or Linux command-line test instructions, and no mention of Linux tools or workflows. Windows-centric patterns (RDP, PowerShell, Windows VM images) are presented as the default or only option.
Recommendations
- Add parallel examples for deploying Linux VMs (e.g., using Ubuntu or CentOS images) alongside Windows VM instructions.
- Include SSH-based connectivity instructions for Linux VMs, in addition to Remote Desktop for Windows.
- Provide Linux shell commands (e.g., dig, curl, wget) for testing DNS and HTTP connectivity through the firewall.
- Mention Linux tools and workflows where relevant, and clarify that the Azure CLI works cross-platform.
- Consider reordering or balancing examples so that Linux and Windows approaches are presented with equal prominence.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides configuration examples for Azure Firewall DNS settings using Azure Portal, Azure CLI, and Azure PowerShell. PowerShell examples are given equal prominence as CLI, but there are no Linux-specific shell (e.g., Bash) or automation examples, nor are Linux-native tools or patterns mentioned. The CLI examples use Azure CLI, which is cross-platform, but the documentation and custom tags (e.g., 'devx-track-azurepowershell') suggest a Windows/PowerShell-centric approach. There is no mention of Linux-specific considerations, such as using cloud-init, systemd-resolved, or resolv.conf for VM DNS configuration, nor are Linux command-line tools (like nmcli or netplan) referenced for updating DNS settings on VMs.
Recommendations
- Add Linux/Bash shell examples for configuring DNS settings on VMs, such as using cloud-init, netplan, or nmcli.
- Include instructions or references for updating DNS settings on Linux VMs (e.g., modifying /etc/resolv.conf or using systemd-resolved).
- Balance PowerShell and CLI examples with Linux-native tooling and automation approaches.
- Explicitly mention that Azure CLI is cross-platform and provide guidance for Linux users where VM-level DNS configuration is required.
- Review and update custom tags to avoid suggesting PowerShell as the primary automation method.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by prominently featuring Azure PowerShell cmdlets in a dedicated section, referencing PowerShell in metadata, and mentioning Azure PowerShell alongside CLI and templates when discussing automation. There are no equivalent Azure CLI or Bash examples, nor are Linux-specific tools or workflows highlighted. The ordering and emphasis suggest a preference for Windows/PowerShell tooling over Linux alternatives.
Recommendations
- Add a section listing equivalent Azure CLI commands for managing IP Groups, with links to relevant documentation.
- Provide example workflows using Bash or shell scripting for Linux users, especially for automation and DevOps scenarios.
- Ensure that references to PowerShell are balanced with references to CLI and REST API throughout the documentation.
- Update metadata to include CLI and Linux tracks, not just PowerShell.
- Where possible, present CLI and PowerShell examples side-by-side to improve parity and accessibility for users on all platforms.
Firewall
Azure Firewall Explicit proxy (preview)
...ure-docs/blob/main/articles/firewall/explicit-proxy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page shows Windows bias by referencing Azure PowerShell for deployment instructions and omitting Linux-specific examples or tools. There are no examples using Azure CLI, Bash, or Linux-native configuration methods, and PowerShell is mentioned as the primary deployment approach.
Recommendations
- Add deployment instructions using Azure CLI and Bash scripts alongside PowerShell.
- Include examples of configuring proxy settings on popular Linux browsers and applications.
- Reference Linux-native tools for uploading PAC files (e.g., using azcopy or Azure CLI).
- Ensure parity in screenshots and step-by-step guides for both Windows and Linux environments.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only a PowerShell example for command-line configuration, mentioning Azure PowerShell before other automation options, and omitting equivalent Linux/CLI examples (such as Azure CLI or Bash). This prioritizes Windows-centric tools and workflows, potentially disadvantaging users on Linux or macOS platforms.
Recommendations
- Add an Azure CLI example for configuring prescaling, using Bash syntax, to provide parity for Linux/macOS users.
- Mention Azure CLI as a configuration option alongside PowerShell, ARM templates, and Bicep in the 'Configuration options' section.
- Ensure that automation and scripting examples are provided for both Windows (PowerShell) and cross-platform (Azure CLI) environments.
- Consider including notes or links for users on Linux/macOS about how to perform equivalent tasks.
Firewall
Scale SNAT ports with Azure NAT Gateway
...b/main/articles/firewall/integrate-with-nat-gateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by presenting Azure PowerShell examples first, which are typically used on Windows systems. There is no mention of Linux-specific tools or patterns (such as Bash scripting or cloud-init), nor are there any Linux shell examples. The CLI example is provided, but only after the PowerShell example, and there is no explicit guidance for Linux users or mention of Linux environments.
Recommendations
- Alternate the order of examples, sometimes presenting Azure CLI (which is cross-platform and commonly used on Linux) before PowerShell.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide context for Linux users.
- Include Bash script examples or references to Linux-native automation tools where appropriate.
- Add a note or section about running these steps in Linux environments, including installation or environment setup tips for Azure CLI on Linux.
- Where PowerShell is used, clarify its availability on Linux and macOS, or provide equivalent Bash commands if possible.
Firewall
Quickstart: Create an Azure Firewall and IP Groups - Resource Manager template
...ain/articles/firewall/quick-create-ipgroup-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively providing a PowerShell example for resource cleanup (Remove-AzResourceGroup) and omitting equivalent instructions for Linux users (such as Azure CLI or Bash). No Linux shell commands or cross-platform alternatives are presented for managing resources, and the only explicit tooling guidance is Windows-centric.
Recommendations
- Add equivalent Azure CLI or Bash commands for resource group deletion, such as 'az group delete --name <your resource group name>'.
- Where PowerShell is used, provide cross-platform alternatives and clarify which platforms each command applies to.
- Include a note or section addressing Linux/macOS users, with instructions tailored to their environments.
- Review other command-line examples to ensure parity between Windows and Linux tooling throughout the documentation.
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through the exclusive mention of Azure PowerShell cmdlets (e.g., Set-AzFirewallPolicy) as workarounds, without providing equivalent Azure CLI or REST API examples. There is also a lack of Linux-specific guidance or parity in tooling references, and no examples are given for Linux shell usage or cross-platform CLI commands. The documentation assumes familiarity with PowerShell and Windows-centric tools, omitting Linux-first or cross-platform alternatives.
Recommendations
- Provide equivalent Azure CLI and REST API examples alongside PowerShell cmdlets for all operations, especially for tasks like updating firewall policy tags.
- Explicitly mention cross-platform tools and usage patterns, such as Bash shell commands or Linux-native utilities, where relevant.
- Ensure that mitigation steps and workarounds do not assume PowerShell as the default, and offer parallel instructions for Linux users.
- Review all troubleshooting and configuration guidance to include both Windows and Linux perspectives, ensuring parity in documentation.
- Add a section or note clarifying that all operations can be performed from Linux, macOS, and Windows, and link to platform-specific guides as appropriate.