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 176-200 of 332 flagged pages
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal-policy.md
...ain/articles/firewall/tutorial-hybrid-portal-policy.md
High Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-hybrid-portal.md
.../blob/main/articles/firewall/tutorial-hybrid-portal.md
High Priority
View Details →
Detected Bias Types
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.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is generally cross-platform and focuses on Azure portal and Kusto queries, which are platform-agnostic. However, there is a notable bias in the section about enabling the Azure Firewall Fat Flow Log (Top flow log), which states that configuration must be done through Azure PowerShell, with no mention of Azure CLI or Bash alternatives. Additionally, the tip about log converter tools references Visual Studio and C#, which are traditionally Windows-centric, without suggesting Linux/macOS alternatives.
Recommendations
- Provide Azure CLI or REST API instructions for enabling Fat Flow Log, or clarify if PowerShell is the only supported method.
- Mention cross-platform code editors (such as VS Code) and .NET Core for log converter tools, or provide equivalent tools/scripts for Linux/macOS users.
- Where PowerShell is referenced, add notes about installation and usage on Linux/macOS, or link to relevant cross-platform documentation.
- Ensure that all example workflows (such as downloading and converting logs) include Linux/macOS-friendly tools (e.g., jq, csvkit, pandas) alongside Excel and Power BI.
Firewall
Deploy Azure Firewall with Availability Zones
...ticles/firewall/deploy-availability-zone-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only Azure PowerShell examples for deploying Azure Firewall with Availability Zones, without any equivalent examples for Azure CLI, ARM templates, or Bicep. This creates friction for Linux/macOS users, who typically use Azure CLI or template-based deployments rather than PowerShell. The exclusive use of PowerShell commands and lack of cross-platform guidance is a notable bias.
Recommendations
- Add Azure CLI examples for deploying Azure Firewall with Availability Zones, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include ARM template and/or Bicep deployment examples to provide platform-agnostic, infrastructure-as-code options.
- Clearly indicate that PowerShell is just one of several supported methods and link to documentation for other deployment approaches.
- Consider reordering or presenting examples for CLI and templates before or alongside PowerShell to signal equal support.
Firewall
Deploy Azure Firewall with Availability Zones
...ticles/firewall/deploy-availability-zone-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a detailed Azure PowerShell example for configuring Availability Zones in Azure Firewall, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, ARM templates, or REST API). The only command-line deployment method shown is PowerShell, which is primarily a Windows tool, creating friction for users on other platforms.
Recommendations
- Add Azure CLI examples for configuring Availability Zones in Azure Firewall.
- Include ARM template or REST API sample payloads for cross-platform automation.
- Explicitly mention that Azure CLI and REST API can be used from Linux/macOS and provide links or code samples.
- Where PowerShell is referenced, clarify its cross-platform availability, or suggest alternatives for non-Windows users.
Medium 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 exclusively provided in PowerShell, with no Bash, Azure CLI, or Linux/macOS shell equivalents. The manual migration steps, troubleshooting, and validation procedures rely entirely on PowerShell cmdlets and scripting, which are native to Windows. There is no mention of how to perform these tasks using cross-platform tools, and PowerShell is referenced as a prerequisite. This creates friction for Linux/macOS users, who may not have PowerShell installed or prefer using Bash/Azure CLI.
Recommendations
- Add equivalent Azure CLI and Bash examples for all PowerShell commands and scripts.
- Explicitly mention that PowerShell Core is available cross-platform, and provide installation guidance for Linux/macOS users.
- Reorder example sections to present Azure portal and cross-platform CLI methods before PowerShell, or side-by-side.
- Include troubleshooting and validation steps using Azure CLI or REST API where possible.
- Clarify which steps are platform-agnostic (e.g., Azure portal, Terraform) and which require Windows-specific tooling.
Firewall
Quickstart: Create an Azure Firewall with Availability Zones - Bicep
...azure-docs/blob/main/articles/firewall/deploy-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively deploying Windows Server virtual machines in the example environment and not mentioning Linux VM options. While the deployment and management steps use cross-platform Azure CLI and PowerShell, the example infrastructure is Windows-centric, which may discourage or confuse Linux users.
Recommendations
- Include examples or notes on deploying Linux virtual machines alongside or instead of Windows Server VMs in the Bicep template.
- Clarify that the jump box and server VMs can be Linux-based and provide sample parameters or template snippets for Linux VM deployment.
- Add a section or sidebar discussing considerations for Linux users, such as SSH access and Linux VM images.
- Ensure parity in documentation by alternating or balancing Windows and Linux examples where applicable.
Firewall
Deploy and configure Azure Firewall using Azure CLI
...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias. All VM creation examples use Windows images (win2016datacenter), and the testing section instructs users to connect via Remote Desktop and run PowerShell commands, with no mention of Linux VM images, SSH, or Linux shell equivalents. There are no Linux/macOS-specific instructions or examples for testing firewall rules, and Windows-centric tools (RDP, PowerShell) are assumed throughout.
Recommendations
- Include examples for creating Linux VMs (e.g., using Ubuntu images) alongside Windows VM instructions.
- Provide SSH connection instructions for Linux/macOS users, rather than only Remote Desktop.
- Offer Linux shell command equivalents for PowerShell commands used in testing (e.g., using curl, wget, dig, or nslookup in bash).
- Explicitly state that the Azure CLI commands work cross-platform, and highlight any OS-specific considerations.
- Reorder or parallelize instructions so that Linux and Windows options are presented equally.
Firewall
Quickstart: Create an Azure Firewall with Availability Zones - Resource Manager template
...re-docs/blob/main/articles/firewall/deploy-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively deploying Windows Server VMs in the example template, referencing Windows-specific administration patterns, and providing only PowerShell commands for resource cleanup. There are no Linux VM deployment options, nor are Linux/macOS command-line alternatives (such as Azure CLI or Bash) provided for post-deployment management.
Recommendations
- Include options in the ARM template and documentation to deploy Linux VMs alongside or instead of Windows Server VMs.
- Provide equivalent Azure CLI and Bash commands for resource cleanup and other management tasks, not just PowerShell.
- Explicitly mention that the template can be customized for Linux workloads, and link to relevant Linux VM documentation.
- Add examples or notes for Linux/macOS users, such as how to connect to deployed VMs or manage resources from non-Windows platforms.
Firewall
Deploy & configure Azure Firewall Basic and policy using the Azure portal
...ticles/firewall/deploy-firewall-basic-portal-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively uses Windows Server as the example workload VM and only demonstrates remote desktop (RDP) access and Internet Explorer for testing, both of which are Windows-specific. There are no Linux VM deployment instructions, nor are SSH or Linux browser testing steps provided. This creates friction for Linux users who wish to follow the guide.
Recommendations
- Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
- Include SSH access setup and DNAT rule examples for Linux VMs.
- Provide Linux-specific testing steps, such as using Firefox/Chrome or command-line tools (curl, dig) to verify firewall rules.
- Mention that the firewall configuration applies equally to Linux and Windows workloads, and clarify any OS-specific differences.
- Show both RDP (Windows) and SSH (Linux) DNAT rule examples side-by-side.
Firewall
Quickstart: Create an Azure Firewall with Availability Zones - Terraform
...e-docs/blob/main/articles/firewall/deploy-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively deploys Windows Server virtual machines in the example environment and only provides instructions for creating Azure Windows VMs. There are no examples or mentions of deploying Linux VMs, nor is there guidance for Linux-specific configuration or parity. This creates a bias toward Windows environments and may exclude users who wish to deploy Linux-based infrastructure.
Recommendations
- Include examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
- Provide sample Terraform code for both Windows and Linux VM deployment, or offer a choice in the walkthrough.
- Mention Linux VM options and any differences in configuration, such as SSH key setup versus password authentication.
- Clarify that the firewall and network setup is OS-agnostic, and highlight how to adapt the steps for Linux users.
Firewall
Azure Firewall Draft + Deployment (preview)
...azure-docs/blob/main/articles/firewall/draft-deploy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides detailed examples for Azure Portal, Azure CLI, and Azure PowerShell. The PowerShell section is extensive and uses Windows-specific cmdlets, which are not natively available on Linux/macOS. PowerShell is presented as a primary automation method alongside CLI, and there is no mention of Bash, shell scripting, or Linux-native tools. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is given equal prominence and detail, reinforcing a Windows-centric approach.
Recommendations
- Clarify that PowerShell examples require PowerShell Core for cross-platform use, or provide equivalent Bash/shell script examples for Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and consider showing CLI examples before PowerShell to reduce perceived Windows-first bias.
- Add troubleshooting or environment setup notes for Linux/macOS users, especially regarding PowerShell compatibility and installation.
- Include links or references to Linux/macOS documentation for Azure Firewall management where available.
Firewall
Azure Firewall Explicit proxy (preview)
...ure-docs/blob/main/articles/firewall/explicit-proxy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell as the primary deployment method in the 'Next steps' section, without mentioning equivalent Linux/macOS CLI options. No Linux-specific tools or examples are provided, and PowerShell is highlighted before any cross-platform alternatives.
Recommendations
- Include Azure CLI deployment instructions alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Add examples or notes for configuring proxy settings on browsers and applications in Linux/macOS environments.
- Reference Linux/macOS tools and workflows where relevant, such as using curl or wget for PAC file testing.
- Ensure that links to deployment guides include both PowerShell and Azure CLI options.
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page contains a few instances of Windows bias, notably referencing Azure PowerShell cmdlets (e.g., Set-AzFirewallPolicy) as the workaround for adding tags, and mentioning PowerShell and CLI support for ICMP as a known issue. There are no explicit Linux or macOS tool examples, and the only command-line tool mentioned is PowerShell, which is traditionally associated with Windows. No Linux-specific tools or patterns (such as Azure CLI, Bash, or ARM template examples) are provided, and workarounds are described using Windows-centric tooling.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell cmdlet examples, especially for operations like updating tags.
- Explicitly mention cross-platform support for Azure CLI and REST API, and provide examples for Linux/macOS users.
- Where PowerShell is referenced, clarify if the operation can also be performed using Azure CLI, Bash, or ARM templates, and provide those examples.
- Add a note or section on how Linux/macOS users can perform the same tasks, ensuring parity in troubleshooting and configuration guidance.
Firewall
Access a storage account using SFTP over an Azure Firewall static public IP address
...zure-docs/blob/main/articles/firewall/firewall-sftp.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Azure PowerShell for all deployment and configuration steps, with no mention of Azure CLI, Bash, or Linux-native tooling. All code samples use PowerShell syntax, and instructions for installing and using Azure PowerShell are given, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or examples, and the only SFTP client example is generic, but the context and command prompt references suggest a Windows-first perspective.
Recommendations
- Provide equivalent Azure CLI (az) commands for all deployment and configuration steps, as Azure CLI is cross-platform and commonly used on Linux/macOS.
- Include Bash shell examples and instructions for Linux/macOS users, especially for environment setup and authentication.
- Add installation and authentication instructions for Azure CLI, and clarify that Azure PowerShell can be used on Linux/macOS, but CLI is often preferred.
- Explicitly mention that SFTP clients are available on all platforms, and provide example commands for Linux/macOS terminals.
- Reorder or parallelize examples so that Linux/macOS instructions are presented alongside Windows/PowerShell ones, rather than Windows-first.
Firewall
FQDN tags overview for Azure Firewall
...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy Examples
Summary
The documentation page demonstrates a Windows-first bias by focusing examples and FQDN tags primarily on Microsoft Windows services (e.g., Windows Update, Windows Diagnostics, Windows 365, Windows Virtual Desktop). There are no explicit Linux/macOS-specific examples, tags, or references, and the majority of FQDN tags are centered around Windows or Microsoft-centric services. However, there are no PowerShell-only instructions or exclusive references to Windows tools; the bias is more in the service focus and example selection.
Recommendations
- Include examples or references for non-Windows/Microsoft services that may be relevant for Linux/macOS environments (e.g., popular Linux repositories, package managers, or third-party SaaS services).
- Clarify whether FQDN tags can be used for non-Microsoft services or if there are plans to support such scenarios.
- Add a note or section addressing how Linux/macOS administrators can use FQDN tags, or what alternatives exist for their typical outbound traffic needs.
- If possible, provide parity by listing or suggesting FQDN tags that would be useful for Linux/macOS environments.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides deployment and configuration instructions for Azure Firewall FTP support, but all code examples and step-by-step instructions use Azure PowerShell first and in detail, with no explicit Bash/Linux/macOS shell examples. The Azure CLI is mentioned, but only in passing and without a concrete example. There are no instructions or examples for Linux/macOS users, nor is there guidance on using the CLI in those environments.
Recommendations
- Add explicit Bash/Azure CLI examples for enabling Active FTP, including full command sequences.
- Present Azure CLI and ARM template instructions before or alongside PowerShell examples to avoid Windows-first ordering.
- Clarify that Azure CLI can be used cross-platform, and provide guidance for Linux/macOS users.
- Include notes or links for installing and using Azure CLI on Linux/macOS.
- Ensure all configuration steps are covered for both PowerShell and CLI users, with parity in detail.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias by highlighting Azure PowerShell cmdlets as the only explicit command-line tooling for managing IP Groups. The 'Related Azure PowerShell cmdlets' section lists only Windows-centric tools, with no equivalent Azure CLI or bash examples. The custom metadata also references 'devx-track-azurepowershell', further reinforcing a PowerShell/Windows focus. While the main text mentions that IP Groups can be managed via Azure CLI, REST API, and portal, practical examples and links are provided only for PowerShell, and not for Linux-friendly alternatives.
Recommendations
- Add equivalent Azure CLI commands and examples for all PowerShell cmdlets listed.
- Include bash or shell script examples where relevant.
- Provide direct links to Azure CLI documentation for IP Group management.
- Ensure that CLI and REST API usage is demonstrated alongside PowerShell, not just mentioned.
- Review metadata and custom tags to avoid reinforcing PowerShell as the primary track.
Firewall
Monitoring data reference for Azure Firewall
...b/main/articles/firewall/monitor-firewall-reference.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong bias towards Windows and PowerShell. All command-line examples for enabling/disabling logging and feature registration use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the use of PowerShell is assumed throughout. This creates friction for users on Linux or macOS who may prefer or require Azure CLI or Bash scripts.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that Azure CLI and portal can be used for these operations, and link to relevant documentation.
- Add a section or callouts for Linux/macOS users, clarifying any differences or additional steps.
- Where possible, use generic terminology (e.g., 'command line') and avoid assuming PowerShell as the default shell.
- Include Bash script examples for common tasks, especially for enabling/disabling features and configuring diagnostics.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only Azure PowerShell examples for critical firewall management operations (stop/start, allocate IPs), with no equivalent Azure CLI or Bash examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The step-by-step instructions and screenshots are also oriented toward the Azure Portal, which is platform-neutral, but all command-line automation is Windows-focused.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for all management operations (stop/start, allocate IPs, etc.).
- Explicitly mention that both PowerShell and CLI can be used, and link to cross-platform tool documentation.
- Consider showing CLI examples first or side-by-side to avoid implicit Windows-first bias.
- Note any differences or limitations between PowerShell and CLI for these operations.
Firewall
Deploy and configure Azure Firewall Premium
...ure-docs/blob/main/articles/firewall/premium-deploy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing a Windows-based WorkerVM for all testing steps, instructing users to open an 'administrator command prompt' and use a browser on Windows. There are no examples or instructions for deploying or testing with a Linux VM, nor are Linux-specific tools or commands mentioned. The certificate deployment step is also described only for Windows. This creates friction for Linux/macOS users who may wish to follow the guide using their preferred platforms.
Recommendations
- Provide parallel instructions for deploying and configuring a Linux WorkerVM, including certificate installation steps.
- Include Linux/macOS command-line examples (e.g., using bash, terminal) alongside Windows examples.
- Clarify that curl and browser-based tests can be performed on any OS, and provide guidance for Linux/macOS users.
- Mention platform-agnostic approaches for certificate handling and browser configuration.
- Ensure screenshots and UI references are not Windows-specific, or provide alternatives.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a detailed PowerShell example for prescaling configuration, while omitting equivalent CLI or Linux-native examples (such as Azure CLI or Bash). The PowerShell example appears before the Bicep template reference, and there is no mention of Linux/macOS-friendly command-line tools or patterns. This may create friction for users who do not use Windows or PowerShell.
Recommendations
- Add an Azure CLI example for configuring prescaling, using Bash syntax, to ensure Linux/macOS users have a direct, supported method.
- Explicitly mention that Azure CLI and ARM templates can be used from any platform, and provide links or examples.
- Reorder examples so that platform-neutral or cross-platform methods (Azure CLI, ARM/Bicep) appear before or alongside PowerShell.
- Clarify that PowerShell is available cross-platform, but provide syntax for both PowerShell and Bash/CLI where possible.
Firewall
Use Azure Firewall to protect Azure Virtual Desktop
...ain/articles/firewall/protect-azure-virtual-desktop.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently refers to Windows-centric concepts and tools, such as 'WindowsVirtualDesktop' service tags, Windows 365, Intune, and Microsoft Edge proxy configuration. There are no examples or guidance for Linux/macOS session hosts, nor are alternative browser or proxy configuration methods mentioned for non-Windows environments. The focus is on Windows tools and terminology, with no parity for Linux/macOS users.
Recommendations
- Include explicit guidance for Linux/macOS session hosts, if supported by Azure Virtual Desktop.
- Provide proxy configuration examples for browsers commonly used on Linux/macOS (e.g., Firefox, Chrome) in addition to Microsoft Edge.
- Clarify whether Azure Virtual Desktop supports non-Windows session hosts, and if so, document any differences in firewall or proxy configuration.
- Mention Linux/macOS equivalents for network configuration, such as using iptables, ufw, or system proxy settings.
- Avoid using Windows-specific terminology exclusively; use more generic terms where possible.
Firewall
Quickstart: Create an Azure Firewall and IP Groups - Resource Manager template
...ain/articles/firewall/quick-create-ipgroup-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell example for deleting resources (Remove-AzResourceGroup), with no equivalent CLI or Bash example for Linux/macOS users. The use of PowerShell cmdlets and lack of cross-platform alternatives creates friction for non-Windows users.
Recommendations
- Add Azure CLI and/or Bash examples for resource group deletion (e.g., az group delete --name <name> --yes --no-wait).
- Where PowerShell is used, provide equivalent commands for Azure CLI, and note platform compatibility.
- Review other sections for implicit Windows tool usage and ensure parity in instructions for Linux/macOS users.
Firewall
Quickstart: Create an Azure Firewall with multiple public IP addresses - Resource Manager template
...articles/firewall/quick-create-multiple-ip-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by focusing on RDP connections to Windows Server VMs, referencing Azure PowerShell for further deployment instructions, and providing only PowerShell-based cleanup commands. There are no Linux/macOS-specific examples, such as SSH connections or CLI commands, and Windows tools/patterns are mentioned exclusively.
Recommendations
- Include examples for connecting to Linux VMs (e.g., SSH) alongside RDP/Windows examples.
- Provide equivalent Azure CLI commands for resource group deletion and other management tasks.
- Reference documentation for deploying Azure Firewall with multiple public IPs using Azure CLI or Bicep, not just PowerShell.
- Clarify that the template can be used for Linux VMs and provide guidance for those scenarios.