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 51-75 of 80 flagged pages
Firewall Manager Azure Firewall Manager deployment overview .../main/articles/firewall-manager/deployment-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell as a method for importing firewall rules, but does not mention or provide examples for equivalent Linux/macOS-friendly tools (such as Azure CLI or REST API). No platform-specific commands or examples are shown, but the only tool named is PowerShell, which is most closely associated with Windows.
Recommendations
  • Explicitly mention Azure CLI and REST API as supported methods for rule import and other management tasks.
  • Provide example commands for Azure CLI alongside PowerShell, especially for critical operations.
  • Clarify that PowerShell is cross-platform, but also highlight Linux/macOS workflows.
  • Add links to documentation for Azure CLI and REST API usage for firewall management.
GitHub Create Pull Request
Firewall Manager Tutorial: Secure your virtual hub using Azure Firewall Manager ...main/articles/firewall-manager/secure-cloud-network.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates deploying and testing Windows Server VMs, and all firewall rule testing is done via Remote Desktop and Internet Explorer, which are Windows-specific. There are no examples or guidance for deploying Linux VMs, connecting via SSH, or testing firewall rules with Linux tools. This creates friction for Linux/macOS users who may want to secure non-Windows workloads or use non-Windows connectivity/testing methods.
Recommendations
  • Include steps for deploying a Linux VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide firewall rule examples for SSH (port 22) and show how to test connectivity using SSH from Linux/macOS.
  • Demonstrate application rule testing using browsers available on Linux/macOS (e.g., Firefox, Chrome), or command-line tools like curl.
  • Clarify that the firewall manager and hub setup is OS-agnostic and can secure both Windows and Linux workloads.
  • Add notes or sections highlighting differences or additional steps for Linux/macOS users.
GitHub Create Pull Request
Firewall Manager Tutorial: Secure your virtual hub using Azure Firewall Manager ...main/articles/firewall-manager/secure-cloud-network.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server for VM deployment and remote desktop (RDP) for connectivity and testing. There are no examples or guidance for deploying Linux VMs, using SSH, or testing with Linux tools. The documentation assumes Windows environments throughout, which may create friction for Linux/macOS users.
Recommendations
  • Include instructions and examples for deploying Linux-based VMs (e.g., Ubuntu, CentOS) alongside Windows Server.
  • Provide alternative connectivity and testing steps using SSH for Linux VMs, including firewall rule examples for port 22.
  • Mention browser options available on Linux for testing application rules.
  • Clarify that the firewall rules and architecture apply to both Windows and Linux workloads, and provide parity in walkthroughs.
GitHub Create Pull Request
Firewall Manager Quickstart: Secure virtual hub using Azure Firewall Manager - Terraform ...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 alternatives or examples. This creates a Windows-first bias and omits guidance for users who prefer or require Linux-based test environments.
Recommendations
  • Include instructions and Terraform examples for deploying Linux virtual machines (e.g., Ubuntu, CentOS) alongside or instead of Windows VMs.
  • Clarify that the firewall testing steps can be performed from either Windows or Linux VMs.
  • Provide sample application rule tests using Linux tools (e.g., curl, wget) in addition to Windows-based methods.
  • Explicitly mention cross-platform compatibility for all steps, ensuring Linux/macOS users are supported.
GitHub Create Pull Request
Firewall Manager Tutorial: Secure your hub virtual network using Azure Firewall Manager ...ain/articles/firewall-manager/secure-hybrid-network.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The tutorial consistently uses Windows-centric examples and instructions, such as creating Windows Server VMs, using PowerShell for VM extension and IIS installation, and referencing RDP and Windows tools. There are no Linux VM creation steps, nor are there Bash or Linux command alternatives for key operations. The documentation assumes the user is working in a Windows environment, which creates friction for Linux/macOS users.
Recommendations
  • Provide parallel instructions for creating Linux-based VMs (e.g., Ubuntu) in addition to Windows Server.
  • Include Bash/Azure CLI examples for VM extension installation and configuration, not just PowerShell.
  • Demonstrate how to install and test a web server (e.g., Apache or Nginx) on a Linux VM.
  • Reference SSH for remote access to Linux VMs, alongside RDP for Windows VMs.
  • Clearly indicate which steps are OS-specific and offer alternatives for Linux/macOS users.
  • Avoid assuming Cloud Shell is set to PowerShell; show how to use Bash as well.
