Firewall Manager
27
Total Pages
13
Linux-Friendly Pages
14
Pages with Bias
51.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
80 issues found
Showing 26-50 of 80 flagged pages
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/rule-hierarchy.md
.../blob/main/articles/firewall-manager/rule-hierarchy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell command examples, referencing Windows filesystem paths (e.g., C:\CustomRoles\), and omitting equivalent instructions for Linux or cross-platform CLI tools. There is no mention of Azure CLI (az), Bash, or Linux file paths, and all automation and scripting guidance is tailored to Windows/PowerShell users.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
- Include file path examples using Linux conventions (e.g., /home/user/CustomRoles/ReaderSupportRole.json) alongside Windows paths.
- Explicitly state that the procedures can be performed on Linux/macOS and provide any necessary adjustments (e.g., command syntax, file editing tools).
- Reference Bash or shell scripting alternatives for automation tasks, not just PowerShell.
- Add a note or section clarifying cross-platform support and linking to relevant documentation for Linux/macOS users.
Create Pull Request
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/secure-hybrid-network.md
...ain/articles/firewall-manager/secure-hybrid-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The tutorial demonstrates a clear Windows bias: all VM creation examples use Windows Server, IIS installation is shown only via PowerShell, and Cloud Shell is set to PowerShell by default. There are no Linux VM examples, nor are Linux tools or command-line patterns (e.g., Bash, SSH, apt/yum) mentioned. Windows-centric tools and workflows (RDP, PowerShell, Windows Server) are used exclusively, with no parity for Linux users.
Recommendations
- Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) in the spoke and on-premises networks.
- Include steps for installing and configuring a web server (e.g., Apache or Nginx) on Linux VMs using Bash/SSH commands.
- Show how to use Azure Cloud Shell with Bash for Linux VM management and extension installation.
- Demonstrate connectivity tests using Linux tools (e.g., curl, ssh, ping) in addition to Windows tools (RDP, browser).
- Explicitly mention that both Windows and Linux VMs are supported and provide guidance for each.
- Balance screenshots and examples to represent both platforms.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/dns-settings.md
...cs/blob/main/articles/firewall-manager/dns-settings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration examples using Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell examples are Windows-centric and there are no explicit Linux shell (bash) or automation examples. The CLI examples use 'azurecli-interactive', which is cross-platform, but PowerShell is highlighted as a separate tab, reinforcing a Windows-first approach. There are no Linux-specific instructions or references to Linux tools or patterns, and no mention of Linux-specific considerations (e.g., restarting Linux VMs, using cloud-init, etc.).
Recommendations
- Add explicit bash shell examples for configuring DNS settings, especially for Linux users.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands in bash syntax.
- Include Linux VM-specific instructions for updating DNS settings (e.g., using cloud-init, resolv.conf, or nmcli).
- Balance PowerShell examples with equivalent bash or Linux shell examples to avoid Windows-first perception.
- Mention Linux automation tools (such as Ansible or Terraform) for managing Azure Firewall DNS settings.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/ip-groups.md
...-docs/blob/main/articles/firewall-manager/ip-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by prominently featuring Azure PowerShell cmdlets for managing IP Groups, listing them in a dedicated section without mentioning equivalent Azure CLI or REST API commands. The 'devx-track-azurepowershell' custom tag further reinforces the PowerShell focus. While the text briefly mentions that IP Groups can be managed via Azure CLI and REST API, no examples or references are provided for these cross-platform tools, and PowerShell is given exclusive, detailed treatment.
Recommendations
- Add equivalent Azure CLI command examples for all major IP Group operations (create, get, set, remove, etc.) alongside PowerShell examples.
- Include REST API references or example payloads for managing IP Groups.
- Ensure that CLI and REST API documentation links are as visible and detailed as PowerShell links.
- Consider reordering sections so that cross-platform tools (CLI, REST API) are presented before or alongside PowerShell to avoid Windows-first impression.
- Review and update custom tags (e.g., 'devx-track-azurepowershell') to include CLI tracking if applicable.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub.md
.../articles/firewall-manager/quick-secure-virtual-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias. It exclusively deploys Windows Server 2019 virtual machines for testing, instructs users to use Remote Desktop and Internet Explorer (Windows-specific tools), and provides only PowerShell (Remove-AzResourceGroup) commands for resource cleanup. There are no Linux VM deployment options, no SSH or Linux browser instructions, and no Bash/Azure CLI examples.
Recommendations
- Include Linux VM deployment options in the ARM template and documentation.
- Provide instructions for connecting to Linux VMs using SSH, and for testing firewall rules with Linux browsers (e.g., Firefox, Chrome).
- Add Azure CLI and Bash examples for resource cleanup alongside PowerShell commands.
- Mention both Windows and Linux tools/patterns when describing validation steps, ensuring parity in user experience.
- Avoid referencing Windows-specific tools (e.g., Internet Explorer, Remote Desktop) exclusively; offer cross-platform alternatives.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/secure-cloud-network.md
...main/articles/firewall-manager/secure-cloud-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The tutorial demonstrates a Windows bias by exclusively deploying Windows Server VMs, providing only Windows-based remote desktop and browser testing instructions, and referencing Windows tools (Internet Explorer, RDP) without mentioning Linux alternatives. There are no examples or guidance for deploying or testing with Linux VMs, nor instructions for using SSH or Linux-native tools.
Recommendations
- Include parallel instructions for deploying Linux VMs (e.g., Ubuntu) alongside Windows Server.
- Provide examples for connecting to Linux VMs using SSH, and for testing firewall rules with Linux-native tools (e.g., curl, wget, Firefox).
- Mention Linux equivalents for remote desktop access (e.g., xrdp, Remmina, or SSH with X11 forwarding), and provide steps for testing application/network rules from a Linux VM.
- Clarify that the firewall rules and architecture apply to both Windows and Linux workloads.
- Add screenshots or CLI examples for Linux users where appropriate.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/dns-settings.md
...cs/blob/main/articles/firewall-manager/dns-settings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides configuration examples only for the Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell examples are Windows-centric, and there are no explicit Linux shell (bash) or automation examples. The PowerShell tab is always present, and the documentation metadata includes 'devx-track-azurepowershell', suggesting a Windows/PowerShell bias. There are no Linux-specific instructions or references to Linux-native tools or scripting, and no mention of Linux-specific considerations for DNS or network configuration.
Recommendations
- Add explicit bash/shell script examples for Linux users alongside PowerShell, especially for scripting and automation tasks.
- Clarify that Azure CLI commands are cross-platform and provide any Linux-specific notes if needed (e.g., differences in environment variables, quoting, or file paths).
- Include troubleshooting or configuration notes relevant to Linux VMs (e.g., how to update /etc/resolv.conf or use cloud-init for DNS settings).
- Balance the prominence of PowerShell and CLI examples, and consider renaming tabs to 'Shell (Linux/macOS)' and 'PowerShell (Windows)' for clarity.
- Review metadata and custom tags to ensure they do not signal a Windows/PowerShell preference unless justified.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-firewall-policy.md
...ain/articles/firewall-manager/quick-firewall-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell example (Remove-AzResourceGroup) for cleaning up resources, with no equivalent command for Linux users (such as Azure CLI or Bash). Additionally, the firewall policy example specifically references Windows Update using the WindowsUpdate FQDN tag, and there are no Linux-specific or cross-platform examples or guidance provided.
Recommendations
- Include Azure CLI (az group delete) and/or Bash examples alongside PowerShell for resource cleanup, to support Linux and macOS users.
- When referencing firewall rules, provide examples for both Windows-specific (e.g., Windows Update) and common Linux update endpoints (e.g., Ubuntu, Red Hat repositories) to ensure parity.
- Review all command-line instructions and ensure both Windows (PowerShell) and Linux (CLI/Bash) equivalents are presented.
- Consider adding a note or section on how to perform all steps using cross-platform tools, not just those available on Windows.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub.md
.../articles/firewall-manager/quick-secure-virtual-hub.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias: it only deploys Windows Server VMs for testing, instructs users to use Remote Desktop and Internet Explorer, and provides only PowerShell (Windows-centric) commands for resource cleanup. There are no Linux VM deployment or validation instructions, nor are Linux tools or command-line examples mentioned.
Recommendations
- Include Linux VM deployment in the ARM template or as an alternative option, and provide instructions for connecting to Linux VMs (e.g., using SSH).
- Add validation steps for Linux, such as using curl or a browser on a Linux VM to test firewall rules.
- Provide Azure CLI or Bash commands for resource cleanup, not just PowerShell.
- Mention cross-platform tools and browsers (e.g., Edge, Chrome, Firefox) instead of only Internet Explorer.
- Present both Windows and Linux examples side-by-side where relevant, or clarify that the steps are specific to Windows and link to Linux equivalents.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/ip-groups.md
...-docs/blob/main/articles/firewall-manager/ip-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page lists Azure PowerShell cmdlets prominently in a dedicated section, without providing equivalent Azure CLI or REST API examples or references. This creates a bias towards Windows/PowerShell users, as PowerShell is most commonly associated with Windows environments. While the text mentions that IP Groups can be managed via the Azure portal, Azure CLI, or REST API, only PowerShell commands are explicitly documented, and no Linux-friendly command-line examples are provided.
Recommendations
- Add a dedicated section listing equivalent Azure CLI commands for managing IP Groups, similar to the PowerShell cmdlets section.
- Provide REST API example calls for creating, updating, and deleting IP Groups.
- Ensure that CLI and REST API references are as detailed and prominent as the PowerShell section.
- Where possible, present CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub-bicep.md
...les/firewall-manager/quick-secure-virtual-hub-bicep.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 2019 virtual machines for testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific tools), and omitting any Linux VM deployment or Linux-based testing workflow. While the deployment and validation steps use both Azure CLI and PowerShell (which are cross-platform), all VM interaction and firewall testing instructions assume a Windows environment.
Recommendations
- Include Linux virtual machine deployment in the Bicep template and documentation, or provide an alternative Linux-based workflow.
- Add instructions for connecting to Linux VMs (e.g., using SSH) and testing firewall rules with Linux tools (such as curl or wget) instead of only using Remote Desktop and Internet Explorer.
- Present both Windows and Linux examples side-by-side when describing how to test connectivity and firewall rules.
- Avoid referencing Windows-specific tools (like Internet Explorer) as the only method for testing, or provide Linux browser/command-line alternatives.
- Clarify that the scenario can be tested with either Windows or Linux VMs, and provide guidance for both.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/secure-hybrid-network.md
...ain/articles/firewall-manager/secure-hybrid-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a strong Windows bias. All virtual machine examples use Windows Server 2019 Datacenter, and the only automation example for configuring IIS uses Azure PowerShell with Windows-specific commands. There are no Linux VM deployment or configuration examples, nor any mention of Linux tools or shell commands. The test and usage scenarios (RDP, PowerShell, IIS) are all Windows-centric, with no Linux alternatives provided.
Recommendations
- Provide parallel Linux examples for VM creation, such as deploying Ubuntu or other Linux distributions.
- Include automation examples using Bash/Cloud Shell for Linux VMs (e.g., using Azure CLI and cloud-init for installing Apache or Nginx).
- Demonstrate connectivity tests using SSH and curl/wget from a Linux VM, in addition to RDP and browser tests.
- Mention both Windows and Linux options when describing VM creation steps and testing scenarios.
- When showing PowerShell scripts, also provide equivalent Azure CLI/Bash scripts for Linux users.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/rule-hierarchy.md
.../blob/main/articles/firewall-manager/rule-hierarchy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Azure PowerShell (Windows-centric) command-line examples and referencing Windows file paths (e.g., C:\CustomRoles\...). There are no examples or instructions for Linux users (e.g., using Azure CLI or Bash), and the documentation does not mention Linux tools or provide cross-platform guidance. The ordering and content assume a Windows environment by default.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Use platform-neutral file paths in examples (e.g., ~/CustomRoles/ or /home/user/CustomRoles/ for Linux/macOS) or explicitly show both Windows and Linux paths.
- Add a section or callouts indicating that all steps can be performed on Linux/macOS, and provide any necessary differences or prerequisites.
- Reference both PowerShell and Bash (or shell) scripting where automation is discussed, or provide links to relevant cross-platform scripting documentation.
- Consider reordering or parallelizing example blocks so that Linux and Windows users see their options side by side, rather than Windows-first.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub.md
.../articles/firewall-manager/quick-secure-virtual-hub.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 exclusively deploying Windows Server virtual machines for testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific), and providing only PowerShell (Remove-AzResourceGroup) for resource cleanup. There are no Linux VM deployment options, no SSH or Linux-based validation steps, and no CLI/Bash examples for resource management.
Recommendations
- Include Linux virtual machine deployment options in the ARM template and documentation steps.
- Provide validation instructions for Linux VMs (e.g., using SSH to connect, using curl or a browser to test connectivity).
- Offer Azure CLI or Bash examples for resource cleanup alongside PowerShell commands.
- Mention both RDP (for Windows) and SSH (for Linux) as connection methods.
- Avoid referencing Windows-only tools (like Internet Explorer) as the sole example; suggest cross-platform browsers or command-line tools.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub-bicep.md
...les/firewall-manager/quick-secure-virtual-hub-bicep.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 and referencing Windows Server 2019 virtual machines for testing, instructing users to use Remote Desktop and Internet Explorer (both Windows-specific tools), and omitting any mention or example of Linux-based virtual machines or tools for firewall validation. While deployment steps are provided for both Azure CLI and PowerShell, the validation and testing sections assume a Windows environment only.
Recommendations
- Include parallel instructions for deploying and testing with Linux virtual machines, such as Ubuntu or CentOS.
- Provide examples of connecting to Linux VMs using SSH, and testing allowed/blocked outbound connections with tools like curl or wget.
- Mention and demonstrate browser-based validation steps that are OS-agnostic, or show how to test connectivity from a Linux shell.
- Avoid referencing only Windows-specific tools (e.g., Remote Desktop, Internet Explorer) and instead offer cross-platform alternatives.
- Explicitly state that the scenario works for both Windows and Linux VMs, and provide guidance for both.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-firewall-policy.md
...ain/articles/firewall-manager/quick-firewall-policy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell example (Remove-AzResourceGroup) for resource cleanup, with no equivalent CLI or Bash example. Additionally, the firewall policy example specifically references a Windows Update FQDN tag, and there are no Linux-specific scenarios or tools mentioned. This creates a bias toward Windows users and omits guidance for Linux users.
Recommendations
- Add Azure CLI (az group delete) and Bash examples alongside the PowerShell example for resource cleanup.
- Include Linux-relevant FQDN tags or application rule examples (e.g., Ubuntu repositories) in the firewall policy.
- Ensure that all command-line instructions are provided in both PowerShell and Bash/Azure CLI formats.
- Mention cross-platform tools and patterns, not just Windows-specific ones, to ensure parity for Linux users.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/private-link-inspection-secure-virtual-hub.md
...-manager/private-link-inspection-secure-virtual-hub.md
High Priority
View Details →
Detected Bias Types
Linux Example Present
Windows Missing
No Os Bias
Summary
The documentation does not exhibit Windows bias. In fact, the only explicit OS-specific example is for Linux (using dig for DNS queries). There are no PowerShell or Windows command-line examples, nor are Windows tools or patterns mentioned exclusively or preferentially. All Azure CLI examples are cross-platform. No Windows-specific instructions or screenshots are present.
Recommendations
- Maintain parity by continuing to provide cross-platform (Azure CLI) examples.
- Optionally, add Windows (e.g., nslookup) and macOS (e.g., dig) equivalents alongside the Linux dig example for DNS troubleshooting to further enhance inclusivity.
- Continue to avoid OS-specific bias by not assuming a particular client OS in future documentation updates.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/policy-overview.md
...blob/main/articles/firewall-manager/policy-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by consistently listing Azure PowerShell before CLI in supported mechanisms, mentioning PowerShell specifically for migration and classic rules, and omitting explicit Linux or Bash examples or tools. There are no Linux-specific instructions or parity in example commands, and the documentation assumes familiarity with PowerShell, which is more common on Windows.
Recommendations
- Ensure that Azure CLI (which is cross-platform) is listed before or alongside PowerShell in all supported mechanisms and migration instructions.
- Provide explicit Bash/Linux shell examples or references where PowerShell is mentioned.
- Include notes or links for Linux/macOS users, especially in sections discussing migration or management via command line.
- Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported equally.
- Where possible, add sample commands for both PowerShell and Bash/CLI to demonstrate parity.
Firewall Manager
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/ip-groups.md
...-docs/blob/main/articles/firewall-manager/ip-groups.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by prominently featuring Azure PowerShell cmdlets as the only explicit command-line tooling for managing IP Groups. While it mentions the Azure portal, Azure CLI, and REST API as options, it provides detailed links and examples only for PowerShell, which is primarily associated with Windows environments. There are no Azure CLI (cross-platform) or REST API command examples or references, and no Linux-specific guidance is provided.
Recommendations
- Add equivalent Azure CLI commands and documentation links for all PowerShell cmdlets listed, ensuring Linux and macOS users have clear, first-class instructions.
- Include REST API examples or references alongside PowerShell and CLI, to support automation and cross-platform use.
- When listing tools or commands, present Azure CLI and REST API options before or alongside PowerShell to avoid implying Windows-first workflows.
- Explicitly state that all management operations can be performed from Linux, macOS, and Windows, and provide examples for each where relevant.
Firewall Manager
Azure Firewall policy DNS settings
...cs/blob/main/articles/firewall-manager/dns-settings.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell, but the PowerShell examples are prominent and detailed, reflecting a Windows-centric approach. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific tooling or considerations. The CLI examples are generic and cross-platform, but PowerShell is featured as a distinct tab and is referenced in metadata. No Linux-specific troubleshooting, file paths, or environment notes are provided.
Recommendations
- Add explicit Bash examples for Linux/macOS users, especially for scripting tasks.
- Clarify that Azure CLI commands work on Linux/macOS and provide any OS-specific notes if needed.
- Balance example order so that CLI or Bash is shown before PowerShell, or at least alternate the order.
- Include troubleshooting notes or links for Linux/macOS environments where relevant.
- Avoid metadata or custom tags that imply PowerShell is the primary or preferred method unless justified.
Firewall Manager
IP Groups in Azure Firewall Policy
...-docs/blob/main/articles/firewall-manager/ip-groups.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page lists Azure PowerShell cmdlets exclusively in the 'Related Azure PowerShell cmdlets' section, without mentioning equivalent Azure CLI commands or REST API examples. PowerShell is primarily associated with Windows, and its prominence may create friction for Linux/macOS users. While the main instructions reference Azure CLI and REST API as options, no concrete examples or links are provided for those platforms, and the only detailed tooling section is Windows-centric.
Recommendations
- Add equivalent Azure CLI commands for creating, managing, and deleting IP Groups alongside the PowerShell examples.
- Provide REST API sample requests for common IP Group operations.
- Ensure that CLI and REST API examples are given equal prominence and detail as PowerShell examples.
- Consider listing CLI examples before or alongside PowerShell to avoid implicit prioritization of Windows tools.
Firewall Manager
Quickstart: Secure virtual hub using Azure Firewall Manager - Terraform
...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively deploys Windows Server 2019 virtual machines for firewall testing, with no mention of Linux VM equivalents or examples. All testing scenarios and instructions assume a Windows environment, potentially excluding Linux users from following the quickstart as written.
Recommendations
- Add instructions and Terraform resource examples for deploying Linux virtual machines alongside or instead of Windows VMs.
- Include testing scenarios that use Linux VMs (e.g., SSH access, curl/wget for connectivity tests) to demonstrate firewall rules.
- Explicitly mention that the steps are applicable to both Windows and Linux, or clarify any differences.
- Provide parity in troubleshooting and usage notes for Linux/macOS users.
Firewall Manager
Quickstart: Secure virtual hub using Azure Firewall Manager - Bicep
...les/firewall-manager/quick-secure-virtual-hub-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively deploying Windows Server 2019 VMs for testing, describing only Windows-based remote desktop and browser usage (Internet Explorer), and omitting any Linux VM deployment or Linux-based connectivity/testing instructions. While Azure CLI and PowerShell examples are both provided for deployment and management, the actual firewall validation steps are Windows-only.
Recommendations
- Include instructions and examples for deploying a Linux VM alongside or instead of Windows VMs.
- Provide Linux-based testing steps, such as using SSH to connect to the workload server and using curl or a Linux browser to validate firewall rules.
- Mention cross-platform remote desktop alternatives (e.g., xrdp for Linux, or using RDP clients on macOS/Linux).
- Avoid referencing Windows-specific tools (Internet Explorer) and suggest alternatives available on Linux/macOS.
- Clarify that the scenario can be tested on Linux or macOS, not just Windows.
Firewall Manager
Use Azure Firewall policy to define a rule hierarchy
.../blob/main/articles/firewall-manager/rule-hierarchy.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell command examples and referencing Windows file paths (e.g., C:\CustomRoles\...). No CLI, Bash, or cross-platform instructions are given, and all automation steps are shown using PowerShell, which is primarily associated with Windows. There are no Linux/macOS equivalents or guidance for users on those platforms.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include file path examples for Linux/macOS (e.g., ~/CustomRoles/...) alongside Windows paths.
- Add notes or sections clarifying how Linux/macOS users can perform the same tasks, including installation instructions for Azure CLI and/or PowerShell Core on those platforms.
- Where possible, show both PowerShell and CLI/Bash examples side-by-side.
- Link to documentation on using Azure PowerShell on Linux/macOS, if PowerShell is required.
Firewall Manager
Tutorial: Secure your hub virtual network using Azure Firewall Manager
...ain/articles/firewall-manager/secure-hybrid-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The tutorial demonstrates a notable Windows bias: all virtual machine creation steps use Windows Server images, and all configuration and testing instructions (such as installing IIS and remote desktop access) are Windows-centric. The only scripting example is a PowerShell command, with no Bash or Linux CLI alternatives. There are no instructions for deploying or testing with Linux VMs, nor for using SSH or Linux-native tools. This creates friction for users who prefer or require Linux-based environments.
Recommendations
- Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu) in both the spoke and on-premises networks.
- Include examples for installing and testing a web server on Linux (e.g., using Bash in Cloud Shell to install Apache or Nginx).
- Offer Linux CLI equivalents for configuration steps, such as using Azure CLI (az) commands instead of PowerShell.
- Demonstrate firewall rule testing using SSH and curl from Linux VMs, not just RDP and browser from Windows.
- Explicitly mention that either Windows or Linux VMs can be used, and clarify any OS-specific requirements.