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 276-300 of 332 flagged pages
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/snat-private-range.md ...docs/blob/main/articles/firewall/snat-private-range.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell (a Windows-centric tool) is given extensive, detailed examples and is presented before Azure CLI in most sections. The PowerShell examples are more verbose and cover more scenarios (e.g., new/existing firewall, policy updates, learned prefixes) than the CLI, which is only briefly covered for basic configuration. There are no Linux-specific command-line examples (e.g., Bash scripts), nor are cross-platform considerations discussed. The documentation assumes familiarity with Windows tooling and patterns.
Recommendations
  • Expand Azure CLI examples to match the depth and breadth of PowerShell coverage, including advanced scenarios like policy updates and learned prefixes.
  • Add explicit notes or examples showing how CLI commands can be run on Linux/macOS, including any platform-specific considerations.
  • Consider including Bash or shell script examples for common tasks, especially for automation scenarios.
  • Clearly state that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • Where PowerShell is mentioned, clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, or link to relevant cross-platform setup guides.
  • Ensure that all configuration methods (portal, ARM template, CLI, PowerShell) are presented with equal detail and prominence, avoiding implicit prioritization of Windows tools.
GitHub Create Pull Request
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 →
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 a Windows bias by exclusively using Windows Server as the example operating system for the test virtual machine and only referencing remote desktop (RDP) and Internet Explorer for connectivity and testing. There are no examples or instructions for deploying or testing with Linux VMs, nor are SSH or Linux tools mentioned. The page does not provide parity for Linux users in its walkthroughs.
Recommendations
  • Include instructions for creating a Linux-based test VM (e.g., Ubuntu) alongside the Windows VM example.
  • Provide examples for connecting to the Linux VM using SSH, and for testing outbound connectivity using Linux command-line tools (e.g., curl, wget, dig).
  • Mention Linux desktop environments and browsers (e.g., Firefox, Chrome) for testing application rules.
  • Clarify that the firewall configuration applies to both Windows and Linux workloads, and provide guidance for both.
  • Add notes or sections highlighting differences or considerations for Linux users, such as configuring DNS on Linux network interfaces.