GitHub Create Pull Request
Firewall Manager IP Groups in Azure Firewall Policy ...-docs/blob/main/articles/firewall-manager/ip-groups.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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, with no mention of equivalent Azure CLI commands or Linux/macOS-specific tooling. The custom metadata also references 'devx-track-azurepowershell', suggesting a PowerShell-centric approach. While the main instructions mention the Azure portal, CLI, and REST API, only PowerShell examples are provided, and Windows tooling is emphasized.
Recommendations
  • Add equivalent Azure CLI command examples for all listed PowerShell cmdlets.
  • Include REST API usage samples for managing IP Groups.
  • Ensure that Linux/macOS users are explicitly supported by referencing cross-platform tools before or alongside PowerShell.
  • Update metadata and navigation to reflect CLI parity, not just PowerShell focus.
GitHub Create Pull Request
Firewall Manager Azure Firewall policy DNS settings ...cs/blob/main/articles/firewall-manager/dns-settings.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but the PowerShell examples are detailed and prominent, reflecting a Windows-centric approach. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is featured as a distinct tab, which may suggest Windows-first bias. The CLI examples use Azure CLI, which is cross-platform, but there are no Linux-specific notes or examples (such as Bash scripting or Linux command-line nuances).
Recommendations
  • Add explicit Bash/Linux shell examples for all CLI commands, including environment variable usage and command chaining.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any OS-specific caveats (e.g., line continuation differences, authentication methods).
  • Balance PowerShell and CLI examples by ensuring Linux/macOS users see their workflows represented equally.
  • Consider adding a section or note for Linux/macOS users, highlighting any differences in experience or setup.
GitHub Create Pull Request
Firewall Manager Use Azure Firewall policy to define a rule hierarchy .../blob/main/articles/firewall-manager/rule-hierarchy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively using Azure PowerShell cmdlets for all CLI examples, referencing Windows file paths (e.g., C:\CustomRoles\...), and omitting equivalent instructions for Linux/macOS users (such as Azure CLI or Bash commands). The examples and workflow assume a Windows environment and do not mention Linux-compatible alternatives or cross-platform considerations.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Use generic or platform-neutral file paths in examples (e.g., /home/user/CustomRoles/...), or show both Windows and Linux/macOS paths.
  • Explicitly mention that the PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide instructions for installing PowerShell on those platforms.
  • Add a section or callout noting platform compatibility and linking to cross-platform setup guides.
  • Where possible, show both Azure Portal and CLI workflows to accommodate users on all platforms.
GitHub Create Pull Request
Firewall Manager Azure Firewall Manager policy overview ...blob/main/articles/firewall-manager/policy-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell and the Azure portal as primary management methods, with PowerShell mentioned before CLI in several places. There are no explicit Linux/macOS-specific instructions or examples, and migration guidance highlights Azure PowerShell and the portal but omits CLI or cross-platform tools. This creates a subtle Windows-first bias and may cause friction for Linux/macOS users.
Recommendations
  • Ensure that Azure CLI is mentioned alongside Azure PowerShell in all relevant sections, especially for migration and management tasks.
  • Provide explicit examples or links for both PowerShell and CLI usage, making clear which are cross-platform.
  • When listing supported deployment mechanisms, alternate the order or list CLI before PowerShell in some instances to avoid Windows-first perception.
  • Add a note clarifying that Azure CLI is fully supported on Linux/macOS and provide links to relevant documentation.
  • Include Linux/macOS-specific examples or screenshots where appropriate, or clarify that the instructions are cross-platform.
GitHub Create Pull Request
Firewall Manager Quickstart: Secure virtual hub using Azure Firewall Manager - Bicep ...les/firewall-manager/quick-secure-virtual-hub-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is notably Windows-centric in its testing and validation steps. While deployment and resource management are shown using both Azure CLI and PowerShell (which are cross-platform), the actual firewall testing instructions exclusively use Windows Server VMs, Remote Desktop, and Internet Explorer, with no mention of Linux or macOS alternatives. There are no examples or guidance for Linux-based test VMs or SSH-based connectivity.
Recommendations
  • Include instructions for deploying and testing with Linux VMs, such as using SSH to connect and curl/wget to validate allowed/blocked outbound connections.
  • Mention cross-platform browsers (e.g., Edge, Chrome, Firefox) instead of Internet Explorer, or provide browser-agnostic instructions.
  • Add examples for connecting to VMs from Linux/macOS clients, not just via Remote Desktop.
  • Clarify that the Azure CLI commands work on Linux/macOS and provide any necessary platform-specific notes.
