Firewall
170
Total Pages
125
Linux-Friendly Pages
45
Pages with Bias
26.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
120 issues found
Showing 101-120 of 120 flagged pages
Firewall
Azure Firewall Explicit proxy (preview)
...ure-docs/blob/main/articles/firewall/explicit-proxy.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Azure PowerShell as the primary deployment method in the 'Next steps' section and not mentioning Linux/macOS equivalents (such as Azure CLI or ARM templates). No explicit Linux or macOS examples or tools are provided, and PowerShell is suggested as the main approach for configuration.
Recommendations
- Add instructions and links for deploying and configuring Azure Firewall using Azure CLI and ARM templates, which are cross-platform.
- Include examples or references for configuring proxy settings on browsers and applications in Linux/macOS environments.
- Ensure that screenshots and walkthroughs are not Windows-centric, or provide alternatives for other platforms.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions 'DevOps integration using REST/PowerShell/CLI/templates/Terraform' and 'DevOps integration: REST/PowerShell/CLI/templates/Terraform support' in feature tables and summaries. PowerShell (a Windows-centric tool) is listed first in both cases, ahead of cross-platform options like CLI and Terraform. No Linux/macOS-specific tools or examples are provided, and no explicit Linux/macOS bias is present, but the ordering subtly prioritizes Windows tooling.
Recommendations
- List cross-platform tools (Azure CLI, Terraform) before Windows-centric tools (PowerShell) to avoid perceived prioritization.
- Explicitly state that all management features are available via Azure CLI and Terraform, which are fully supported on Linux/macOS.
- Provide example commands for both PowerShell and Azure CLI in relevant deployment/configuration documentation.
- Add a note clarifying that all features are accessible from Linux/macOS environments using CLI and Terraform.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through the mention of Azure PowerShell as the required method for enabling the Fat Flow Log (Top flow log), without referencing equivalent CLI or REST methods. Additionally, the tip about log converter tools references Visual Studio and C#, which are more commonly associated with Windows environments. There are no explicit Linux/macOS examples or mentions of cross-platform alternatives, and Windows-centric tools are referenced before any Linux equivalents (if any). However, most of the guidance is platform-neutral, focusing on Azure portal and KQL queries.
Recommendations
- Provide Azure CLI and REST API instructions for tasks currently described as PowerShell-only (e.g., enabling Fat Flow Log).
- Mention cross-platform log converter tools or provide instructions for using Python or other language-based tools that work on Linux/macOS.
- When referencing tools like Visual Studio, also mention alternatives such as VS Code or command-line utilities that are cross-platform.
- Explicitly state that all JSON log manipulation and viewing can be performed on Linux/macOS using standard tools (jq, csvkit, etc.), and provide example commands.
- Ensure that any screenshots or step-by-step instructions do not assume a Windows environment unless absolutely necessary.
Firewall
Quickstart: Create an Azure Firewall and IP Groups - Terraform
...in/articles/firewall/quick-create-ipgroup-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists 'Create a random password for the Windows VM' before 'Create an Azure Linux Virtual Machine' in the checklist, suggesting a Windows-first bias. However, both Windows and Linux VM creation steps are present, and all command-line instructions use cross-platform tools (Terraform, Azure CLI) without Windows-specific commands or tools. No PowerShell examples or Windows-only tools are given, and Linux parity is generally maintained.
Recommendations
- List Linux and Windows VM creation steps together or in alphabetical order to avoid perceived prioritization.
- Explicitly mention that all steps and tools (Terraform, Azure CLI) work on Linux, macOS, and Windows.
- If possible, provide example code for both Linux and Windows VM creation, or clarify that both are covered.
- Avoid language that implies Windows is the default or primary platform.
Firewall
Azure Firewall Premium certificates
...cs/blob/main/articles/firewall/premium-certificates.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell scripts for certificate creation, but the PowerShell script is presented after the Bash script, and both are given equal prominence. There is no explicit Windows-only tooling or instructions, but the inclusion of PowerShell as a primary example may indicate a slight Windows bias. All instructions for certificate creation rely on OpenSSL, which is cross-platform. No steps are missing for Linux/macOS users, and the Bash script is fully functional for them.
Recommendations
- Clarify that both Bash and PowerShell scripts are equivalent and suitable for their respective platforms.
- Explicitly mention platform compatibility for each script (e.g., Bash for Linux/macOS, PowerShell for Windows).
- Consider listing the Bash script first to prioritize Linux/macOS parity, or present both scripts side-by-side.
- Add a note that OpenSSL must be installed on all platforms and provide installation guidance for Windows, Linux, and macOS.
Firewall
Configure Azure Firewall application rules with SQL FQDNs
...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Azure Firewall application rules with SQL FQDNs. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and is presented as a main method. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, and the PowerShell section is given equal prominence to CLI, which may suggest a Windows-centric approach. However, the CLI instructions are sufficient for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- Add explicit Bash shell examples or notes for Linux users where relevant.
- Consider mentioning cross-platform compatibility in the introduction to reduce perceived Windows bias.
- If PowerShell is required for advanced scenarios, provide equivalent Bash/CLI alternatives or note any limitations.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all configuration steps, but PowerShell examples are given equal prominence and detail as CLI. The CLI examples are cross-platform, but the documentation's metadata and custom tags (e.g., 'devx-track-azurepowershell') suggest a Windows/PowerShell orientation. There are no Linux/macOS-specific instructions, troubleshooting notes, or references to Linux tools or shell environments. Windows/PowerShell patterns are presented as a primary method, and there is no explicit mention of Linux or macOS user experience.
Recommendations
- Add explicit notes confirming that Azure CLI commands work on Linux/macOS and provide any OS-specific caveats.
- Include troubleshooting steps or tips for Linux/macOS users (e.g., how to restart VMs, check DNS settings, or install Azure CLI on Linux).
- Balance metadata and custom tags to include cross-platform tooling (e.g., 'devx-track-azurecli').
- Consider adding bash or shell script examples for common Linux admin tasks related to DNS settings.
- Clarify that PowerShell is Windows-centric and recommend CLI for cross-platform scenarios.
Firewall
Azure Firewall Explicit proxy (preview)
...ure-docs/blob/main/articles/firewall/explicit-proxy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. The 'Next steps' section links only to Azure PowerShell deployment instructions, omitting Linux/macOS CLI alternatives. No explicit Linux or cross-platform examples are provided, and PowerShell is referenced before any other tool, which may create friction for non-Windows users.
Recommendations
- Add equivalent deployment instructions using Azure CLI and/or ARM templates, which are cross-platform.
- Include examples or references for configuring proxy settings on Linux/macOS browsers and applications.
- Ensure that links to deployment guides include both PowerShell and CLI options, or clarify cross-platform support.
- Explicitly mention that the Azure Portal and REST API are available for configuration, which are platform-agnostic.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions 'Easy DevOps integration using REST/PowerShell/CLI/templates/Terraform' and 'DevOps integration: REST/PowerShell/CLI/templates/Terraform support' in feature lists. PowerShell is listed before CLI, which is more commonly used on Linux/macOS. There are no explicit Linux/macOS examples or references to Bash, and no mention of Azure CLI usage patterns or shell scripting for non-Windows platforms. However, the page does not provide any actual command-line examples, so the bias is limited to ordering and naming.
Recommendations
- List Azure CLI before PowerShell when mentioning cross-platform management tools.
- Explicitly state that Azure CLI and Terraform are fully supported on Linux/macOS.
- Add examples or links for Azure CLI and Bash usage for common management tasks.
- Clarify that PowerShell Core is cross-platform, if relevant, and provide parity examples.
Firewall
Scale SNAT ports with Azure NAT Gateway
...b/main/articles/firewall/integrate-with-nat-gateway.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step examples for associating a NAT gateway with an Azure Firewall subnet using Azure PowerShell and Azure CLI. The PowerShell example is presented first, which may indicate a Windows-first bias. While Azure CLI is cross-platform and included, there are no explicit Linux/macOS-specific notes or examples, and no mention of Bash scripting or Linux shell environments. The use of PowerShell as the primary scripting language may create friction for Linux/macOS users who are less familiar with it.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and more familiar to Linux/macOS users.
- Add explicit notes clarifying that Azure CLI commands work natively on Linux/macOS and Windows.
- Consider including Bash scripting examples or guidance for Linux users where relevant.
- Avoid implying PowerShell is the default or preferred method unless necessary for functionality.
- Add links to installation guides for Azure CLI on Linux/macOS.
Firewall
FQDN tags overview for Azure Firewall
...cs/azure-docs/blob/main/articles/firewall/fqdn-tags.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy Examples
Summary
The documentation page demonstrates a Windows bias by focusing examples and tag descriptions primarily on Windows-related services (e.g., Windows Update, Windows Diagnostics, WindowsVirtualDesktop, Windows365). The first and most detailed examples are Windows-centric, and there are no explicit Linux/macOS service tags or examples. While the core concept (FQDN tags) is platform-agnostic, the documentation implicitly prioritizes Windows use cases and services.
Recommendations
- Add examples or descriptions for Linux/macOS-related services if applicable (e.g., Azure Linux VM update endpoints, Linux diagnostics, or other non-Windows Microsoft services).
- Include a note clarifying that FQDN tags can be used for any outbound traffic, not just Windows services.
- Reorder examples or provide a more balanced set of examples, alternating between Windows and non-Windows services.
- Explicitly mention that the firewall and FQDN tags are platform-agnostic and can be used for Linux/macOS workloads.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through references to Windows-centric tools (Excel, Power BI, Visual Studio, C#) and requiring Azure PowerShell for enabling certain features (Fat Flow Log). There are no explicit Linux/macOS examples or alternative instructions for non-Windows users, and Windows tools are mentioned before cross-platform or open-source equivalents. However, most of the core monitoring and logging tasks are performed within the Azure portal or via KQL, which are platform-agnostic.
Recommendations
- Provide CLI (az) and REST API instructions for enabling features currently described as PowerShell-only, especially for configuring Fat Flow Log.
- Mention open-source or cross-platform tools (e.g., jq, pandas, LibreOffice Calc) for viewing and analyzing JSON/CSV logs alongside Excel and Power BI.
- Include guidance for users on Linux/macOS for log conversion and analysis, such as using Python scripts or shell utilities.
- Clarify that Visual Studio and C# log converter tools are optional, and suggest alternatives for non-Windows environments.
- Where screenshots or examples reference Windows-only tools or UI, add notes or alternatives for Linux/macOS users.
Firewall
Azure Firewall Premium certificates
...cs/blob/main/articles/firewall/premium-certificates.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell scripts for certificate creation, but the PowerShell script is presented after the Bash script, and both use OpenSSL (a cross-platform tool). There is no explicit Windows-only tooling or instructions, and Linux examples are present. However, the presence of a PowerShell script and its mention may indicate a slight Windows bias, especially for users who expect Linux-first or Linux-only examples in Azure documentation.
Recommendations
- Clarify that both Bash and PowerShell scripts are equivalent and can be used on any platform with OpenSSL installed.
- Explicitly state platform compatibility for each script (e.g., Bash for Linux/macOS, PowerShell for Windows).
- Consider providing usage instructions for macOS, as it is not mentioned.
- Ensure that the Bash script is presented first (as currently done) and note that it is suitable for Linux/macOS users.
- Add troubleshooting notes for common Linux/macOS certificate import issues if applicable.
Firewall
Quickstart: Create an Azure Firewall and IP Groups - Terraform
...in/articles/firewall/quick-create-ipgroup-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists the creation of a random password for a Windows VM before mentioning the Linux VM, and references Windows VM resources before Linux VM resources in the checklist. However, the implementation and verification steps use cross-platform tools (Terraform and Azure CLI), and Linux VM creation is also covered. No PowerShell or Windows-only tools are used in the main workflow.
Recommendations
- List Linux and Windows VM resources together or mention Linux VM first to avoid perceived prioritization.
- Clarify that the workflow is cross-platform and works equally on Linux, macOS, and Windows.
- If examples for VM creation are given, provide both Linux and Windows examples side by side.
- Explicitly state that Azure CLI and Terraform are supported on all major platforms.
Firewall
Azure Firewall SNAT private IP address ranges
...docs/blob/main/articles/firewall/snat-private-range.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Minor Windows Tools
Summary
The documentation provides configuration examples for Azure Firewall SNAT private IP address ranges using Azure PowerShell, Azure CLI, ARM templates, and the Azure portal. While both PowerShell and CLI are covered, PowerShell examples and instructions are presented before CLI, and the PowerShell section is more detailed. There is a slight emphasis on PowerShell, which is traditionally associated with Windows environments, and some minor references to Windows-centric tools. However, Azure CLI and ARM templates are cross-platform, and no critical functionality is locked to Windows-only tools.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
- Ensure CLI instructions are as detailed as PowerShell instructions, including notes and caveats.
- Explicitly mention that Azure CLI and ARM templates are fully supported on Linux/macOS.
- Add a note clarifying that all configuration methods (CLI, ARM, portal) work on Linux/macOS, and PowerShell Core is available cross-platform.
- Where possible, provide bash or shell script snippets for Linux users, especially for automation scenarios.
Firewall
Configure Azure Firewall application rules with SQL FQDNs
...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides configuration instructions using Azure CLI, Azure PowerShell, and the Azure portal. While Azure CLI is cross-platform, the PowerShell section is Windows-centric, and there are no Linux/macOS-specific command examples or notes. The ordering of examples places Azure CLI first, but the inclusion of PowerShell as a primary method may suggest a Windows bias, especially since no Bash or Linux-native alternatives are mentioned.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit Bash shell examples where relevant.
- Add notes or examples for Linux/macOS users, such as validating prerequisites (e.g., az CLI installation on Linux).
- If PowerShell is mentioned, note that PowerShell Core is cross-platform, and provide installation/usage guidance for Linux/macOS.
- Consider adding troubleshooting tips or environment-specific notes for non-Windows users.
Firewall
Azure Firewall Premium certificates
...cs/blob/main/articles/firewall/premium-certificates.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell scripts for certificate generation, but the PowerShell script is presented after the Bash script, and there is no evidence of exclusive Windows tools or patterns. Both scripts rely on OpenSSL, which is cross-platform. However, the inclusion of a PowerShell script may indicate some Windows bias, as PowerShell is primarily used on Windows (though it is available on Linux/macOS). No Windows-only tools or examples are given, and Linux users are not prevented from completing the task.
Recommendations
- Clarify that both Bash and PowerShell scripts are cross-platform, and mention that PowerShell Core is available on Linux/macOS.
- Explicitly state that OpenSSL commands work on Windows, Linux, and macOS, and provide installation guidance for each OS.
- Consider providing a brief example of running the Bash script on Windows using WSL, or running PowerShell on Linux/macOS.
- Ensure that any future troubleshooting or configuration steps do not assume Windows-only environments.
Firewall
Azure Firewall Explicit proxy (preview)
...ure-docs/blob/main/articles/firewall/explicit-proxy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by referencing Azure PowerShell as the primary deployment method in the 'Next steps' section, without mentioning equivalent Linux/macOS-friendly options (such as Azure CLI or ARM templates). There are no explicit examples or instructions tailored for Linux or macOS users, and Windows-centric tooling is referenced first.
Recommendations
- Include instructions or links for deploying and configuring Azure Firewall using Azure CLI, which is cross-platform.
- Mention ARM/Bicep template deployment options for platform neutrality.
- Ensure examples and tooling references are presented in a platform-agnostic order, or provide parallel examples for Windows (PowerShell) and Linux/macOS (CLI).
- Add notes clarifying that PowerShell is available on Linux/macOS, or suggest alternatives where appropriate.
Firewall
Quickstart: Create an Azure Firewall and IP Groups - Terraform
...in/articles/firewall/quick-create-ipgroup-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists creation of a Windows VM and its password before the Linux VM in the checklist, but otherwise provides platform-neutral instructions and examples. No PowerShell, Windows-specific tools, or commands are present in the main workflow; Azure CLI is used for verification, which is cross-platform.
Recommendations
- List Linux VM creation before Windows VM in the checklist to avoid implicit prioritization.
- Explicitly state that all CLI commands are cross-platform and provide any necessary notes for Linux/macOS users (e.g., shell syntax differences if relevant).
- If mentioning VM creation, clarify that both Windows and Linux VMs are supported and provide parity in example details if possible.
Firewall
Configure Azure Firewall application rules with SQL FQDNs
...docs/blob/main/articles/firewall/sql-fqdn-filtering.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Azure Firewall application rules with SQL FQDNs. While Azure CLI is cross-platform, Azure PowerShell is primarily associated with Windows environments, and its inclusion may suggest a Windows-centric workflow. The order of presentation places Azure CLI first, which is positive for Linux parity, but the PowerShell section is detailed and assumes familiarity with Windows tooling. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, nor is there explicit mention of Linux/macOS compatibility for the CLI commands.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell script examples or notes for Linux users where relevant.
- Clarify that Azure PowerShell can be used on Linux/macOS (if true), or recommend Azure CLI for non-Windows users.
- Consider including troubleshooting or environment setup notes for Linux/macOS users.