GitHub Create Pull Request
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 →
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 exclusively uses Windows Server as the example workload for testing DNAT rules and demonstrates connectivity via Remote Desktop (RDP) to port 3389, which is a Windows-specific protocol. There are no Linux VM examples, nor instructions for connecting to a Linux server (e.g., via SSH on port 22). This presents a Windows-first bias and lacks Linux parity in practical guidance.
Recommendations
  • Add parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet.
  • Include NAT rule examples for SSH (port 22) to a Linux VM alongside the RDP/Windows example.
  • Provide testing steps for Linux (e.g., using SSH client to connect to the firewall's public IP).
  • Explicitly mention that the process applies to both Windows and Linux workloads, and highlight any OS-specific considerations.
  • Ensure screenshots and portal instructions do not assume only Windows environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the example workload VM and only describes connecting via Remote Desktop (RDP), a Windows-centric protocol. There are no instructions or examples for deploying a Linux VM, connecting via SSH, or testing with Linux tools. The documentation assumes the administrator is using Windows, both for the test server and for connectivity, and omits Linux alternatives.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include steps for connecting to the Linux VM using SSH, and testing outbound connectivity using Linux command-line tools (e.g., curl, dig).
  • Provide examples for configuring and testing firewall rules with Linux workloads, such as allowing outbound HTTP/HTTPS and DNS from a Linux VM.
  • Mention both RDP (for Windows) and SSH (for Linux) when describing DNAT rule configuration and testing.
  • Ensure screenshots and walkthroughs show both Windows and Linux options where relevant.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively uses Windows Server as the example workload VM and only describes connecting via Remote Desktop (RDP), which is a Windows-centric protocol. There are no Linux VM deployment instructions, nor examples for SSH access or Linux-specific testing. The documentation implicitly assumes users are working in a Windows environment, both for the test VM and for connectivity patterns.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Provide examples for configuring DNAT rules for SSH (port 22) access to a Linux VM, alongside the RDP example.
  • Describe how to test connectivity to a Linux VM using SSH clients (e.g., PuTTY, OpenSSH) in addition to Remote Desktop.
  • Clarify that the firewall DNAT configuration applies to both Windows and Linux workloads, and provide guidance for both.
  • Where possible, avoid assuming the test VM is Windows-only; offer users a choice of OS for the example.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using Windows Server as the example operating system for the workload VM and remote desktop testing. There are no instructions or examples for deploying or testing with a Linux VM, nor any mention of Linux tools or SSH access. The testing steps assume Windows-only tools (Remote Desktop, Internet Explorer), and Linux alternatives are not provided.
Recommendations
  • Add parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Include examples for connecting to the Linux VM using SSH, and testing outbound access using Linux tools (e.g., curl, wget, dig).
  • Mention Linux as an option when describing VM creation, and provide guidance for both Windows and Linux users.
  • In the firewall testing section, provide Linux-specific steps for verifying connectivity and DNS resolution.
  • Where remote desktop is referenced, also reference SSH for Linux VMs.
  • Consider using cross-platform terminology (e.g., 'connect to your VM') and avoid assuming Windows-only environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using Windows Server as the example operating system for the workload VM, and by instructing users to test the firewall using Remote Desktop and Internet Explorer, both Windows-specific tools. There are no Linux VM deployment instructions, nor are there examples for connecting to or testing with Linux tools (e.g., SSH, curl, Firefox). The documentation does not mention Linux alternatives or provide parity for Linux users.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet.
  • Provide Linux-specific testing steps, such as connecting via SSH and using curl or Firefox to test outbound access.
  • Mention Linux as an option when creating the VM, and provide example usernames/passwords or SSH key setup for Linux.
  • Show how to test DNS resolution and firewall rules from a Linux VM.
  • Avoid assuming Internet Explorer or Remote Desktop are the only tools; suggest cross-platform alternatives (e.g., RDP clients for Linux, browser options).
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/idps-signature-categories.md ...ob/main/articles/firewall/idps-signature-categories.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page shows mild Windows bias. Several categories (ActiveX, Exploit, Web Server) mention Microsoft-specific technologies (ActiveX controls, Windows vulnerabilities, IIS) before or alongside other platforms. Windows technologies are referenced explicitly, while Linux equivalents (e.g., Linux kernel vulnerabilities, Apache/Nginx) are mentioned but not prioritized. There are no command-line examples, so no Powershell bias, but the ordering and emphasis on Windows technologies suggest a Windows-first perspective.
Recommendations
  • Ensure equal mention and description of Linux/Unix technologies and vulnerabilities alongside Windows examples in relevant categories.
  • When listing technologies (e.g., web servers), alternate or randomize the order so Windows and Linux tools are not always listed first.
  • Add explicit references to Linux/Unix-specific threats and technologies where appropriate (e.g., mention Linux kernel exploits in the Exploit category).
  • Review all category descriptions to ensure platform parity and avoid implicit prioritization of Windows technologies.
GitHub Create Pull Request
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 →
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 uses Windows Server as the example operating system for the workload VM, and all testing instructions (such as remote desktop and browser usage) assume a Windows environment. There are no Linux VM deployment or testing instructions, nor are Linux tools or patterns mentioned. This creates a Windows-first bias and omits Linux parity.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu or CentOS) in the workload subnet, alongside or instead of Windows Server.
  • Provide Linux-specific testing steps, such as SSH access for remote connectivity and using browsers like Firefox or Chrome for rule validation.
  • Mention how to configure DNS settings on Linux network interfaces, either via the Azure portal or using cloud-init/Netplan.
  • Clarify that the firewall and policy configuration applies equally to Linux workloads, and provide examples for both platforms.
  • Where remote desktop is referenced, also provide SSH instructions for Linux VMs.
  • Ensure screenshots and UI references are not Windows-specific, or provide Linux equivalents where relevant.