GitHub Create Pull Request
Firewall Manager Azure Firewall Manager deployment overview .../main/articles/firewall-manager/deployment-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell as a method for importing firewall rules, but does not mention or provide equivalent examples for Linux-native tools, CLI, or automation methods. There are no explicit Windows-only tools, but the mention of PowerShell without Azure CLI or REST API alternatives suggests a bias towards Windows-centric administration patterns. No Linux-specific examples or parity are provided.
Recommendations
  • Include Azure CLI commands and examples alongside PowerShell references for all deployment and management steps.
  • Explicitly mention REST API or ARM template options for automation, which are platform-agnostic.
  • Add notes or examples for Linux users, clarifying how to perform equivalent actions without PowerShell.
  • Ensure that all references to tooling (e.g., importing rules) provide both PowerShell and CLI alternatives, and order them equally or alternate which is presented first.
GitHub Create Pull Request
Firewall Manager Quickstart: Secure virtual hub using Azure Firewall Manager - Terraform ...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively deploys Windows Server 2019 virtual machines for firewall testing, with no mention or example of Linux-based VMs. The narrative and resource list focus solely on Windows, omitting Linux equivalents and usage patterns. This presents a Windows-first bias and lacks Linux parity in examples and guidance.
Recommendations
  • Include examples that deploy Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside or instead of Windows VMs for firewall testing.
  • Provide instructions and sample code for connecting to and testing from Linux VMs, including SSH usage and relevant troubleshooting steps.
  • Mention both Windows and Linux options when describing test scenarios, and clarify that either OS can be used.
  • Ensure resource lists and walkthroughs reference Linux VM resources and patterns where applicable.
GitHub Create Pull Request
Firewall Manager Quickstart: Secure virtual hub using Azure Firewall Manager - Bicep ...les/firewall-manager/quick-secure-virtual-hub-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively deploying Windows Server 2019 virtual machines for firewall testing and providing instructions for connecting via Remote Desktop and using Internet Explorer. There are no examples or guidance for deploying or testing with Linux VMs, nor are Linux-specific tools or workflows mentioned.
Recommendations
  • Include parallel instructions for deploying and testing with Linux virtual machines (e.g., Ubuntu, CentOS).
  • Provide examples for connecting to Linux VMs (e.g., using SSH) and testing firewall rules with Linux browsers (e.g., Firefox, Chrome).
  • Mention Linux-friendly tools and workflows alongside Windows ones, ensuring equal visibility and guidance.
  • Clarify that the scenario works for both Windows and Linux workloads, or explain any limitations.
GitHub Create Pull Request
Firewall Manager Quickstart: Secure virtual hub using Azure Firewall Manager - Bicep ...les/firewall-manager/quick-secure-virtual-hub-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively deploying Windows Server 2019 virtual machines for firewall testing and providing instructions for connecting via Remote Desktop and using Internet Explorer. There are no examples or guidance for deploying or testing with Linux VMs, nor for using Linux-native tools or browsers. The deployment and validation steps use Azure CLI and PowerShell, which are cross-platform, but the VM usage and testing instructions are Windows-specific.
Recommendations
  • Include Linux VM deployment in the Bicep template and documentation, alongside Windows VMs.
  • Provide instructions for connecting to Linux VMs (e.g., using SSH) and testing firewall rules with Linux-native browsers (such as Firefox or Chromium).
  • Show examples of validating connectivity from a Linux VM, including command-line tools (e.g., curl, wget) to test allowed and blocked domains.
  • Mention both Windows and Linux options when describing VM usage and testing steps, ensuring parity in guidance.
