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 151-175 of 332 flagged pages
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-template.md
...articles/firewall/quick-create-multiple-ip-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by focusing on RDP access to Windows Server VMs, referencing PowerShell for resource cleanup, and omitting Linux VM or SSH examples. The only command-line example uses Azure PowerShell, and the workflow assumes Windows-centric tools and patterns.
Recommendations
- Include examples for deploying and accessing Linux VMs (e.g., SSH access) alongside Windows examples.
- Provide equivalent Azure CLI commands for resource management (such as deleting the resource group), not just Azure PowerShell.
- Mention both RDP (for Windows) and SSH (for Linux) as possible ways to connect to backend servers.
- Balance references to Windows and Linux tools and workflows throughout the documentation.
Create Pull Request
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-preview.md
...e-docs/blob/main/articles/firewall/firewall-preview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows environments by referencing Azure PowerShell as a configuration method without mentioning Azure CLI or other cross-platform tools. There are no Linux-specific or cross-platform command examples, and the only tool explicitly mentioned for configuration is Azure PowerShell, which is more commonly associated with Windows environments.
Recommendations
- Include Azure CLI examples alongside or instead of Azure PowerShell for configuration steps, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that configuration can be performed from Linux, macOS, or Windows environments using Azure CLI or portal.
- Where PowerShell is referenced, provide equivalent Bash/Azure CLI commands to ensure parity for Linux users.
- Review all instructions to ensure that no step assumes a Windows environment or toolset by default.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-cli.md
...s/azure-docs/blob/main/articles/firewall/deploy-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server images for virtual machines, instructing users to connect via Remote Desktop (RDP), and providing only PowerShell-based test commands. There are no examples or instructions for deploying or testing with Linux VMs, nor are there Linux shell command alternatives for testing firewall rules.
Recommendations
- Include parallel instructions and examples for deploying Linux-based virtual machines (e.g., using Ubuntu images) alongside the Windows examples.
- Provide SSH-based connection instructions for Linux VMs, in addition to RDP for Windows.
- Offer Linux shell command equivalents (e.g., using dig or curl) for testing DNS resolution and HTTP access, alongside the PowerShell commands.
- Explicitly mention that the procedure is cross-platform and clarify any differences in steps or tools between Windows and Linux environments.
- Where possible, use neutral language and examples that apply to both Windows and Linux, or present both options side by side.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-template.md
...re-docs/blob/main/articles/firewall/deploy-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the example template, referencing only Windows-based admin workflows (e.g., admin username/password for Windows VMs), and providing cleanup instructions solely via a PowerShell command. There are no Linux VM deployment options, nor are there CLI/bash examples for resource cleanup or management.
Recommendations
- Include Linux VM options in the deployment template and documentation steps, or provide a parallel example using Linux distributions (e.g., Ubuntu).
- When describing admin credentials, clarify differences for Linux (e.g., SSH key vs. password) and provide relevant instructions.
- Add resource cleanup instructions using Azure CLI (az group delete) and bash, not just PowerShell.
- Where possible, present both Windows and Linux options side-by-side, or at least mention Linux alternatives.
- Avoid assuming the user is working from a Windows environment; provide cross-platform guidance.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/dns-settings.md
...azure-docs/blob/main/articles/firewall/dns-settings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring Azure Firewall DNS settings, but it demonstrates a Windows bias by including detailed PowerShell instructions (a Windows-centric tool) and referencing Azure PowerShell modules. The PowerShell examples are given equal prominence to CLI, but there are no explicit Linux shell (bash) or cross-platform scripting examples. The documentation also uses terminology and patterns (such as PowerShell object manipulation) that are specific to Windows environments. Additionally, the custom metadata includes 'devx-track-azurepowershell', further indicating a Windows/PowerShell focus.
Recommendations
- Add explicit bash or shell scripting examples for Linux users, especially for tasks currently shown only in PowerShell.
- Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
- Where possible, provide bash scripting equivalents for multi-step PowerShell object manipulations (e.g., updating DNS server lists).
- Balance the order of examples: sometimes show CLI or bash first, not always PowerShell.
- Remove or balance custom metadata tags (such as 'devx-track-azurepowershell') to reflect cross-platform support.
- Explicitly state that all configuration steps can be performed from Linux/macOS using Azure CLI, and provide troubleshooting tips for non-Windows environments.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/easy-upgrade.md
...azure-docs/blob/main/articles/firewall/easy-upgrade.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page mentions PowerShell as a supported method for performing Azure Firewall SKU upgrades/downgrades, but does not mention or provide examples for equivalent Linux/Unix command-line tools (such as Azure CLI). The order of mention (Azure portal, then PowerShell, then Terraform) also places a Windows-centric tool before cross-platform alternatives. No Linux-specific or cross-platform command-line examples are provided.
Recommendations
- Include Azure CLI examples for performing upgrade/downgrade operations, as Azure CLI is cross-platform and widely used on Linux.
- Mention Azure CLI alongside PowerShell and Terraform in the list of supported tools, ideally listing the cross-platform option first or at least equally.
- Provide sample commands or links to documentation for both PowerShell and Azure CLI to ensure parity for Linux users.
- Review other documentation pages for similar patterns and update them to ensure equal representation of Linux-compatible tools.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/explicit-proxy.md
...ure-docs/blob/main/articles/firewall/explicit-proxy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell as the deployment method in the 'Next steps' section, without mentioning or linking to equivalent Linux/CLI instructions. No Linux or cross-platform command-line examples are provided, and the only deployment guidance is via PowerShell, which is more commonly associated with Windows environments.
Recommendations
- Add links or references to Azure CLI and ARM template deployment guides alongside the PowerShell example.
- Include explicit instructions or examples for configuring and deploying the explicit proxy feature using cross-platform tools (e.g., Azure CLI, Bash scripts).
- Ensure that all configuration steps (such as uploading PAC files, generating SAS URLs) are described in a platform-agnostic way, or provide both Windows and Linux/macOS workflows.
- Where possible, avoid assuming the use of Windows tools or environments; mention cross-platform alternatives early and equally.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-known-issues.md
...s/blob/main/articles/firewall/firewall-known-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell cmdlets as the primary or sole method for certain operations (e.g., updating firewall policy tags), mentioning PowerShell and CLI support together but not distinguishing or providing parity for Linux/Unix users, and omitting Linux-specific or cross-platform command-line examples. There are no explicit Linux/Unix command examples or tool references, and PowerShell is assumed as the default scripting environment for management tasks.
Recommendations
- For every PowerShell example or reference, provide an equivalent Azure CLI (az) example, which is cross-platform and widely used on Linux and macOS.
- When mentioning PowerShell and CLI support, clarify which commands are available in each and provide explicit Linux/Unix usage notes where relevant.
- Where a workaround or mitigation references a PowerShell cmdlet (e.g., Set-AzFirewallPolicy), include the equivalent Azure CLI command (e.g., az network firewall policy update) if available.
- Avoid assuming PowerShell as the default scripting environment; instead, present both PowerShell and CLI options side by side.
- Add a section or note addressing Linux/macOS users, highlighting any differences or limitations in tooling or support.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/firewall-sftp.md
...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 biased towards Windows and PowerShell usage. All deployment and configuration steps are provided exclusively using Azure PowerShell cmdlets, with no mention or examples for Azure CLI, Bicep, ARM templates, or Terraform, which are commonly used on Linux and cross-platform environments. The only command-line example for SFTP connection is generic, but the setup and management instructions assume a Windows/PowerShell environment throughout.
Recommendations
- Provide equivalent Azure CLI examples for all deployment and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bicep or ARM template snippets for infrastructure-as-code parity.
- Add a note at the beginning clarifying that the instructions are PowerShell-specific, and link to cross-platform alternatives.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and provide links or examples.
- Ensure that any references to tools or commands (such as 'command prompt') are platform-neutral or include both Windows and Linux/macOS equivalents.
- Consider including a table or section comparing PowerShell and CLI commands for each major step.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first and Windows-heavy bias. Most FQDN tags and examples focus on Windows or Microsoft-specific services (e.g., Windows Update, Windows Diagnostics, Windows 365, Windows Virtual Desktop), with no mention of Linux-specific services or scenarios. There are no examples or guidance for Linux administrators or non-Windows environments.
Recommendations
- Include examples of FQDN tags relevant to Linux-based workloads or popular open-source services (if supported by Azure Firewall).
- Add a section or examples addressing how Linux administrators might use FQDN tags, or clarify if the feature is equally applicable to Linux-based environments.
- Balance the documentation by mentioning both Windows and non-Windows scenarios where possible, or explicitly state the Windows-centric nature if it is by design.
- If Azure Firewall supports FQDN tags for non-Microsoft or cross-platform services, provide examples and documentation for those cases.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ftp-support.md
.../azure-docs/blob/main/articles/firewall/ftp-support.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and referencing PowerShell-based deployment and update workflows first and in more detail. While Azure CLI and ARM template options are mentioned, there are no explicit Linux shell (bash) examples or guidance, and the PowerShell workflow is given prominence and more explanation. There is no mention of Linux-native tools or workflows, and the CLI section lacks example commands.
Recommendations
- Add explicit bash/Azure CLI command examples for both deployment and updating scenarios, similar to the PowerShell examples.
- Present Azure CLI and ARM template instructions before or alongside PowerShell, rather than after.
- Include notes or examples relevant to Linux users, such as using Azure CLI in bash or cloud shell.
- Ensure parity in detail and explanation between PowerShell and CLI/ARM template sections.
- Where possible, avoid assuming PowerShell as the default automation tool, and clarify that all examples are cross-platform unless otherwise stated.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/integrate-with-nat-gateway.md
...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 presents Azure PowerShell examples before Azure CLI, which is more commonly used on Linux and cross-platform environments. There are no Bash or Linux-specific shell examples, and the PowerShell section is labeled and presented first, suggesting a Windows-centric approach. No mention is made of Linux tools or workflows, and all command-line examples are either PowerShell or Azure CLI, with no explicit Linux context.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Include explicit Bash/Linux shell examples, especially for users working in Linux environments.
- Add a note clarifying that Azure CLI commands can be run on Windows, Linux, and macOS, and provide guidance for Linux users if there are any differences.
- Ensure parity in documentation by referencing both Windows and Linux environments where relevant, and avoid assuming PowerShell as the default shell.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/ip-groups.md
...cs/azure-docs/blob/main/articles/firewall/ip-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively listing Azure PowerShell cmdlets for managing IP Groups, without providing equivalent Azure CLI (cross-platform) or Bash examples. There are no Linux-specific instructions or examples, and the only command-line tooling referenced is PowerShell, which is traditionally associated with Windows, despite its cross-platform availability. This may disadvantage Linux users or those preferring CLI/Bash workflows.
Recommendations
- Add Azure CLI examples for all IP Group management tasks alongside PowerShell cmdlets.
- Explicitly mention that Azure CLI and REST API can be used, and provide links or code snippets.
- Include Bash shell examples for common operations, especially for tasks like exporting/importing CSVs.
- Balance the 'Related Azure PowerShell cmdlets' section with a 'Related Azure CLI commands' section.
- Clarify that PowerShell is available cross-platform, but highlight CLI/Bash parity for Linux users.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/management-nic.md
...ure-docs/blob/main/articles/firewall/management-nic.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for managing the Azure Firewall Management NIC, with no mention of Azure CLI (cross-platform) or Bash/shell equivalents. The only automation examples use PowerShell cmdlets, which are primarily associated with Windows environments. There is no guidance or parity for Linux/macOS users, and the documentation implicitly assumes a Windows-centric workflow.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide side-by-side examples where possible.
- Include Bash/shell script snippets for common tasks, or at least reference how to perform the same actions from non-Windows environments.
- Review the documentation for other Windows-centric terminology or assumptions, and ensure instructions are inclusive of all supported platforms.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall-reference.md
...b/main/articles/firewall/monitor-firewall-reference.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for enabling and disabling diagnostic logs (Top flows and Flow trace), with no equivalent Azure CLI, Bash, or Linux-native instructions. The only command-line tooling referenced is PowerShell, which is most commonly associated with Windows environments, and there is no mention of cross-platform or Linux-first alternatives.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and clarify any platform-specific requirements.
- Where possible, include Bash script examples alongside PowerShell, especially for enabling/disabling diagnostic settings.
- Reference Azure Portal UI steps as an alternative for users who may not use PowerShell or CLI.
- Add a note or table summarizing all available tooling (PowerShell, Azure CLI, REST API, Portal) for each operation, with links to relevant documentation.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/monitor-firewall.md
...e-docs/blob/main/articles/firewall/monitor-firewall.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation displays a subtle Windows bias. It references Windows-centric tools (Excel, Power BI, Visual Studio, C#) and specifically calls out Azure PowerShell for enabling certain features (e.g., Fat Flow Log), without mentioning or providing parity for Linux or cross-platform alternatives (such as Azure CLI, Linux-compatible log viewers, or editors). There are no explicit Linux or cross-platform command-line examples, and the only tooling guidance for log conversion is for Visual Studio/C# users.
Recommendations
- Provide Azure CLI examples alongside or instead of Azure PowerShell for configuration steps, especially for enabling features like Fat Flow Log.
- Mention and provide examples for Linux-compatible tools for viewing and analyzing logs (e.g., jq, csvkit, LibreOffice Calc, or open-source BI tools).
- If referencing Visual Studio/C# tools, also mention scripting or conversion options in Python or Bash that are platform-agnostic.
- Ensure that any references to downloading and converting logs (e.g., JSON to CSV) include command-line examples that work on Linux/macOS (such as using jq or csvkit).
- Explicitly state that all features and steps can be performed from Linux/macOS environments, and provide links or examples where relevant.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy-certificates-enterprise-ca.md
.../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, Windows Certificate Export Wizard), and prerequisites assume Active Directory and Windows CA infrastructure. There are no Linux or cross-platform alternatives or examples provided for certificate creation, request, or export. The workflow is not accessible to administrators using Linux or non-Windows PKI solutions.
Recommendations
- Provide equivalent instructions for Linux environments, such as using OpenSSL for certificate requests and exports.
- Include examples for managing certificates with non-Windows CAs (e.g., OpenSSL, EJBCA, or HashiCorp Vault).
- Describe how to interact with Azure Key Vault and import certificates using CLI tools available on Linux (e.g., Azure CLI, REST API).
- Avoid assuming the use of Internet Explorer or Windows Certificate Export Wizard; offer browser-agnostic or command-line alternatives.
- Clarify which steps are Windows-specific and provide cross-platform alternatives wherever possible.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-deploy.md
...ure-docs/blob/main/articles/firewall/premium-deploy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing a Windows test virtual machine (WorkerVM) for all hands-on steps, such as running curl commands and opening browsers. There are no Linux VM deployment instructions or examples, and the process for installing certificates is only described for Windows. The use of 'administrator command prompt' and browser-based testing is also presented only in a Windows context.
Recommendations
- Provide parallel instructions for deploying and configuring a Linux-based WorkerVM, including certificate installation steps for common distributions (e.g., Ubuntu).
- Include Linux-specific command-line examples (e.g., using bash or terminal) alongside Windows examples.
- Clarify that curl and browser-based tests can be performed on both Windows and Linux, and provide any necessary Linux-specific guidance (such as installing curl or updating CA certificates).
- When describing certificate deployment, include steps for both Windows and Linux VMs.
- Use neutral language (e.g., 'open a terminal') instead of 'administrator command prompt' where possible.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/premium-migrate.md
...re-docs/blob/main/articles/firewall/premium-migrate.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All code examples and automation scripts are provided exclusively in PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. The instructions for module installation and validation are PowerShell-specific, and there are no Linux or cross-platform alternatives presented. Even though Azure PowerShell is technically cross-platform, the documentation assumes a Windows/PowerShell environment and does not address Linux users' needs or workflows.
Recommendations
- Provide equivalent Azure CLI (az) commands for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples or at least command-line snippets for Linux users.
- Clearly state that Azure PowerShell is available on Linux and macOS, and provide installation instructions for those platforms.
- When referencing tooling (such as module installation), include both PowerShell and Azure CLI alternatives.
- Where possible, add screenshots or walkthroughs using the Azure Portal, which is platform-agnostic.
- Review the order of presentation so that cross-platform methods (Azure CLI, Portal) are mentioned before or alongside PowerShell.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/protect-azure-virtual-desktop.md
...ain/articles/firewall/protect-azure-virtual-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based Azure Virtual Desktop deployments, referencing Windows-specific service tags, and providing proxy configuration examples only for Microsoft Edge. There are no examples or guidance for Linux-based session hosts or cross-platform scenarios, and Linux tools or patterns are not mentioned.
Recommendations
- Include explicit guidance and examples for Linux-based Azure Virtual Desktop session hosts, such as required FQDNs, endpoints, and firewall rules.
- When discussing proxy configuration, provide examples for popular Linux browsers (e.g., Firefox, Chromium) and command-line tools.
- Mention and link to documentation about deploying and managing Azure Virtual Desktop on Linux, if available.
- Use neutral terminology (e.g., 'session host' instead of 'Windows session host') where possible, and clarify when instructions are Windows-specific.
- If certain features are Windows-only, clearly state this and provide alternative recommendations for Linux environments.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-bicep.md
...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 demonstrates a Windows bias by focusing on RDP access to Windows Server VMs, referencing Azure PowerShell as a primary tool, and omitting Linux-specific examples or scenarios (such as SSH access to Linux VMs). The clean-up instructions use only PowerShell, and there is no mention of Linux tools or workflows.
Recommendations
- Include examples for accessing Linux VMs (e.g., SSH) alongside RDP/Windows examples.
- Provide clean-up instructions using Azure CLI, not just PowerShell.
- Mention both Azure CLI and PowerShell equally when describing deployment and management steps.
- Reference documentation for deploying and accessing both Windows and Linux VMs through the firewall.
- Balance the use of Windows and Linux terminology and tools throughout the documentation.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/secured-hub-customer-public-ip.md
...in/articles/firewall/secured-hub-customer-public-ip.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing configuration instructions and examples exclusively for the Azure portal and Azure PowerShell, both of which are Windows-centric tools. There are no equivalent examples or guidance for Linux users, such as Azure CLI or ARM templates. The PowerShell example is given as the only command-line method, and there is no mention of cross-platform alternatives.
Recommendations
- Add Azure CLI examples for all configuration steps to ensure Linux and macOS users have clear, supported instructions.
- Mention ARM template or Bicep deployment options for infrastructure-as-code parity.
- When listing configuration methods, present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools (e.g., PowerShell).
- Explicitly state that the instructions apply to all platforms, or clarify any platform-specific limitations.
- Include screenshots or walkthroughs from non-Windows environments where applicable.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/service-tags.md
...azure-docs/blob/main/articles/firewall/service-tags.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for configuring Azure Firewall service tags. There are no examples using Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there references to Linux-native tools or shell environments. The configuration section leads with and exclusively details PowerShell commands, reinforcing a Windows-centric approach.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands shown, ensuring Linux/macOS users can follow along without needing PowerShell.
- Explicitly mention that Azure CLI can be used from any platform and provide links to relevant CLI documentation.
- Consider including Bash shell examples where appropriate, especially for scripting or automation scenarios.
- Reorder the configuration section to present Azure CLI and PowerShell examples side by side, or start with the more cross-platform Azure CLI.
- Review and update any references or links that are PowerShell-specific to include CLI alternatives.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/snat-private-range.md
...docs/blob/main/articles/firewall/snat-private-range.md
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 Azure PowerShell (Windows-centric) examples before Azure CLI, and by not including any Linux-specific shell or scripting examples (e.g., Bash). The PowerShell examples are more extensive and detailed than the CLI ones. There are no references to Linux tools, shell environments, or considerations for Linux users. The documentation assumes familiarity with PowerShell, which is traditionally a Windows tool, and does not offer parity for Linux-native workflows.
Recommendations
- Provide Bash shell examples alongside Azure CLI commands to demonstrate Linux-native workflows.
- Ensure that Azure CLI examples are as detailed and comprehensive as the PowerShell examples, including notes on prerequisites and environment setup for Linux users.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any OS-specific considerations if applicable.
- Where PowerShell is referenced, clarify that PowerShell Core is cross-platform, or provide alternative scripts for Bash/zsh users.
- Add a section or notes addressing Linux users, including any differences in command syntax, environment variables, or deployment steps.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/sql-fqdn-filtering.md
...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides configuration steps using Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric and still most commonly used on Windows) and the absence of Linux-native tools or explicit Linux shell examples (such as Bash scripts) indicate a Windows bias. Additionally, the PowerShell section is given equal prominence to the CLI, and there are no Linux-specific troubleshooting or environment notes. There are no examples or guidance tailored for Linux users beyond the CLI, and no mention of Linux-specific considerations.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, including any necessary environment setup or differences for Linux users.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any Linux-specific notes if applicable (e.g., line continuation differences, authentication nuances).
- If PowerShell is included, consider also including Bash or shell script equivalents for parity.
- Mention that Azure PowerShell is available cross-platform, but note any differences or prerequisites for Linux users.
- Include troubleshooting steps or references for common issues on Linux environments.