GitHub 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 →
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 virtual machines as test workloads and does not mention or provide examples for Linux VM deployment. All VM-related Terraform resources and password generation steps are specific to Windows, with no Linux equivalents or parity. The examples and walkthroughs do not address Linux scenarios, which may alienate users seeking cross-platform guidance.
Recommendations
  • Add Linux VM deployment examples alongside Windows VM examples using azurerm_linux_virtual_machine.
  • Include instructions for generating Linux SSH keys and configuring Linux VM authentication.
  • Provide parity in password/credential generation for Linux VMs (e.g., random SSH key resource).
  • Explicitly mention that the sample can be adapted for Linux workloads and link to relevant Linux VM documentation.
  • Consider alternating or balancing Windows and Linux examples throughout the guide to avoid platform bias.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-bicep.md ...azure-docs/blob/main/articles/firewall/deploy-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 page demonstrates a Windows bias by exclusively deploying Windows Server virtual machines in the example environment. There are no Linux VM examples or mentions, and the narrative assumes Windows as the default OS for both the jump box and server. While deployment and management instructions are cross-platform (Azure CLI and PowerShell), the infrastructure itself is Windows-centric.
Recommendations
  • Add examples and instructions for deploying Linux-based virtual machines (e.g., Ubuntu, CentOS) alongside or instead of Windows Server VMs.
  • Explicitly mention that the jump box and server can be Linux or Windows, and provide parameter options in the Bicep file for selecting the OS type.
  • Include sample Bicep code snippets for Linux VM deployment, and update descriptive text to reflect cross-platform possibilities.
  • Ensure screenshots, walkthroughs, and troubleshooting steps cover both Linux and Windows scenarios where relevant.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/threat-intel.md ...azure-docs/blob/main/articles/firewall/threat-intel.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 provides a hosts file modification example specifically for Windows, referencing the Windows file path and omitting equivalent instructions for Linux or macOS systems. No Linux or cross-platform examples are given for testing or configuration steps.
Recommendations
  • Include hosts file modification instructions for Linux (e.g., /etc/hosts) and macOS alongside the Windows example.
  • Explicitly mention that the testing steps apply to all platforms and provide platform-specific guidance where file paths or commands differ.
  • Add examples or notes for Linux users to ensure parity and inclusivity in operational instructions.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using a Windows Server VM for the workload, referencing Remote Desktop (RDP) and Microsoft Edge for testing, and omitting any mention of Linux VM deployment, SSH access, or Linux-based testing. All examples and instructions assume a Windows environment, with no Linux alternatives provided.
Recommendations
  • Add instructions for deploying a Linux VM (e.g., Ubuntu) in the workload subnet alongside or instead of Windows Server.
  • Include Linux-specific testing steps, such as using SSH to connect to the VM and using curl or wget to test outbound access.
  • Provide guidance for configuring DNS on Linux network interfaces.
  • Mention Linux equivalents for remote access (SSH) and web browsing (Firefox, Chrome, etc.), and show how to verify firewall rules from a Linux environment.
  • Ensure that all steps referencing Windows tools (RDP, Edge, Internet Explorer) have Linux alternatives.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/snat-private-range.md ...docs/blob/main/articles/firewall/snat-private-range.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
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 more detailed and appear before CLI examples, which may indicate a Windows-first and PowerShell-heavy bias. There are no explicit Linux shell (bash) or cross-platform scripting examples, and PowerShell is traditionally associated with Windows environments.
Recommendations
  • Add bash shell script examples for Azure CLI commands to demonstrate usage on Linux and macOS.
  • Ensure CLI examples are as detailed as PowerShell examples, including both creation and update scenarios.
  • Consider providing example workflows for Linux administrators, such as using cloud-init or Ansible for ARM template deployment.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Reorder sections so that Azure CLI examples appear before or alongside PowerShell examples to avoid Windows-first perception.
GitHub Create Pull Request
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 →
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 page demonstrates a Windows bias by exclusively deploying Windows Server 2019 virtual machines and focusing on RDP connectivity. There are no examples or instructions for deploying Linux VMs, nor is SSH connectivity mentioned. The only VM creation example uses azurerm_windows_virtual_machine, and password generation is tailored for Windows. The referenced PowerShell deployment article is mentioned before any Linux/CLI equivalent. No Linux-specific patterns, tools, or examples are provided.
Recommendations
  • Add parallel instructions and Terraform code samples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine).
  • Include SSH connectivity examples and NAT rule collections for Linux VMs, alongside the RDP/Windows examples.
  • Reference documentation for deploying Azure Firewall with multiple public IPs using Azure CLI or Bash, not just PowerShell.
  • Ensure password generation and VM configuration examples are not Windows-specific; include Linux username/password/SSH key scenarios.
  • Present Windows and Linux options side-by-side, or alternate which is presented first, to avoid implicit prioritization.