GitHub Create Pull Request
Firewall Manager Quickstart: Secure virtual hub using Azure Firewall Manager - Terraform ...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively deploying Windows Server 2019 virtual machines for firewall testing, with no mention of Linux VM alternatives or examples. The resource list includes only azurerm_windows_virtual_machine, omitting azurerm_linux_virtual_machine, and the testing scenario is described solely in terms of Windows environments.
Recommendations
  • Include examples and instructions for deploying Linux virtual machines alongside or instead of Windows VMs.
  • Add azurerm_linux_virtual_machine to the list of Terraform resources used in the sample code.
  • Describe how to test the firewall using Linux VMs, including relevant connection and verification steps.
  • Ensure troubleshooting and next steps sections reference both Windows and Linux environments where applicable.
GitHub Create Pull Request
Firewall Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/deployment-overview.md .../main/articles/firewall-manager/deployment-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell as a method for importing firewall rules, but does not mention or provide equivalent examples for Linux users (e.g., Azure CLI or Bash). There are no explicit Windows tools mentioned, but the lack of Linux/CLI parity and the PowerShell reference indicate a subtle Windows bias.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all deployment and management steps.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or portal.
  • Where PowerShell is referenced, provide equivalent Bash/CLI commands and links to relevant documentation.
  • Review tutorials and linked pages to ensure Linux parity in walkthroughs and screenshots.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively deploying Windows Server 2019 virtual machines for firewall testing and providing only Windows-centric instructions (e.g., using Remote Desktop and Internet Explorer). There are no examples or guidance for deploying or testing with Linux VMs, nor are Linux tools or workflows mentioned.
Recommendations
  • Include Linux VM deployment in the Bicep template and document how to test firewall rules using a Linux jump server and workload server.
  • Provide Linux-specific instructions for connecting to VMs (e.g., using SSH) and for testing allowed/blocked outbound connections (e.g., using curl or wget).
  • Mention and demonstrate Linux tools and patterns alongside Windows ones, ensuring parity in examples and validation steps.
  • Explicitly state that both Windows and Linux VMs can be used for firewall testing, and provide guidance for both platforms.
GitHub Create Pull Request
Firewall Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub-terraform.md ...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively deploying Windows Server 2019 virtual machines for firewall testing, without mentioning or providing examples for Linux-based VMs. The workflow and testing steps are centered around Windows environments, omitting Linux alternatives or parity.
Recommendations
  • Include examples and instructions for deploying Linux virtual machines alongside or instead of Windows VMs for firewall testing.
  • Provide guidance on connecting to Linux VMs (e.g., using SSH) and testing firewall rules from a Linux environment.
  • Mention both Windows and Linux options when describing the test scenario, ensuring users on either platform can follow the quickstart.
  • Add sample Terraform code for azurerm_linux_virtual_machine resource and reference its documentation.
  • Clarify that the firewall testing process is not limited to Windows and can be performed from any supported OS.
GitHub Create Pull Request
Firewall Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/deployment-overview.md .../main/articles/firewall-manager/deployment-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation references Azure PowerShell as a method for importing firewall rules, but does not mention or provide equivalent examples for Linux-friendly tools such as Azure CLI or REST API. There are no explicit Windows-only tools, but the lack of Linux/CLI parity in examples and tool mentions suggests a mild Windows bias.
Recommendations
  • Add Azure CLI examples for all deployment and rule import steps alongside PowerShell references.
  • Mention REST API as an alternative for automation, which is platform-agnostic.
  • Ensure that all tooling references (e.g., PowerShell) are paired with Linux-compatible options (e.g., Azure CLI) and provide links to relevant documentation.
  • Explicitly state that all steps can be performed from Linux, macOS, or Windows environments using cross-platform tools.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively deploying Windows Server 2019 virtual machines for firewall testing and only describing test steps using Windows tools (Remote Desktop, Internet Explorer). There are no Linux VM deployment or testing instructions, nor are Linux tools (SSH, curl, etc.) mentioned. While deployment and resource management examples are provided for both Azure CLI and PowerShell, the validation and usage scenario is Windows-centric.
Recommendations
  • Include instructions for deploying a Linux VM alongside or instead of Windows VMs in the Bicep template.
  • Provide Linux-based testing steps, such as connecting via SSH to the Linux VM and using curl or wget to test allowed/blocked outbound connectivity.
  • Mention Linux-compatible tools and browsers (e.g., Firefox, curl) for firewall rule validation.
  • Add screenshots or command examples for both Windows and Linux environments to ensure parity.
  • Clarify that the scenario works for both Windows and Linux VMs, and provide guidance for users who prefer Linux.
