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 1-25 of 332 flagged pages
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 Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation is strongly biased toward Windows environments, assuming the use of Active Directory, Windows Server, and Windows-specific tools (certtmpl.msc, Internet Explorer, Internet Options, Windows certificate export wizard). No Linux or cross-platform alternatives are mentioned for certificate creation, request, or export. The prerequisites and workflow are tightly coupled to Windows infrastructure, making it difficult for Linux/macOS users to follow or replicate the process.
Recommendations
- Provide equivalent steps for Linux/macOS environments, such as using OpenSSL for certificate creation and export.
- Mention cross-platform certificate authorities and workflows (e.g., using OpenSSL, cfssl, or other PKI tools).
- Include examples for requesting and exporting certificates via command line or browser-agnostic methods.
- Clarify which steps are Windows-specific and offer alternatives where possible.
- Reorder examples so that platform-neutral or Linux/macOS methods are presented alongside or before Windows-specific instructions.
Create Pull Request
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, especially in the manual migration section, where all command-line examples and scripts are provided exclusively in PowerShell. There are no CLI/bash examples, and the only automation tooling mentioned outside PowerShell is Terraform (which is cross-platform but not shown in detail). The prerequisites and troubleshooting sections also reference PowerShell modules and commands without Linux/macOS alternatives. The order of presentation consistently puts PowerShell before Terraform, and no Azure CLI or bash examples are provided for Linux/macOS users.
Recommendations
- Add equivalent Azure CLI/bash examples for all PowerShell commands and scripts, especially for manual migration and troubleshooting.
- Explicitly mention that PowerShell Core is available cross-platform, but provide Azure CLI alternatives for users who prefer native Linux/macOS tools.
- In prerequisites, clarify that Azure CLI can be used for Linux/macOS users and provide installation instructions.
- Present Terraform and Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
- Where scripts are provided, offer downloadable bash/CLI scripts for Linux/macOS users.
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 Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments, relying exclusively on Windows-specific tools (certtmpl.msc, Internet Explorer, Active Directory Certification Services) and workflows. There are no Linux/macOS equivalents or alternative instructions provided, making it difficult or impossible for non-Windows users to follow the guide.
Recommendations
- Provide instructions for generating and managing CA certificates using cross-platform tools such as OpenSSL.
- Include Linux/macOS workflows for certificate requests, exports, and imports (e.g., using OpenSSL, certtool, or web interfaces accessible from non-Windows browsers).
- Clarify which steps are strictly Windows-only and offer alternatives or workarounds for Linux/macOS environments.
- Add examples for certificate management using Azure CLI or REST APIs, which are platform-agnostic.
- Reorder examples so that platform-neutral or Linux/macOS instructions are presented alongside or before Windows-specific steps.
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing 'PowerShell' before 'CLI' in the management integration section, suggesting a Windows-first approach. There is no mention of Linux-specific tools or examples, and the reference to 'PowerShell' without specifying cross-platform compatibility may mislead users into thinking Windows is required. No Linux shell examples (such as Bash) or explicit parity with Linux management tools are provided.
Recommendations
- Clarify that Azure CLI and PowerShell are both cross-platform, and provide explicit examples for both Windows (PowerShell) and Linux (Bash/CLI).
- List management tools in a neutral order (e.g., 'REST/CLI/PowerShell/templates/Terraform') or alternate the order in different sections.
- Add a note or section highlighting Linux compatibility and usage patterns, including links to Linux-specific deployment guides.
- Provide example commands for both PowerShell and Bash/CLI in relevant sections to ensure parity.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by prominently listing Azure PowerShell cmdlets for managing IP Groups, referencing PowerShell in metadata, and providing no equivalent Azure CLI or REST API command references or examples. The 'Related Azure PowerShell cmdlets' section is detailed, while Linux-friendly tools (Azure CLI, REST API) are only mentioned generically earlier in the text and not given parity in example or reference. This may make Linux users feel secondary or unsupported.
Recommendations
- Add a 'Related Azure CLI commands' section with equivalent az network ip-group commands and links.
- Provide REST API references or example calls for IP Group management.
- Ensure examples and step-by-step instructions are given for both Azure CLI and PowerShell, ideally side-by-side.
- Remove or balance metadata tags (e.g., devx-track-azurepowershell) to include CLI and REST API.
- When listing tools or commands, mention Azure CLI and REST API before or alongside PowerShell to avoid Windows-first impression.
Firewall
FQDN tags overview for Azure Firewall
...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Heavy
Summary
The documentation page demonstrates a Windows bias by predominantly referencing Windows services (e.g., Windows Update, Windows Diagnostics, Windows Virtual Desktop, Windows 365) and providing examples and tags related to Windows-centric scenarios. There are no explicit examples or mentions of Linux-specific services or endpoints, nor are Linux equivalents to the Windows tags discussed. The order and focus of examples and tags prioritize Windows use cases, with little to no attention given to Linux or cross-platform needs.
Recommendations
- Include examples of FQDN tags relevant to Linux services (e.g., Azure Linux VM management, Linux-based update services, SSH endpoints).
- Add documentation or references for managing outbound traffic for Linux-based workloads and applications.
- Balance the order and prominence of examples to include both Windows and Linux scenarios, ensuring parity.
- Explicitly mention whether FQDN tags can be used for common Linux management endpoints or third-party Linux services.
- Provide guidance or links for Linux administrators on configuring Azure Firewall for Linux-centric environments.
Firewall
Customer provided public IP address support in secured hubs
...in/articles/firewall/secured-hub-customer-public-ip.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 command-line configuration, with no equivalent instructions for Linux users (e.g., Azure CLI or Bash). Windows tools and patterns (PowerShell cmdlets) are mentioned exclusively and repeatedly, and the portal instructions are generic, not platform-specific. There is no mention of Linux or cross-platform command-line usage, nor are Linux-friendly tools or examples provided.
Recommendations
- Add Azure CLI (az) examples alongside PowerShell for all configuration steps, ensuring Linux and macOS users have parity.
- Explicitly mention that both PowerShell and Azure CLI are supported, and link to cross-platform installation guides.
- Where possible, provide Bash script examples for automation scenarios.
- Review and update screenshots or UI instructions to clarify platform neutrality.
- Include a note on platform compatibility for all tools and commands referenced.
Firewall
Deploy and configure Azure Firewall in a hybrid network by using the Azure portal
.../blob/main/articles/firewall/tutorial-hybrid-portal.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 for all VM examples, providing only PowerShell commands for configuration (specifically for IIS installation), and omitting any Linux VM or Bash/CLI examples. The instructions for deploying workload and on-premises VMs are Windows-centric, and the only automation example uses PowerShell, with no mention of Linux alternatives or parity.
Recommendations
- Include parallel instructions for deploying Linux-based VMs (e.g., Ubuntu) in both the spoke and on-premises networks.
- Provide examples for installing a web server (e.g., Apache or Nginx) on Linux VMs using Bash or Azure CLI.
- Offer equivalent automation commands using Azure CLI and Bash, not just PowerShell.
- Explicitly mention that the firewall and network setup applies equally to Linux workloads, and highlight any OS-agnostic aspects.
- Add troubleshooting and testing steps for Linux VMs (e.g., SSH access, curl to test web server) alongside the Windows RDP and browser tests.
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 by providing extensive PowerShell-based instructions and scripts for Azure Firewall SKU changes and migrations, with no equivalent examples for Linux shell environments (e.g., Bash, Azure CLI). Windows tools and patterns (PowerShell modules, cmdlets) are mentioned exclusively and in detail, while Linux-native tools or cross-platform alternatives are absent. The ordering and emphasis on PowerShell further reinforce the Windows-first approach.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, ensuring Linux and macOS users have clear, tested instructions.
- Include Bash script samples for migration and policy transformation tasks, especially for steps currently covered only by PowerShell scripts.
- Explicitly mention cross-platform compatibility for all tooling and clarify which steps can be performed from Linux/macOS environments.
- Add troubleshooting and validation steps using Azure CLI, not just PowerShell.
- Review and update prerequisites to reference both PowerShell and Azure CLI, and link to installation guides for each on all platforms.
- Consider reordering sections to present cross-platform or Azure CLI methods before or alongside PowerShell, rather than PowerShell-first.
Firewall
Deploy Azure Firewall with Availability Zones
...ticles/firewall/deploy-availability-zone-powershell.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 exclusively providing Azure PowerShell examples for deploying Azure Firewall with Availability Zones. There are no CLI (az), Bash, or Linux-oriented instructions, and PowerShell is mentioned as the primary scripting/deployment method. Windows tools and patterns are referenced without Linux or cross-platform alternatives, making the instructions less accessible to users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands to ensure cross-platform accessibility.
- Explicitly mention that deployment can be performed from Linux/macOS using Azure CLI or REST API.
- Provide Bash script examples where appropriate.
- Reorder sections so that cross-platform methods (Azure CLI, REST API) are presented before or alongside PowerShell.
- Clarify that PowerShell is not required and highlight platform-agnostic options.
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
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows-based VM images (win2016datacenter), referencing Remote Desktop for connectivity, and providing only PowerShell-based test commands. There are no Linux VM deployment examples, no SSH connectivity instructions, and no Linux shell command equivalents for testing firewall rules. Windows tools and patterns are mentioned exclusively, with no Linux parity.
Recommendations
- Include Linux VM deployment examples (e.g., using Ubuntu or CentOS images) alongside Windows examples.
- Provide instructions for connecting to Linux VMs using SSH, in addition to Remote Desktop for Windows.
- Add Linux shell command equivalents for firewall testing, such as using 'dig', 'nslookup', 'curl', or 'wget' in Bash.
- Mention both Windows and Linux administrative patterns/tools when discussing VM setup and connectivity.
- Ensure that examples and instructions are presented in a cross-platform manner, or clearly indicate platform-specific steps.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific features (e.g., Windows Update FQDN tag) and listing PowerShell as a primary management tool before CLI and other cross-platform options. Windows tools and terminology are mentioned without equal Linux-specific examples, and there are no explicit Linux-focused usage scenarios or references to Linux equivalents for features like service tags or DevOps integration.
Recommendations
- Include Linux-focused examples and references, such as using Linux update repositories in FQDN tags (e.g., Ubuntu, Red Hat, CentOS).
- List Azure CLI and Terraform before or alongside PowerShell when mentioning DevOps integration to emphasize cross-platform parity.
- Provide explicit examples or scenarios for managing Azure Firewall from Linux environments, including shell scripts and CLI commands.
- Mention Linux-specific network management patterns or tools where relevant, such as integration with Linux-based SIEM solutions.
- Balance references to Windows-centric features (like Windows Update) with equivalent Linux features to avoid implying Windows is the primary or default platform.
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 demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. The Azure portal and PowerShell are introduced first, with PowerShell examples provided before Azure CLI. The only scripting example in the initial registration step is PowerShell, and references to 'Get started with Azure PowerShell' appear before 'Get started with Azure CLI'. There is no mention of Linux-specific tools, shell environments, or guidance for Linux users. The screenshots and step-by-step instructions are tailored to the Azure portal, which is platform-agnostic but often associated with Windows workflows. The CLI section is present but appears after PowerShell, reinforcing a Windows-first approach.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to ensure equal visibility for Linux and cross-platform users.
- Include explicit references to Linux environments (e.g., bash, zsh) and clarify that Azure CLI commands work natively on Linux, macOS, and Windows.
- Add notes or sections for Linux users, such as installation guidance for Azure CLI on Linux, and troubleshooting tips for common Linux scenarios.
- Avoid using PowerShell as the default or only scripting example in introductory steps; provide parallel examples for Azure CLI.
- Ensure that any screenshots or UI instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or terminology).
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 its example environment, omitting any mention of Linux VM options. Additionally, cleanup instructions only provide a PowerShell command, with no equivalent Bash or Azure CLI example for Linux users. The documentation does not reference Linux tools or patterns, nor does it offer parity in examples or instructions for non-Windows platforms.
Recommendations
- Include options in the ARM template and documentation to deploy Linux-based virtual machines alongside or instead of Windows Server VMs.
- Provide cleanup instructions using Azure CLI (az group delete) and Bash, in addition to PowerShell, to support Linux and cross-platform users.
- Explicitly mention that both Windows and Linux VMs can be used in the test environment, and link to relevant guidance for deploying each.
- Ensure that examples and tooling references are balanced between Windows and Linux, or presented in a platform-neutral way.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides configuration examples using Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell examples are Windows-centric and presented equally alongside CLI, with no mention of Linux-specific tools, shell patterns, or guidance for Linux users. There are no bash or Linux shell script examples, nor references to Linux-native DNS management tools or patterns. The documentation assumes familiarity with PowerShell and Windows conventions, and does not address Linux-specific considerations for DNS or VM configuration.
Recommendations
- Add bash/Linux shell script examples for all CLI operations, especially for updating DNS settings and enabling DNS proxy.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if needed (e.g., environment variables, file paths).
- Include guidance for Linux VM DNS configuration, such as updating /etc/resolv.conf or using cloud-init for DNS settings.
- Reference Linux-native DNS troubleshooting tools (e.g., dig, nslookup, systemd-resolved) in relevant sections.
- Clarify any differences in DNS behavior or VM restart requirements between Windows and Linux guests.
- Balance PowerShell examples with bash equivalents, or provide a tabbed interface for bash, PowerShell, and CLI where appropriate.
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 demonstrates Windows bias by referencing Azure PowerShell as the primary method for deploying and configuring Azure Firewall, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI or Bash). No Linux-specific tools, commands, or examples are provided, and the only deployment link is to a PowerShell-based workflow.
Recommendations
- Add equivalent deployment and configuration instructions using Azure CLI (az commands), which are cross-platform and commonly used on Linux and macOS.
- Include examples and screenshots for configuring explicit proxy settings from Linux environments, such as using curl or wget with proxy settings.
- Reference Bash scripting or Linux-native tools for uploading PAC files and generating SAS URLs, in addition to PowerShell.
- Provide links to documentation for deploying Azure Firewall using methods other than PowerShell, such as via the Azure Portal or ARM templates.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell as a configuration method for certain features, without mentioning equivalent Linux-friendly tools (such as Azure CLI or ARM templates). No Linux-specific examples or instructions are provided, and the only command-line tool referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI examples alongside PowerShell for all configuration steps, especially for enabling features and deploying resources.
- Explicitly mention cross-platform tools (e.g., Azure CLI, ARM templates, Terraform) when describing configuration options.
- Add Linux-specific instructions or notes where relevant, ensuring parity for administrators working on non-Windows systems.
- Review all references to PowerShell and ensure they are balanced with equivalent Linux-compatible alternatives.
Firewall
Azure Firewall IDPS signature rule categories
...ob/main/articles/firewall/idps-signature-categories.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Several categories (ActiveX, Exploit, Web Server) mention Microsoft/Windows technologies (ActiveX, Windows exploits, IIS) explicitly, while Linux equivalents (e.g., Linux-specific exploits, Apache, NGINX) are mentioned but not given equal prominence or detail. There are no code examples, but the pattern of listing Windows technologies first or exclusively is present. No Linux-specific tools or attack vectors are highlighted, and Linux is not referenced in the context of exploits or vulnerabilities except as part of a list. There are no PowerShell examples, but the overall framing is more Windows-centric.
Recommendations
- Ensure Linux technologies (e.g., Linux kernel exploits, Samba, Linux-specific vulnerabilities) are mentioned with equal detail and prominence as Windows equivalents.
- When listing categories or examples, alternate or balance the order between Windows and Linux technologies to avoid 'Windows first' bias.
- Add explicit references to Linux attack vectors and tools where relevant (e.g., mention Linux-specific web servers, desktop environments, or protocols).
- Include examples or notes for both Windows and Linux environments when discussing exploits, vulnerabilities, or detection logic.
- Review and update category descriptions to ensure parity in coverage of both Windows and Linux platforms.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for firewall stop/start and allocation operations, with no equivalent Azure CLI (cross-platform) or Bash examples. The use of PowerShell cmdlets and syntax is exclusive, and there is no mention of Linux-native tools or workflows. All command-line instructions assume a Windows/PowerShell environment, which may disadvantage Linux or macOS users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux and macOS users can follow the instructions without needing PowerShell.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to relevant cross-platform tool documentation.
- Where screenshots or instructions reference the Azure portal, clarify that the portal is accessible from any OS.
- Review all command-line instructions to ensure parity between Windows and Linux environments, including Bash syntax where appropriate.
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 mild Windows bias, primarily through references to PowerShell cmdlets (e.g., Set-AzFirewallPolicy) as the only example for updating firewall policy tags, without mentioning equivalent Azure CLI or REST API commands. There is also a lack of Linux-specific or cross-platform examples for common administrative tasks, and Windows tooling (PowerShell) is mentioned exclusively in mitigation steps. No explicit Linux commands, Bash, or platform-neutral instructions are provided for these operations.
Recommendations
- Provide Azure CLI and REST API examples alongside PowerShell cmdlets for all management operations, especially for updating firewall policy tags.
- Include platform-neutral instructions or Bash/Linux command equivalents where possible.
- Explicitly state cross-platform support and parity for all features and management tasks.
- Review mitigation steps and ensure that Linux users are not excluded from guidance, especially in sections referencing command-line tools.
- Add a note or table summarizing which management operations can be performed via PowerShell, CLI, REST API, and Portal, with links to relevant documentation for each platform.
Firewall
Access a storage account using SFTP over an Azure Firewall static public IP address
...zure-docs/blob/main/articles/firewall/firewall-sftp.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
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 tools. All code samples are in PowerShell, and there are no alternative instructions or examples for Linux users. The only SFTP client example is generic, but the overall workflow assumes a Windows/PowerShell environment.
Recommendations
- Provide equivalent Azure CLI (az) commands for all deployment and configuration steps alongside PowerShell examples.
- Include Bash script samples for Linux users where appropriate.
- Explicitly mention that the SFTP client example works on Linux, macOS, and Windows, and provide sample commands for each platform.
- Add notes or sections on how to install and use Azure CLI on Linux and macOS.
- Ensure that prerequisites and setup steps do not assume PowerShell as the default shell, and offer alternatives for Linux users.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and references before CLI and ARM template examples. The PowerShell section is more extensive, including both deployment and update scenarios, while the Azure CLI section is brief and lacks update instructions. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. The CLI instructions are generic and do not address Linux nuances, and PowerShell is presented as the primary method for configuration.
Recommendations
- Add explicit bash shell examples for Azure CLI commands, including both deployment and update scenarios.
- Ensure CLI instructions are as detailed as PowerShell, covering all relevant operations (e.g., updating an existing firewall).
- Present CLI and ARM template examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Mention cross-platform compatibility for CLI commands and clarify that PowerShell examples are primarily for Windows users.
- Include notes or links for Linux users regarding installation and usage of Azure CLI and ARM templates.
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 a Windows bias by presenting Azure PowerShell examples first, followed by Azure CLI. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux tools or patterns. The use of PowerShell as the primary example may disadvantage Linux users, who are more likely to use Bash or other shell environments.
Recommendations
- Add Bash shell examples for Linux users, especially for Azure CLI commands.
- Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any platform-specific notes if relevant.
- If there are platform-specific considerations (e.g., file paths, environment variables), highlight them for both Windows and Linux.
- Include a note or section on how Linux users can install and use Azure CLI and interact with Azure resources.
Firewall
Monitoring data reference for Azure Firewall
...b/main/articles/firewall/monitor-firewall-reference.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias, particularly in sections describing how to enable and configure logging features for Azure Firewall. All command-line examples use Azure PowerShell, with no Bash/CLI or Linux-native alternatives provided. The instructions assume the use of PowerShell and Windows-centric tooling, and do not mention or prioritize cross-platform options such as Azure CLI, Bash, or automation via REST API. This may hinder Linux users or those working in non-Windows environments from easily following the guidance.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all configuration and log enablement steps.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
- Add Bash script examples for common tasks such as enabling/disabling logs and checking registration status.
- Reference REST API methods for advanced users who may wish to automate these tasks outside of PowerShell.
- Reorder instructions to present cross-platform (CLI, REST) options before or alongside PowerShell, rather than PowerShell-only.
- Include a note or table comparing PowerShell and CLI commands for parity, helping users choose the best tool for their environment.
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page displays a moderate Windows bias. It references Windows-centric tools (Excel, Power BI, Visual Studio, C# log converter), and instructs users to configure certain features (Fat Flow Log) via Azure PowerShell only, without mentioning Linux alternatives or CLI equivalents. Windows tools are mentioned before any cross-platform or Linux-friendly options, and there are no Linux-specific examples or guidance for log conversion, viewing, or automation. No Bash, Azure CLI, or open-source tool examples are provided.
Recommendations
- Add Azure CLI and Bash examples for configuring diagnostic settings and enabling features such as Fat Flow Log, alongside or before PowerShell instructions.
- Mention open-source and cross-platform log analysis tools (e.g., jq, pandas, Grafana) for viewing and processing logs, not just Excel or Power BI.
- Provide sample scripts or commands for Linux environments to download, convert, and analyze logs.
- Reference editors and development environments available on Linux (e.g., VS Code, JetBrains IDEs) when discussing log conversion tools.
- Ensure all tooling and automation instructions are platform-neutral or offer parity for Linux users.