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 326-332 of 332 flagged pages
Firewall
Azure Firewall SNAT private IP address ranges
...docs/blob/main/articles/firewall/snat-private-range.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
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. However, the PowerShell examples are presented first and in greater detail, which may indicate a subtle Windows-first and PowerShell-heavy bias. There are no explicit Linux/macOS-only tools or shell examples (e.g., Bash scripts), but Azure CLI is cross-platform and is included. No critical functionality is locked to Windows, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS and Windows.
- Consider including Bash shell script examples for automation scenarios.
- Balance the depth of explanation between PowerShell and CLI sections.
- Where possible, avoid language that assumes use of Windows tools or environments.
Create Pull Request
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, the PowerShell section is Windows-centric and is presented immediately after the CLI section, giving it prominence. There are no Linux-specific examples or notes, and no mention of Linux/macOS nuances or troubleshooting. The portal instructions are platform-neutral, but the overall flow prioritizes Windows tooling and patterns.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and Windows, and highlight any platform-specific considerations.
- Add troubleshooting notes or tips for Linux/macOS users, such as shell quoting or az CLI installation steps.
- Consider adding a Linux/macOS validation example (e.g., using curl or sqlcmd from a Linux VM to test connectivity).
- Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users if needed.
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 creation of a Linux VM, suggesting a Windows-first bias. However, the main Terraform examples and verification steps use cross-platform tools (Terraform and Azure CLI), and there are no PowerShell-specific instructions or Windows-only tools. There is no explicit omission of Linux examples, but the ordering prioritizes Windows VM creation over Linux VM creation.
Recommendations
- List the creation of Linux and Windows VMs together or mention Linux VM creation first to avoid perceived prioritization.
- Provide parity in example details for both Windows and Linux VM creation (e.g., show password generation for Linux VM if relevant).
- Explicitly state that the instructions and tools (Terraform, Azure CLI) are cross-platform and suitable for both Windows and Linux users.
- If mentioning OS-specific resources, ensure both Windows and Linux are covered equally in explanations and sample code.
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 random password for a Windows VM before mentioning the creation of a Linux VM, suggesting a Windows-first bias in resource examples. However, the main verification and operational instructions use Azure CLI, which is cross-platform, and there are no PowerShell-exclusive instructions or Windows-only tools referenced. No Linux examples are missing, but Windows VM is mentioned before Linux VM in the checklist.
Recommendations
- List Linux VM creation before or alongside Windows VM creation in the checklist to avoid suggesting Windows is primary.
- Explicitly mention that all CLI instructions work on both Windows and Linux platforms.
- If possible, provide parity in VM examples (e.g., show both Windows and Linux VM creation together or clarify their use cases).
- Review other sections for subtle prioritization of Windows tools or workflows and ensure Linux parity.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-terraform.md
...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 creation of a Linux VM, suggesting a Windows-first bias in resource examples. However, the actual implementation steps and verification use cross-platform tools (Terraform and Azure CLI), and there are no PowerShell-specific instructions or exclusive use of Windows tools.
Recommendations
- List Linux and Windows VM creation steps together or mention Linux VM first, as Terraform is cross-platform and many cloud engineers use Linux.
- Provide parity in example details for both Linux and Windows VMs, or clarify why a Windows VM is included if not used in the walkthrough.
- Ensure that any OS-specific instructions (e.g., password generation, SSH key creation) are balanced for both platforms.
- Explicitly state that all steps can be performed on both Windows and Linux systems, and provide any necessary OS-specific notes if relevant.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-terraform.md
...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 creation of a Linux VM, suggesting a Windows-first bias in the resource checklist. However, the implementation steps and code samples focus on cross-platform tools (Terraform, Azure CLI) and do not provide OS-specific examples or instructions. No PowerShell examples or Windows-only tools are present, and the verification steps use Azure CLI, which is available on both Windows and Linux.
Recommendations
- Reorder the checklist to mention Linux and Windows VM creation together or list Linux first to avoid perceived prioritization.
- Explicitly state that all CLI commands and Terraform steps work on both Windows and Linux platforms.
- If mentioning OS-specific VM creation, provide parity in examples and explanations for both Windows and Linux.
- Add a note clarifying that the guide is platform-agnostic and suitable for users on Windows, Linux, or macOS.
Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/quick-create-ipgroup-terraform.md
...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 creation of a Linux VM, and references a Windows VM specifically in the checklist of resources. However, the main implementation steps and code samples are platform-agnostic, and the verification and CLI instructions use Azure CLI, which is cross-platform. There are no PowerShell-specific examples, and both Windows and Linux VMs are mentioned, though Windows is listed first.
Recommendations
- List the creation of Linux and Windows VMs together or mention Linux first to avoid implicit prioritization of Windows.
- Provide equivalent detail for both Linux and Windows VM creation steps, or clarify that both are optional and can be created as needed.
- Ensure that any references to OS-specific resources or steps are balanced and that neither platform is implied as the default.
- If possible, add explicit notes that the instructions and code samples are cross-platform and work on both Windows and Linux environments.