GitHub Create Pull Request
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 →
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 uses Windows Server as the example operating system for the test virtual machine and only describes remote desktop (RDP) access and Internet Explorer for testing. There are no instructions or examples for deploying or testing with a Linux VM, nor are SSH or Linux tools mentioned. This presents a Windows-first bias and lacks Linux parity.
Recommendations
  • Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) in the test subnet.
  • Include examples for connecting to the Linux VM using SSH, and testing outbound access using Linux tools (e.g., curl, wget, dig).
  • Mention Linux equivalents for remote access and browser testing, such as using Firefox or Chromium.
  • Clarify that the firewall configuration applies equally to Linux workloads, and provide explicit Linux testing steps.
  • Where RDP is referenced, also describe how to test DNAT rules with SSH for Linux VMs.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial exclusively demonstrates the creation and testing of a Windows Server virtual machine, with instructions to connect via Remote Desktop (RDP). There are no examples or guidance for deploying a Linux VM, nor for connecting using SSH or other Linux-native tools. All test and usage scenarios are Windows-centric, and Linux users are not provided with equivalent steps.
Recommendations
  • Add instructions for creating a Linux virtual machine (e.g., Ubuntu) in the same subnet, alongside or instead of the Windows VM.
  • Include examples for configuring DNAT rules for SSH (port 22) access to a Linux VM, in addition to RDP for Windows.
  • Provide testing steps for Linux users, such as connecting via SSH to the firewall public IP, and verifying access to the Linux VM.
  • Mention both Windows and Linux options when describing VM creation and remote access, ensuring parity in documentation.
  • Where possible, use generic terminology (e.g., 'remote access') and illustrate with both RDP and SSH examples.
GitHub Create Pull Request
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 →
Scanned: 2025-07-16 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The tutorial demonstrates a Windows bias by exclusively using Windows Server as the example OS for the workload VM and referencing Windows-specific tools (e.g., Internet Explorer, Remote Desktop) for testing. There are no Linux-based examples or instructions for deploying or testing with a Linux VM, nor are Linux-compatible tools or workflows mentioned.
Recommendations
  • Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the workload subnet.
  • Include Linux-specific steps for connecting to the VM (e.g., using SSH instead of RDP) and for testing outbound connectivity (e.g., using curl or wget instead of Internet Explorer).
  • When describing firewall rule testing, provide both Windows and Linux command-line examples for DNS resolution and web access.
  • Explicitly mention that the tutorial applies to both Windows and Linux workloads, and provide links to relevant Linux documentation where appropriate.
  • Ensure that screenshots and UI references are not OS-specific, or provide alternatives for both platforms.
GitHub 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 →
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 deploys Windows Server virtual machines in its example scenario, with no mention of Linux VM options or parity. All VM-related steps and resources reference only Windows, and there are no examples or guidance for deploying or managing Linux VMs in the same context.
Recommendations
  • Include parallel examples for deploying Linux virtual machines (e.g., using azurerm_linux_virtual_machine) alongside Windows VM examples.
  • Update the scenario description to mention both Windows and Linux VM deployment options, or provide a rationale for the Windows-only focus.
  • Add a section or note explaining how to adapt the Terraform configuration for Linux VMs, including any differences in variables or resources.
  • Ensure that any scripts, troubleshooting, or verification steps are not Windows-specific, or provide Linux equivalents where applicable.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/threat-intel.md ...azure-docs/blob/main/articles/firewall/threat-intel.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 provides a hosts file modification example specifically for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS systems. No Linux or cross-platform examples are given for testing or configuration steps.
Recommendations
  • Include Linux and macOS equivalents when referencing file paths or system modifications (e.g., mention /etc/hosts for Linux/macOS alongside the Windows path).
  • Provide cross-platform instructions or clarify that the steps apply to all major operating systems.
  • When giving examples, either show both Windows and Linux/macOS commands or use neutral, platform-agnostic language where possible.
