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 301-325 of 332 flagged pages
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-firewall-basic-portal-policy.md
...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 OS for the workload VM, with no mention of Linux alternatives or instructions. The testing section assumes the use of Remote Desktop and Internet Explorer, both Windows-specific tools, and does not provide Linux equivalents or guidance. While the Azure portal is cross-platform, the step-by-step instructions and validation steps are Windows-centric.
Recommendations
- Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the workload subnet, including example settings.
- Include guidance for connecting to the Linux VM (e.g., using SSH) and testing outbound connectivity (e.g., using curl or wget to access allowed FQDNs).
- In the firewall DNAT rule section, mention SSH (port 22) as an alternative to RDP (port 3389) for Linux VMs.
- In the testing section, add Linux-specific examples for verifying DNS and HTTP/HTTPS access (e.g., using dig, nslookup, curl, or wget).
- Explicitly state that the procedure is applicable to both Windows and Linux VMs, and provide links to relevant Azure Linux VM documentation.
Create Pull Request
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-terraform.md
...e-docs/blob/main/articles/firewall/deploy-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the Terraform example and referring only to Windows VMs throughout. There are no examples or mentions of deploying Linux VMs, nor are there instructions or notes for users who may wish to use Linux servers instead. This may give the impression that only Windows is supported or recommended in this scenario.
Recommendations
- Include parallel examples or instructions for deploying Linux virtual machines using azurerm_linux_virtual_machine alongside the Windows VM steps.
- Update the narrative to mention that either Windows or Linux VMs can be used, and provide guidance or code samples for both.
- Where VM credentials or configuration are discussed (such as random_password for Windows), add equivalent Linux-focused steps (e.g., SSH key generation).
- Ensure that any troubleshooting or verification steps are not specific to Windows and clarify cross-platform applicability.
- Consider rephrasing the description and checklist to refer to 'virtual machines' generically, or explicitly state that both Windows and Linux are supported.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-template.md
...ain/articles/firewall/quick-create-ipgroup-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell example (Remove-AzResourceGroup) for resource cleanup but does not offer equivalent CLI or Bash commands for Linux/macOS users. No Linux-specific or cross-platform command-line instructions are given, despite the ARM template including a Linux jumpbox.
Recommendations
- Add Azure CLI and/or Bash examples for resource group deletion (e.g., az group delete --name <your resource group name>).
- Wherever PowerShell is used, provide equivalent cross-platform commands or clearly indicate alternatives for Linux/macOS users.
- Consider including a table or section summarizing common operations (deploy, delete, review) with both PowerShell and Azure CLI/Bash commands.
- Review other steps for implicit Windows assumptions and clarify that all steps can be performed from any OS using the Azure CLI or portal.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-multiple-ip-terraform.md
...rticles/firewall/quick-create-multiple-ip-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by focusing exclusively on deploying and accessing Windows Server virtual machines (with RDP), without mentioning or providing examples for Linux VMs or SSH access. The only VM example is Windows, and the NAT rules are described as enabling RDP to Windows Server 2019 VMs. There are no Linux VM deployment steps or verification instructions for Linux users.
Recommendations
- Include parallel examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside the Windows VM steps.
- Describe how to configure NAT rules for SSH access to Linux VMs, in addition to RDP for Windows.
- In the checklist and resource creation steps, mention both Windows and Linux VM options, or provide a choice.
- In the verification section, add instructions for verifying access to Linux VMs (e.g., using SSH) as well as Windows VMs.
- Reference documentation for both Windows and Linux VM management in Azure, not just Windows/PowerShell.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/remote-work-support.md
...ocs/blob/main/articles/firewall/remote-work-support.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on Windows-based virtual desktop infrastructure, specifically Azure Virtual Desktop (which is Windows-centric), and does not mention or provide guidance for Linux-based virtual desktop solutions or clients. All examples and descriptions assume a Windows environment, with no reference to Linux equivalents or cross-platform scenarios.
Recommendations
- Include references to Linux-based virtual desktop solutions that can be protected by Azure Firewall, such as Linux VDI or third-party Linux desktop virtualization tools.
- Provide examples or guidance for securing outbound/inbound connections for Linux virtual machines or Linux-based remote desktop clients.
- Mention that Azure Firewall can protect both Windows and Linux workloads, and provide parity in documentation for both operating systems.
- If possible, add links or references to documentation on securing Linux remote work environments with Azure Firewall.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal-policy.md
...les/firewall/tutorial-firewall-deploy-portal-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using a Windows Server virtual machine for the workload and providing only instructions for connecting via Remote Desktop (RDP) and using Microsoft Edge. There are no examples or guidance for deploying or testing with a Linux VM, nor are there instructions for connecting via SSH or using Linux-based tools to test firewall rules.
Recommendations
- Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including appropriate configuration steps.
- Include examples for connecting to the Linux VM using SSH, and provide Linux-based testing steps (e.g., using curl or wget to test outbound access, dig or nslookup for DNS testing).
- When describing the test phase, offer both Windows (RDP, Edge) and Linux (SSH, browser or command-line tools) options.
- Consider mentioning both Windows and Linux options side-by-side throughout the tutorial, rather than only referencing Windows tools and patterns.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-deploy-portal.md
...n/articles/firewall/tutorial-firewall-deploy-portal.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation exclusively demonstrates deploying and testing Azure Firewall using a Windows Server virtual machine, with no mention or example of Linux-based VMs. The test instructions (e.g., using Remote Desktop and Internet Explorer) are Windows-specific, and there are no Linux alternatives or parity in the walkthrough. The only OS option presented for the test VM is Windows, and the testing steps assume a Windows environment.
Recommendations
- Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the test subnet, including example configuration values.
- Include Linux-specific testing steps, such as connecting via SSH and using a browser like Firefox or Chrome to test outbound access.
- Provide guidance on configuring DNS settings for Linux VMs (e.g., editing /etc/resolv.conf or using cloud-init).
- Wherever possible, present both Windows and Linux options side-by-side, or at least mention Linux as an alternative.
- Avoid assuming the use of Windows-only tools (e.g., Remote Desktop, Internet Explorer) in testing steps; suggest cross-platform or Linux-native alternatives.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat-policy.md
...ain/articles/firewall/tutorial-firewall-dnat-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial exclusively uses a Windows Server virtual machine as the workload example and instructs users to test connectivity using Remote Desktop (RDP), which is a Windows-centric protocol. There are no Linux VM deployment instructions or SSH-based testing examples, and the only OS option explicitly mentioned is Windows Server. This creates a Windows-first impression and omits Linux parity in both deployment and testing steps.
Recommendations
- Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including specifying username, authentication, and any required inbound ports (e.g., 22 for SSH).
- Include testing steps for Linux VMs, such as connecting via SSH to the firewall public IP address and verifying access to the Linux VM.
- When listing OS choices for the VM, mention both Windows and Linux options, or provide a choice step.
- If using RDP as an example, also provide an SSH example for Linux, including the necessary DNAT rule for port 22.
- Ensure that screenshots or UI steps do not assume only Windows Server images are being used.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-firewall-dnat.md
.../blob/main/articles/firewall/tutorial-firewall-dnat.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 testing via Remote Desktop (RDP) to port 3389, which is specific to Windows environments. There are no Linux VM deployment instructions, nor are there examples for Linux-based access (such as SSH on port 22). This presents a Windows-first bias and omits Linux parity in both deployment and testing steps.
Recommendations
- Include parallel instructions for deploying a Linux VM (e.g., Ubuntu Server) in the 'Create a virtual machine' section.
- Provide an example NAT rule for SSH (port 22) to a Linux VM, alongside the RDP example.
- In the 'Test the firewall' section, add steps for connecting via SSH to the Linux VM using its public IP and port 22.
- When referencing operating system-specific steps, present both Windows and Linux options, or clarify that the process is OS-agnostic where possible.
- Consider mentioning cross-platform remote access tools or protocols, or provide a note about how to adapt the instructions for Linux workloads.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/tutorial-protect-firewall-ddos.md
...in/articles/firewall/tutorial-protect-firewall-ddos.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the example operating system for the workload VM, with no mention of Linux alternatives or instructions. The testing steps assume the use of Remote Desktop and Internet Explorer, both Windows-specific tools, and there are no Linux command-line or desktop environment equivalents provided. The only alternative workflow mentioned is Azure PowerShell, with no reference to Azure CLI or Bash scripting.
Recommendations
- Include parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) alongside the Windows Server example.
- Provide Linux-compatible testing steps, such as using SSH for remote access and browsers like Firefox or Chrome for validation.
- Reference Azure CLI and Bash scripting alternatives for users who prefer or require non-Windows environments.
- Explicitly mention that the tutorial is applicable to both Windows and Linux VMs, and provide guidance for both where steps differ.
- When suggesting remote access, offer both RDP (for Windows) and SSH (for Linux) instructions.
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is generally platform-neutral, but there are minor signs of Windows bias. Specifically, mitigation steps for adding tags to Azure Firewall Policy mention using the Azure PowerShell cmdlet (`Set-AzFirewallPolicy`), with no mention of equivalent CLI or REST API methods. Additionally, the 'Missing PowerShell and CLI support for ICMP' issue references Azure PowerShell and CLI, but does not clarify Linux/macOS alternatives or parity. There are also references to IIS for FTP configuration, which is a Windows-specific tool, without mentioning Linux FTP server equivalents.
Recommendations
- Where PowerShell is suggested for configuration (e.g., updating tags), also provide Azure CLI and REST API alternatives, and clarify their cross-platform availability.
- When referencing FTP server configuration, include examples or links for popular Linux FTP servers (such as vsftpd or ProFTPD) alongside IIS.
- Explicitly state platform parity for Azure CLI and REST API usage, especially for tasks currently only documented with PowerShell.
- Review mitigation steps to ensure Linux/macOS users are not left without guidance for critical operations.
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is generally cross-platform and does not focus on Windows-specific deployment or configuration patterns. However, there are minor instances of Windows bias: PowerShell is mentioned as the only CLI tool for updating firewall policy tags, and an FTP workaround links to IIS documentation, a Windows-only web server. These references may create friction for Linux/macOS users who may prefer Bash, Azure CLI, or Linux-based FTP servers.
Recommendations
- When referencing CLI tools, provide Azure CLI and/or Bash examples alongside PowerShell, especially for common operations like updating firewall policy tags.
- For FTP server configuration workarounds, include links or examples for popular Linux FTP servers (e.g., vsftpd, ProFTPD) in addition to IIS.
- Clarify when a workaround or tool is Windows-specific, and offer Linux/macOS alternatives where possible.
Firewall
Azure Firewall known issues and limitations
...s/blob/main/articles/firewall/firewall-known-issues.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation page is generally platform-neutral and focuses on Azure Firewall service limitations. However, there are minor signs of Windows bias: PowerShell is mentioned as the primary tool for updating firewall policy tags, and IIS is referenced as an example for FTP server configuration. There are no Linux/macOS-specific CLI or tool examples, and PowerShell is suggested without parity for Bash/CLI. No critical sections are Windows-only, and most guidance applies equally to all platforms.
Recommendations
- When mentioning PowerShell cmdlets (e.g., Set-AzFirewallPolicy), also provide equivalent Azure CLI (az) commands or REST API examples for Linux/macOS users.
- When referencing IIS for FTP configuration, add a note or link to equivalent configuration steps for common Linux FTP servers (e.g., vsftpd, proftpd).
- Ensure that troubleshooting steps and mitigations do not assume use of Windows-only tools unless the feature is Windows-specific.
- Where possible, clarify that portal and REST API actions are cross-platform.
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 both Azure PowerShell and Azure CLI examples for associating a NAT gateway with an Azure Firewall subnet. However, the PowerShell example is presented first and in greater detail, which may signal a Windows-first bias. PowerShell is primarily a Windows-centric tool, though it is available cross-platform. There are no Linux/macOS-specific shell or tool examples (e.g., Bash scripts), nor is there explicit mention of platform differences or parity.
Recommendations
- Alternate the order of examples, sometimes presenting Azure CLI (which is more native to Linux/macOS) first.
- Add explicit notes clarifying that both Azure PowerShell and Azure CLI are cross-platform, and provide guidance for Linux/macOS users on installing and using these tools.
- Consider including Bash script examples or links to platform-specific guidance for Linux/macOS users.
- Ensure that documentation sections do not implicitly prioritize Windows tools unless there is a technical reason.
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 and workflows. For example, enabling the Azure Firewall Fat Flow Log (Top flow log) is stated to require Azure PowerShell, with no mention of equivalent CLI or automation options for Linux/macOS users. The log converter tool is described as a C#/.NET solution, which is more accessible on Windows. Data visualization examples prioritize Excel and Power BI, both Windows-first tools, before mentioning generic alternatives. No explicit Linux/macOS examples or parity guidance are provided.
Recommendations
- Provide Azure CLI or REST API instructions for tasks currently described as PowerShell-only, such as enabling Fat Flow Log.
- Mention cross-platform log conversion tools (e.g., Python scripts, jq, csvkit) alongside the C#/.NET converter.
- List open-source or cross-platform visualization tools (e.g., Grafana, Tableau Public) before or alongside Excel and Power BI.
- Explicitly state that all steps can be performed from Linux/macOS, and provide example commands or screenshots from those platforms where relevant.
- Where screenshots or instructions reference the Azure portal, clarify that the portal is OS-agnostic.
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 lists the Bash script first and gives equal prominence to both. There is no evidence of exclusive Windows tools or patterns, and Linux users are not blocked from completing any task. All instructions are cross-platform, relying on OpenSSL, which is available on both Windows and Linux. However, the inclusion of a PowerShell script may suggest a slight Windows bias, as PowerShell is primarily a Windows tool (though now available on Linux). No Windows-only tools or examples are present, and Linux parity is generally good.
Recommendations
- Clarify that PowerShell is available on Linux, or note that Bash is recommended for Linux/macOS users.
- Explicitly state that all scripts require OpenSSL, which is cross-platform.
- Consider providing a macOS-specific note if there are any platform-specific caveats.
- Ensure that future examples do not prioritize Windows tools unless 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 the creation of a random password for a Windows VM before mentioning the Linux VM, and references the Windows VM specifically in the checklist of resources to be created. However, the main implementation steps and code samples are platform-neutral, and the verification and cleanup steps use Azure CLI, which is cross-platform. No PowerShell-specific instructions or Windows-only tools are present.
Recommendations
- List Linux and Windows VM resources together or mention Linux first to avoid perceived prioritization.
- Clarify that both Linux and Windows VMs are supported and provide parity in example coverage.
- If mentioning OS-specific resources (like random_password for Windows VM), also mention their Linux equivalents or usage scenarios.
- Ensure any future troubleshooting or advanced sections include both Windows and Linux command-line examples if relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions DevOps integration via REST/PowerShell/CLI/templates/Terraform, listing PowerShell (a Windows-centric tool) before CLI and Terraform, but does not provide any platform-specific examples or instructions. The only service tag example given is for Windows Update, which is a Windows-specific scenario. However, the overall content is platform-neutral and does not provide command-line or tool usage examples that would disadvantage Linux/macOS users.
Recommendations
- List platform-neutral tools (CLI, Terraform, REST) before or alongside PowerShell to avoid perceived prioritization of Windows tooling.
- Provide examples for both PowerShell and Azure CLI when mentioning DevOps integration, or clarify that all features are available via both tools.
- Include a service tag example relevant to Linux/macOS (e.g., allowing traffic for Ubuntu updates) alongside the Windows Update example.
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. However, the PowerShell section is given equal prominence to CLI, despite PowerShell being a Windows-centric tool. There are no Linux-specific instructions or examples, and the order of presentation (CLI, then PowerShell, then Portal) is neutral but could be improved by clarifying cross-platform support. No Windows-only tools are mentioned, but the inclusion of PowerShell may imply a Windows bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying that Azure PowerShell can be used on Linux/macOS via PowerShell Core, or link to installation instructions for non-Windows platforms.
- Consider providing bash or shell script examples for Linux users, or clarify that the CLI commands work natively on Linux/macOS.
- Reorder sections to present CLI first, and clarify platform compatibility for each method.
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 mentioning the Linux VM, and refers to a 'random password for the Windows VM' specifically in its checklist. However, the implementation steps and code samples are platform-agnostic, and the verification and cleanup sections use Azure CLI, which is cross-platform. No PowerShell-specific or Windows-only tools are used, and Linux VM creation is also covered.
Recommendations
- List Linux and Windows VM creation steps together or mention Linux VM first to avoid perceived prioritization.
- Clarify that the random password resource can be used for either Windows or Linux VMs, or provide examples for both.
- Ensure parity in examples and explanations for both Linux and Windows VM scenarios.
- Explicitly state that all CLI commands work on Linux, macOS, and Windows.
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 CLI options. No explicit Linux/macOS examples or tools are provided, and PowerShell is suggested as the main approach for configuration.
Recommendations
- Include Azure CLI instructions alongside PowerShell for deployment and configuration, as Azure CLI is cross-platform.
- Explicitly mention that PowerShell is available on Linux/macOS, or provide Bash shell examples where appropriate.
- Add guidance or links for Linux/macOS users to ensure parity in configuration steps.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-specific tools and patterns, such as mentioning PowerShell and the Windows Update FQDN tag, and lists 'REST/PowerShell/CLI/templates/Terraform' for DevOps integration with PowerShell (a Windows-centric tool) before CLI and Terraform. The example of FQDN tags uses Windows Update, which is a Windows-specific service, and there is no mention of Linux/macOS equivalents or examples. However, the documentation does mention cross-platform tools (CLI, Terraform) and does not provide step-by-step examples that are Windows-only.
Recommendations
- Include Linux/macOS-specific examples or references, such as using Linux Update repositories in FQDN tag examples.
- List cross-platform tools (CLI, Terraform) before Windows-specific tools (PowerShell) when describing DevOps integration.
- Provide explicit statements that all features and management tools are available and supported on Linux/macOS, where applicable.
- Add example use cases or scenarios relevant to Linux/macOS environments.
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 both Azure PowerShell and Azure CLI. However, the PowerShell example is presented first, which may signal a Windows-centric approach. PowerShell is traditionally associated with Windows environments, and its prominence may create friction for Linux/macOS users who typically use Azure CLI or other tools. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but Azure CLI is cross-platform and included.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash script examples or notes for Linux users where relevant.
- Clarify that PowerShell Core is available cross-platform, if PowerShell examples are retained.
- Add a short section or note on tool parity for Linux/macOS users, explaining which tools are supported and recommended.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias. The only explicit mention of a platform-specific tool is Azure PowerShell, which is required to enable the Fat Flow Log (Top flow log). There are references to using Excel and Visual Studio/C# for log conversion and analysis, which are traditionally Windows-centric tools. No Linux/macOS-specific tools or CLI examples are provided, and there are no Bash/Azure CLI instructions for tasks like enabling logs or converting data. However, most instructions are portal-based and generic, and JSON log formats are platform-neutral.
Recommendations
- Provide Azure CLI and Bash examples for enabling features such as Fat Flow Log, alongside PowerShell instructions.
- Mention cross-platform alternatives for log conversion and analysis, such as jq, pandas (Python), or csvkit.
- Include references to Linux/macOS-compatible editors and visualization tools (e.g., LibreOffice Calc, VS Code, or open-source BI tools).
- Clarify that Visual Studio and Excel are optional and suggest platform-neutral or open-source alternatives.
- Ensure that any code snippets or tool recommendations are not exclusively Windows-centric.
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, and the scripts themselves use OpenSSL, which is cross-platform. However, the inclusion of a PowerShell script may suggest a slight Windows bias, as PowerShell is primarily used on Windows (though it is available on Linux/macOS). No Linux-specific tools or examples (such as native Linux certificate management commands) are mentioned, and there is no guidance for macOS users. The overall bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
- Clarify that both Bash and PowerShell scripts are cross-platform and provide guidance for running PowerShell on Linux/macOS.
- Add explicit instructions or troubleshooting notes for Linux/macOS users regarding OpenSSL installation and usage.
- Consider including Linux-native certificate management commands or references (e.g., using 'certtool' or 'update-ca-certificates').
- Add a note for macOS users about certificate trust and installation procedures.