GitHub Create Pull Request
Firewall Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub-terraform.md ...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively deploys Windows Server 2019 virtual machines for firewall testing and does not mention or provide examples for Linux-based VMs or Linux testing scenarios. All references to VM deployment and testing are Windows-centric, with no Linux alternatives or parity.
Recommendations
  • Include Linux virtual machine deployment in the Terraform sample code and documentation steps, alongside Windows VMs.
  • Provide examples and instructions for testing the firewall using Linux VMs, such as using curl or wget from a Linux workload server.
  • Explicitly mention that both Windows and Linux VMs can be used for testing, and highlight any differences in setup or connectivity.
  • Ensure that troubleshooting and next steps sections reference both Windows and Linux environments where applicable.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively deploying and testing with Windows Server virtual machines and using Remote Desktop Protocol (RDP) and Internet Explorer for validation. There are no examples or instructions for deploying Linux servers, using SSH, or testing with Linux-native tools. All server deployment and connectivity testing steps assume a Windows environment.
Recommendations
  • Include parallel instructions for deploying Linux virtual machines (e.g., Ubuntu Server) 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, or a Linux browser).
  • Demonstrate how to test application and network rules from a Linux VM, such as using SSH to connect between VMs or using command-line tools to access allowed/blocked FQDNs.
  • Mention both RDP (for Windows) and SSH (for Linux) in firewall rule creation and testing sections.
  • Use neutral language when referring to operating systems, and avoid assuming the user will always deploy Windows workloads.
GitHub Create Pull Request
Firewall Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/fqdn-filtering-network-rules.md ...icles/firewall-manager/fqdn-filtering-network-rules.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page does not provide any OS-specific examples, but it references protocols and tools (such as RDP) that are strongly associated with Windows environments. There are no Linux-specific examples or tools mentioned, and the documentation does not demonstrate parity in terms of cross-platform usage or guidance.
Recommendations
  • Include examples or references to Linux-relevant protocols and tools (e.g., SSH, SCP, SFTP) alongside or before Windows-centric ones like RDP.
  • Explicitly mention that FQDN filtering applies equally to Linux and Windows environments.
  • Provide example scenarios or command-line snippets for both Windows (PowerShell) and Linux (Bash/CLI) where relevant.
  • Balance protocol mentions so that Linux use cases are as visible as Windows ones.
GitHub Create Pull Request
Firewall Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/policy-overview.md ...blob/main/articles/firewall-manager/policy-overview.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates subtle Windows bias by listing Azure PowerShell (a Windows-centric tool) before CLI in several places and referencing PowerShell explicitly as a supported deployment mechanism. There is no explicit Linux example or mention of Linux-specific tools, and the migration example only references the portal and Azure PowerShell, omitting CLI or Linux-native approaches.
Recommendations
  • Ensure that Azure CLI is always mentioned alongside or before Azure PowerShell, as CLI is cross-platform and widely used on Linux.
  • When referencing deployment mechanisms, clarify that both Azure CLI and PowerShell are supported, and provide parity in examples and migration paths.
  • Add explicit examples or references for Linux users, such as using Azure CLI for policy creation, management, and migration.
  • Avoid listing Windows tools (like PowerShell) before cross-platform tools (like CLI) to prevent the perception of Windows-first bias.
  • Consider including a table or section that highlights tool parity and usage across different operating systems.
GitHub Create Pull Request
Firewall Manager https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall-manager/quick-secure-virtual-hub-terraform.md ...firewall-manager/quick-secure-virtual-hub-terraform.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references Windows Server 2019 virtual machines for testing the firewall and does not mention or provide examples for Linux-based virtual machines. There are no instructions or guidance for deploying or testing with Linux VMs, nor are Linux tools or patterns discussed.
Recommendations
  • Include parallel instructions and Terraform resource examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
  • Describe how to test firewall rules from a Linux VM, including example commands (e.g., using curl or wget to access www.microsoft.com).
  • Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both.
  • Ensure that troubleshooting and cleanup steps are applicable to both Windows and Linux environments, or note any differences.
GitHub Create Pull Request
← Previous Page 3 of 4 Next →