GitHub Create Pull Request
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 →
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 using a Windows Server virtual machine for the workload example and only describing remote desktop (RDP) access and Microsoft Edge browser for testing. There are no Linux VM deployment instructions, nor are there SSH or Linux-based testing steps. The documentation assumes a Windows environment for both deployment and validation, omitting Linux alternatives.
Recommendations
  • Provide parallel instructions for deploying a Linux virtual machine (e.g., Ubuntu) in the workload subnet, including sample configuration values.
  • Include steps for connecting to the Linux VM using SSH, and for testing outbound access using Linux command-line tools (e.g., curl or wget) instead of only Microsoft Edge.
  • Demonstrate how to configure DNS settings on a Linux VM (e.g., by editing /etc/resolv.conf or using netplan), not just via the Azure portal.
  • When describing firewall rules (such as DNAT), include examples for both RDP (Windows) and SSH (Linux) to show parity.
  • In the testing section, provide both Windows and Linux validation steps, ensuring users on either platform can follow along.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the example operating system for the workload VM, and by instructing users to connect via Remote Desktop and use Internet Explorer for testing. There are no examples or instructions for deploying or testing with a Linux VM, nor are Linux tools or workflows mentioned.
Recommendations
  • Provide parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu Server) in the workload subnet, including example settings.
  • Include Linux-specific testing steps, such as connecting via SSH and using curl, wget, or a Linux browser to test outbound connectivity.
  • When describing remote access, mention both RDP (for Windows) and SSH (for Linux) as options, and show how to configure DNAT rules for SSH (port 22) as well as RDP (port 3389).
  • Avoid assuming the use of Internet Explorer or Windows-specific tools for testing; instead, offer cross-platform alternatives.
  • Explicitly state that the procedure applies to both Windows and Linux workloads, and provide example commands or screenshots for both where relevant.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation exclusively uses Windows Server as the example OS for the test virtual machine and only describes connecting via Remote Desktop (RDP) and using Internet Explorer for testing. There are no examples or instructions for deploying or testing with a Linux VM, nor are Linux tools or workflows mentioned. The only OS-specific instructions are for Windows, and these appear before any mention of alternatives (which are absent).
Recommendations
  • Add parallel instructions for deploying a Linux-based virtual machine (e.g., Ubuntu) in the 'Create a virtual machine' section, including example settings and commands.
  • Include Linux-specific testing instructions, such as using SSH to connect to the VM and using curl, wget, or a browser like Firefox for testing outbound connectivity.
  • When describing DNS configuration, provide guidance for setting DNS servers on a Linux VM (e.g., editing /etc/resolv.conf or using netplan).
  • In the 'Test the firewall' section, include Linux-based examples for verifying connectivity and DNS resolution.
  • Where possible, present both Windows and Linux options side-by-side, or at least mention Linux alternatives to ensure cross-platform parity.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/deploy-bicep.md ...azure-docs/blob/main/articles/firewall/deploy-bicep.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively deploys Windows Server virtual machines in the example environment, with no mention of Linux VM options. All VM references are to Windows, and the admin credential instructions assume a Windows context. While deployment and management commands are cross-platform (Azure CLI and PowerShell), the infrastructure example is Windows-centric, lacking Linux parity.
Recommendations
  • Include an example or option for deploying Linux virtual machines (e.g., Ubuntu Server) alongside or instead of Windows Server VMs in the Bicep template.
  • Explicitly mention that the jump box and server VMs can be either Windows or Linux, and provide parameterization or instructions for both.
  • When describing admin credentials, clarify any differences for Linux VMs (e.g., SSH keys vs. passwords).
  • Ensure that screenshots, walkthroughs, and validation steps reference both Windows and Linux VM scenarios where applicable.
GitHub Create Pull Request
Firewall https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/firewall/threat-intel.md ...azure-docs/blob/main/articles/firewall/threat-intel.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a hosts file modification example only for Windows (C:\Windows\System32\drivers\etc\hosts) and does not mention the equivalent process for Linux or macOS. This prioritizes Windows and omits guidance for users on other platforms.
Recommendations
  • Include equivalent instructions for modifying the hosts file on Linux (e.g., /etc/hosts) and macOS.
  • Present cross-platform examples together, or mention all major platforms when giving file path or configuration instructions.
  • Review the documentation for other areas where platform-specific instructions may be needed to ensure parity.
GitHub Create Pull Request
← Previous Page 12 of 14 Next →