Nat Gateway

28
Total Pages
13
Linux-Friendly Pages
15
Pages with Bias
53.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

89 issues found
Showing 26-50 of 89 flagged pages
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-connectivity.md .../articles/nat-gateway/troubleshoot-nat-connectivity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: troubleshooting steps and examples reference PowerShell and Windows-specific tools (e.g., 'ps ping', 'netsh trace', curl in PowerShell), and no Linux or cross-platform equivalents are provided. Windows-centric terminology and patterns (such as STOP/START for VM reboot) are used without mention of Linux alternatives. This may hinder Linux users from following troubleshooting steps or understanding how to apply guidance in their environments.
Recommendations
  • Provide equivalent Linux troubleshooting commands and examples (e.g., use 'ping', 'ss', 'tcpdump', 'curl' with Linux flags) alongside PowerShell/Windows examples.
  • When referencing VM operations (e.g., reboot), clarify how to perform these actions on Linux VMs (e.g., using 'sudo reboot' or Azure CLI).
  • Avoid referencing only Windows tools (e.g., 'netsh', 'ps ping')β€”include cross-platform or Linux-native tools (e.g., 'tcpdump', 'nmap', 'netcat').
  • Where examples are given (such as disabling keepalive in curl), show both PowerShell and Bash/Linux shell syntax.
  • Review all troubleshooting steps and ensure Linux users are explicitly supported, either by parallel instructions or by noting cross-platform alternatives.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-route-nat.md ...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example Powershell Heavy
Summary
The tutorial demonstrates a bias toward Windows in several areas. While the simulated NVA uses Ubuntu and includes Linux configuration steps, all test virtual machines in the spokes are Windows Server, and all functional validation (IIS install, web server, browser testing) is shown only for Windows. There are no equivalent Linux VM examples or instructions for deploying, configuring, or testing with Linux in the spokes. Additionally, all scripting and automation examples are provided in PowerShell, with no Bash/Azure CLI alternatives, and Windows tools (IIS, Microsoft Edge) are used exclusively for validation steps.
Recommendations
  • Add equivalent Linux VM deployment instructions for spoke test VMs, including Ubuntu or other supported distributions.
  • Provide Linux-based web server setup steps (e.g., Apache or Nginx) for spoke VMs, alongside IIS instructions.
  • Include validation steps using Linux tools (e.g., curl, wget, Firefox) to test outbound NAT and inter-spoke routing.
  • Offer Bash/Azure CLI examples in addition to PowerShell for resource creation and configuration.
  • Ensure that both Windows and Linux options are presented in parallel throughout the tutorial, especially in sections where only Windows is currently shown.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-nat-firewall.md ...rticles/nat-gateway/tutorial-hub-spoke-nat-firewall.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation provides step-by-step instructions for integrating NAT Gateway with Azure Firewall in a hub and spoke network, offering examples via the Azure Portal and PowerShell. However, it lacks equivalent examples for Linux users, such as Bash or Azure CLI, and relies heavily on PowerShell commands and Windows-centric tooling. PowerShell is presented as the primary scripting interface, with no mention of Bash scripts or Azure CLI commands, which are more commonly used on Linux and macOS platforms. This creates a bias toward Windows users and may hinder Linux users from following the tutorial efficiently.
Recommendations
  • Add Azure CLI (az) examples for every PowerShell command block, ensuring parity for Linux/macOS users.
  • Include Bash script snippets where appropriate, especially for VM creation and network configuration.
  • Explicitly mention that Azure CLI can be used cross-platform and provide links to CLI installation and usage guides.
  • Where PowerShell-specific instructions are given (e.g., credential handling), provide equivalent Bash/CLI workflows.
  • Review and update all sections to ensure that Linux users can follow the tutorial without needing to use PowerShell or Windows-only tools.
  • Consider reordering examples so that CLI/Bash instructions are presented before or alongside PowerShell, rather than after.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway-v2.md ...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools Windows First
Summary
The documentation provides detailed instructions and code samples exclusively for the Azure portal (GUI) and Azure PowerShell, with no examples or guidance for Linux users or cross-platform CLI tools such as Azure CLI or Bash. All command-line automation is shown using PowerShell, which is traditionally a Windows-centric tool, and there is no mention of Linux shell environments or their usage. This creates a strong Windows bias and leaves Linux users without parity in automation or scripting guidance.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell code samples, as Azure CLI is cross-platform and preferred by many Linux users.
  • Include Bash shell scripting examples where appropriate, especially for resource management tasks.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide installation links.
  • Ensure that prerequisites and setup instructions include both PowerShell and Azure CLI, with clear guidance for Linux users.
  • Review all sections to ensure Linux users can follow along without needing to use PowerShell or Windows-specific tools.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway-v2-templates.md ...-gateway/quickstart-create-nat-gateway-v2-templates.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows a bias toward Windows and PowerShell environments. The ARM template deployment instructions exclusively use Azure PowerShell, with no Azure CLI or Bash example provided for Linux/macOS users. PowerShell is presented first and in more detail, while CLI instructions are only present for Bicep deployments and not for ARM templates. There is no mention of using Bash or native Linux shell for ARM template deployment, and Windows-centric patterns (e.g., PowerShell, 'Right-click and Paste') are described before any Linux alternatives. This may make it less accessible for Linux users or those who prefer CLI over PowerShell.
Recommendations
  • Add Azure CLI/Bash examples for ARM template deployment, not just for Bicep.
  • Present CLI and PowerShell instructions side-by-side or in parallel tabs for both ARM and Bicep, rather than PowerShell-first.
  • Include explicit instructions for Linux/macOS users, such as how to run CLI commands in Bash or Zsh.
  • Avoid Windows-specific UI instructions (e.g., 'Right-click and Paste') or provide Linux/macOS equivalents.
  • Ensure all code blocks and deployment steps have parity between PowerShell and CLI/Bash.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway.md ...s/blob/main/articles/nat-gateway/manage-nat-gateway.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are extensive and detailed, often appearing before Azure CLI equivalents. The prerequisites and instructions for PowerShell include detailed steps about installing modules and connecting to Azure, which are specific to Windows environments. There is no mention of Linux-specific shell environments (e.g., Bash) or alternative scripting approaches, and the CLI examples do not reference Linux usage patterns or shell differences. The documentation assumes familiarity with Windows tools and patterns, and PowerShell is treated as a primary automation method.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, including usage in Linux/macOS terminals and Cloud Shell.
  • Clarify that Azure CLI commands are cross-platform and provide notes or examples for Linux/macOS users (e.g., differences in command syntax, environment setup).
  • Balance the order of examples so that CLI and PowerShell are presented with equal prominence, or alternate which comes first.
  • Reduce the emphasis on PowerShell-specific prerequisites and add equivalent guidance for Bash/Unix shell environments (e.g., verifying Azure CLI installation, authentication steps in Linux).
  • Mention that Azure Cloud Shell supports both Bash and PowerShell, and provide links or instructions for using Bash in Cloud Shell.
  • Where possible, use generic terminology (e.g., 'shell' or 'terminal') instead of 'PowerShell' when referring to command-line usage.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway-v2.md ...ticles/nat-gateway/quickstart-create-nat-gateway-v2.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation provides examples for Azure Portal, PowerShell, and Azure CLI, but PowerShell is given equal prominence to CLI, and is described in detail with installation and usage instructions. There is a notable emphasis on PowerShell tools and patterns, which are primarily Windows-centric. Instructions for installing and updating Azure PowerShell are included, while Linux-specific CLI usage is not highlighted. The CLI section mentions Docker as an option for Windows/macOS, but does not explicitly address Linux usage or provide parity in guidance for Linux users. The documentation assumes familiarity with PowerShell and Windows tools, potentially making it less accessible for Linux-first users.
Recommendations
  • Add explicit instructions and examples for running Azure CLI on Linux, including installation and authentication steps.
  • Provide parity in guidance for Linux users, such as using Bash scripts or native Linux tools where appropriate.
  • Reorder sections so that CLI examples are presented before PowerShell, or clarify that CLI is cross-platform and recommended for Linux users.
  • Include notes or links to Linux-specific troubleshooting or best practices for Azure resource management.
  • Reduce reliance on PowerShell-specific instructions and ensure that all steps can be completed using CLI or other cross-platform tools.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-connectivity.md .../articles/nat-gateway/troubleshoot-nat-connectivity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page displays several signs of Windows bias. Troubleshooting steps and examples reference PowerShell and Windows-specific tools (e.g., 'ps ping', 'netsh'), with no Linux or cross-platform equivalents provided. Where command-line examples are given, they are PowerShell-centric. Windows tools and patterns are mentioned exclusively or before any Linux alternatives, and there are no Linux-specific troubleshooting instructions or commands. This may hinder Linux users from effectively following the guidance.
Recommendations
  • Provide equivalent Linux command examples (e.g., use 'ping', 'nc', 'ss', 'tcpdump', or 'nmap' for network troubleshooting).
  • Include cross-platform instructions for connectivity validation and packet capture (e.g., show how to use 'tcpdump' or 'wireshark' on Linux).
  • When referencing PowerShell, also mention Bash or CLI alternatives for Azure management and troubleshooting.
  • Avoid assuming the use of Windows VMs; clarify steps for both Windows and Linux environments.
  • Add troubleshooting steps and examples for common Linux scenarios, such as checking routing tables, firewall rules (iptables, firewalld), and network interface configuration.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-nat-firewall.md ...rticles/nat-gateway/tutorial-hub-spoke-nat-firewall.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First πŸ”§ Windows Tools
Summary
The documentation provides step-by-step instructions for integrating NAT Gateway with Azure Firewall in a hub and spoke network, with examples for both the Azure Portal and PowerShell. However, it exclusively uses PowerShell for command-line examples, omitting Azure CLI (which is cross-platform and preferred on Linux/macOS). There are no bash or Linux-native CLI examples, and PowerShell is presented as the only scripting option. The documentation also references Windows-centric tools and patterns (e.g., PowerShell modules, Get-Credential for VM creation), and PowerShell instructions are given before any mention of CLI alternatives. This creates a bias towards Windows users and environments, making it less accessible for Linux administrators.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all resource creation and management steps.
  • Present Azure CLI (bash) examples before or alongside PowerShell to ensure Linux parity.
  • Avoid exclusive reliance on PowerShell-specific patterns (e.g., Get-Credential, PowerShell object syntax) and provide equivalent bash/CLI instructions.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
  • Where possible, add notes or links to Linux-specific guidance (e.g., SSH key management, bash scripting).
  • Ensure that references to tools and modules are not Windows-specific, or provide Linux alternatives.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md ...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page displays several types of Windows bias. In troubleshooting sections, Windows tools (PsPing, PowerShell Invoke-WebRequest) are listed alongside Linux equivalents, but Windows tools are hyperlinked and described in more detail. PowerShell is used exclusively for command-line examples to resolve network interface issues, with no Linux CLI (e.g., Azure CLI, Bash) alternatives provided. The use of Azure Resource Explorer is recommended with Microsoft Edge, further reinforcing a Windows-centric approach. Linux users are given less guidance and fewer actionable examples, especially for command-line troubleshooting and remediation.
Recommendations
  • Provide Azure CLI or Bash command examples alongside PowerShell for all resource management and troubleshooting tasks.
  • Include Linux-native tools (e.g., ss, ip, curl, nc) with detailed usage instructions and links, matching the detail given for Windows tools.
  • Ensure troubleshooting steps are platform-neutral or offer parallel instructions for both Windows and Linux environments.
  • Avoid recommending browser-specific tools (e.g., Microsoft Edge) unless strictly necessary, and clarify cross-platform compatibility.
  • Hyperlink Linux tool documentation as is done for Windows tools.
  • Add explicit Linux examples for resolving failed network interface states, not just PowerShell/Resource Explorer.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-route-nat.md ...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Windows Heavy Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a bias towards Windows in several areas. While the simulated NVA is based on Ubuntu and its configuration is shown, all test virtual machines in the spokes are Windows Server 2022, and all testing instructions use Windows tools (Microsoft Edge, IIS). There are no examples or instructions for deploying or testing with Linux VMs in the spokes, nor for using Linux-native tools for verification. Additionally, PowerShell is the only CLI scripting language provided, with no Bash/Azure CLI equivalents, and Windows-centric patterns (IIS, Edge) are used for validation throughout.
Recommendations
  • Provide parallel examples for deploying Linux VMs in the spokes, including instructions for installing and testing with Apache or Nginx.
  • Include Azure CLI (Bash) examples alongside PowerShell for all resource creation and configuration steps.
  • Offer Linux-native testing instructions, such as using curl or wget to verify outbound NAT and inter-spoke connectivity.
  • Demonstrate how to install and test web servers on Linux VMs (e.g., Apache, Nginx), and how to verify connectivity using Linux tools.
  • Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both platforms.
  • Avoid using only Windows-specific tools (e.g., Microsoft Edge, IIS) for validation; include Linux alternatives.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md ...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a moderate Windows bias. In troubleshooting steps, PowerShell commands and Windows-specific tools (like PsPing and Invoke-WebRequest) are highlighted, while Linux equivalents are either less detailed or omitted. In sections on resolving failed states, only PowerShell and Azure Resource Explorer (browser-based, with a browser recommendation) are provided, with no CLI or Linux-native alternatives. In the connectivity validation table, Windows tools are linked and described in more detail than their Linux counterparts. Windows approaches are often listed before Linux ones.
Recommendations
  • Provide equivalent Linux CLI (e.g., Azure CLI, Bash) commands alongside PowerShell examples for managing network interfaces and troubleshooting failed states.
  • Expand Linux tool recommendations in the connectivity validation table, e.g., suggest 'curl' or 'wget' for TCP tests, and 'socat' or 'iperf' for UDP tests, with example commands.
  • Avoid recommending only Windows-specific tools (like PsPing) without mentioning cross-platform or Linux alternatives.
  • Where PowerShell is used, add Azure CLI or REST API examples for parity.
  • Ensure Linux and Windows instructions are presented with equal detail and prominence, and avoid consistently listing Windows approaches first.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway.md .../articles/nat-gateway/quickstart-create-nat-gateway.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but exhibits a Windows/PowerShell bias in several ways. PowerShell is given a prominent, detailed walkthrough with extensive explanations and code samples, often before CLI/Linux-native alternatives. The PowerShell sections reference Windows-specific tools and installation patterns (e.g., Azure PowerShell module, Get-Module), and the ARM template cleanup instructions reference PowerShell rather than CLI/bash. While Linux is represented (e.g., Ubuntu VM examples, CLI usage), the documentation structure and depth of PowerShell content suggest a Windows-first approach.
Recommendations
  • Ensure that CLI (az) and bash examples are as detailed and prominent as PowerShell, including explanations for environment setup and troubleshooting.
  • Where PowerShell-specific instructions are given (e.g., module installation, cleanup), provide equivalent bash/CLI/Linux-native instructions alongside or before them.
  • In ARM and Bicep template deployment and cleanup sections, include both PowerShell and CLI/bash commands for parity.
  • Review the order of tabs and sections to avoid consistently placing PowerShell/Windows content before CLI/Linux content.
  • Audit for references to Windows-specific tools or patterns (such as 'Get-Module') and ensure Linux equivalents (such as checking az CLI version) are also provided.
  • Highlight that Azure Cloud Shell supports both bash and PowerShell, and provide instructions for both where relevant.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway.md ...s/blob/main/articles/nat-gateway/manage-nat-gateway.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools
Summary
The documentation demonstrates a moderate Windows bias by consistently presenting Azure PowerShell (a Windows-centric tool) before Azure CLI in all code example tabs. The PowerShell sections are more detailed, with additional context and troubleshooting steps, and the documentation assumes familiarity with PowerShell cmdlets and patterns. There is no explicit mention of Linux or Bash-specific instructions, and the CLI examples, while present, are always listed after PowerShell, reinforcing a Windows-first approach. The documentation also refers to 'PowerShell' generically in some places, which may confuse cross-platform users, as PowerShell Core is available on Linux/macOS but is less commonly used than Bash.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI (which is cross-platform) before PowerShell to avoid reinforcing a Windows-first workflow.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and clarify that PowerShell examples are also compatible with PowerShell Core on non-Windows platforms.
  • Add Bash-specific notes or examples where relevant, especially for scripting scenarios.
  • In prerequisite sections, clarify installation instructions for both Windows and Linux environments for all tools (Azure CLI, PowerShell).
  • Use neutral language such as 'Azure CLI' and 'PowerShell' (with platform notes) rather than assuming a Windows environment.
  • Consider including troubleshooting tips or environment setup notes for Linux users, especially regarding authentication and module installation.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md ...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a moderate Windows bias. In troubleshooting sections, PowerShell and Windows-specific tools (e.g., PsPing, Invoke-WebRequest) are provided for Windows users, while Linux examples are less detailed or missing. For some tasks (e.g., resolving failed network interfaces), only PowerShell and Azure Resource Explorer (browser-based, with a browser recommendation) are described, with no equivalent Linux CLI or cross-platform Azure CLI guidance. In the connectivity validation table, Windows tools are named and linked, but Linux examples are generic and less supported. Windows approaches are sometimes presented first or exclusively.
Recommendations
  • For all PowerShell-based instructions, provide equivalent Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
  • In troubleshooting steps involving network interfaces, include az network nic commands for querying and updating provisioning state.
  • In the connectivity validation table, provide more detailed Linux examples (e.g., using nc, curl, or ss for TCP/UDP tests) and link to relevant documentation.
  • Avoid recommending specific browsers unless necessary; if a browser-based tool is required, clarify that it is platform-agnostic.
  • Where Windows tools are linked (e.g., PsPing, Invoke-WebRequest), provide Linux tool links (e.g., netcat, curl, socat) and usage examples.
  • Ensure that for every Windows-specific example or tool, there is a Linux (and ideally macOS) equivalent provided with equal detail and prominence.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-connectivity.md .../articles/nat-gateway/troubleshoot-nat-connectivity.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell-specific commands and Windows-native tools (e.g., 'ps ping', 'netsh') without providing equivalent Linux commands or guidance. Examples and troubleshooting steps assume a Windows environment, and there are no Linux/Unix alternatives or parity in the instructions. This may hinder users operating Linux-based Azure VMs or those more familiar with Linux tooling.
Recommendations
  • For every PowerShell or Windows-native tool example (such as 'ps ping' or 'netsh'), provide equivalent Linux commands (e.g., 'ping', 'ss', 'tcpdump', 'traceroute', 'ncat', or 'ip netns').
  • When referencing command-line examples, clearly indicate both Windows and Linux syntax, or provide tabs/switches for each OS.
  • Avoid assuming the use of Windows VMs; explicitly mention that instructions apply to both Windows and Linux, or provide OS-specific guidance where necessary.
  • Include troubleshooting steps and diagnostic tool recommendations that are available and commonly used on Linux (e.g., 'tcpdump', 'netstat', 'ss', 'lsof').
  • Review all sections for implicit Windows-first language or assumptions, and revise to ensure Linux users are equally supported.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-route-nat.md ...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: (1) Windows Server virtual machines are used exclusively for test workloads, with no Linux VM alternatives or examples; (2) IIS (a Windows-only web server) is installed for testing, with no mention of Linux-based web servers (e.g., Apache, Nginx); (3) All test and verification steps (such as browsing with Microsoft Edge and using PowerShell scripts) are Windows-centric, with no Linux equivalents; (4) PowerShell and Windows tools are referenced heavily, and Linux alternatives are not provided or are only mentioned in passing.
Recommendations
  • Provide parallel Linux-based examples for test workloads, such as deploying Ubuntu or other Linux VMs in the spokes, and using Apache or Nginx for web server testing.
  • Include Linux command-line instructions (e.g., using curl or wget) for testing outbound connectivity and inter-spoke routing, alongside the Microsoft Edge/Windows instructions.
  • Offer Bash shell scripts or Azure CLI examples for configuration and testing, not just PowerShell.
  • When demonstrating installation of web servers or other software, show both Windows (IIS) and Linux (Apache/Nginx) options.
  • Explicitly mention that either Windows or Linux can be used for test VMs, and provide guidance for both.
  • Balance the order of presentation so that Linux and Windows are given equal prominence, or alternate which OS is presented first in examples.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway.md .../articles/nat-gateway/quickstart-create-nat-gateway.md
High Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but exhibits a Windows/PowerShell bias in several areas. PowerShell instructions are detailed and extensive, with more narrative and explanation than the equivalent Azure CLI (cross-platform) sections. PowerShell is often listed before CLI, and Windows/PowerShell-specific tools and patterns (such as Get-Credential, PowerShell module installation/upgrade, and PowerShell-specific resource management) are described in depth. There is no explicit mention of Linux shell or scripting environments in the PowerShell sections, and the CLI sections, while present, are less detailed in terms of setup and troubleshooting. The documentation does not provide Windows-only commands, but the prominence and depth of PowerShell coverage, as well as the ordering, suggest a subtle Windows-first bias.
Recommendations
  • Ensure that Azure CLI instructions are as detailed and comprehensive as PowerShell instructions, including setup, troubleshooting, and environment preparation.
  • When listing deployment methods or tabs, alternate the order or list CLI before PowerShell to avoid a Windows-first impression.
  • Where PowerShell-specific guidance is given (e.g., module installation, credential prompts), provide equivalent guidance for Linux/macOS environments (e.g., Azure CLI installation, using SSH keys, environment variables for credentials).
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide links or notes for installing and using CLI in those environments.
  • In sections describing resource cleanup or management, include bash/zsh scripting examples or notes for Linux users, not just PowerShell.
  • Review narrative and instructional text to ensure parity in depth and clarity between PowerShell and CLI/Linux sections.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/manage-nat-gateway.md ...s/blob/main/articles/nat-gateway/manage-nat-gateway.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Windows First
Summary
The documentation provides extensive Azure PowerShell examples and guidance, which is a Windows-centric toolset, and references PowerShell-specific installation and usage patterns. PowerShell is presented before Azure CLI in both prerequisites and procedural sections, and there is no mention of native Linux shell scripting or Linux-specific nuances. While Azure CLI is cross-platform, the documentation's structure and emphasis favor Windows/PowerShell users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more universally available across platforms.
  • Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows, and provide any Linux-specific notes if needed.
  • Add Bash script examples for common tasks, especially in sections where PowerShell scripting is demonstrated.
  • Avoid assuming PowerShell as the default scripting environment; clarify that both PowerShell and CLI are supported and highlight cross-platform compatibility.
  • Where PowerShell installation is discussed, provide equivalent instructions for Bash/CLI environments on Linux and macOS.
  • Consider adding a short section or callout for Linux/macOS users, summarizing the parity and any differences.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/quickstart-create-nat-gateway.md .../articles/nat-gateway/quickstart-create-nat-gateway.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First πŸ”§ Windows Tools
Summary
The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but the PowerShell sections are notably more detailed and verbose than their CLI (cross-platform) counterparts. PowerShell (a Windows-centric tool, though available on Linux) is often presented with more context, explanations, and step-by-step breakdowns. In several places, PowerShell is listed before CLI, and guidance on installing and updating Azure PowerShell is included, but there is no equivalent Linux shell or Bash-specific guidance. The documentation assumes familiarity with PowerShell cmdlets and patterns, which may be less accessible to Linux-first users.
Recommendations
  • Ensure CLI (az) examples are as detailed as PowerShell examples, including explanations and context for each step.
  • Add explicit Bash/Linux shell guidance where appropriate, such as using Bash variables, loops, or environment setup.
  • When listing deployment methods, alternate the order or explicitly state that CLI is cross-platform and suitable for Linux/macOS/Windows.
  • Provide links or references for installing/updating Azure CLI on Linux, similar to the PowerShell installation guidance.
  • Where PowerShell-specific patterns are explained (e.g., use of hashtables, cmdlet pipelines), offer analogous Bash/CLI scripting tips.
  • Review all sections for assumptions of Windows/PowerShell familiarity and add clarifying notes for Linux users as needed.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat-connectivity.md .../articles/nat-gateway/troubleshoot-nat-connectivity.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a moderate Windows bias. Troubleshooting steps and examples reference Windows-specific tools (such as 'ps ping', 'netsh', and PowerShell usage with curl) without providing equivalent Linux commands or guidance. There are no Linux or cross-platform examples for network troubleshooting, and the only code/tooling examples are Windows-centric. The mention of PowerShell and Windows tools appears before or instead of Linux alternatives, and there is no mention of common Linux utilities (e.g., ping, traceroute, tcpdump, ip, netcat) for network diagnostics.
Recommendations
  • Provide equivalent Linux command-line examples alongside Windows/PowerShell commands (e.g., use 'ping', 'nc', 'ss', 'tcpdump', 'traceroute' for Linux).
  • When referencing tools like 'ps ping' or 'netsh', add corresponding Linux alternatives (e.g., 'ping', 'ss', 'tcpdump', 'ip route').
  • Avoid using only PowerShell-specific flags (such as '-DisableKeepalive') in examples; show how to achieve the same in Bash or Linux shells.
  • Explicitly mention that the troubleshooting steps apply to both Windows and Linux VMs, and clarify any OS-specific differences.
  • Include .NET examples for both Windows and Linux environments, or provide cross-platform code samples.
  • Balance the order of presentation so that Linux and Windows tools are mentioned together or in alternating order, rather than Windows-first.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/troubleshoot-nat.md ...ocs/blob/main/articles/nat-gateway/troubleshoot-nat.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy πŸ”§ Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a moderate Windows bias. In troubleshooting steps, PowerShell commands are provided for resolving failed network interface states, but there are no equivalent CLI or Linux-native instructions. In the connectivity validation table, Windows-specific tools (PsPing, PowerShell Invoke-WebRequest) are listed, while Linux tools are mentioned but with less detail. The PowerShell method is described first and in more detail than the Azure Resource Explorer method, and there is no mention of Azure CLI or Linux-native alternatives for managing network interfaces. This may disadvantage users working primarily in Linux environments or using cross-platform automation.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, especially for managing network interfaces in failed states.
  • Expand Linux tool recommendations in the connectivity validation table (e.g., suggest 'ss', 'telnet', or 'curl' for UDP where appropriate).
  • Ensure that Linux and cross-platform tools are mentioned alongside or before Windows-specific tools, or present both together.
  • Where PowerShell is used, add corresponding Bash/Azure CLI scripts to ensure parity.
  • Clarify that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
  • Consider adding a section or callout for cross-platform troubleshooting approaches.
GitHub Create Pull Request
Nat Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/nat-gateway/tutorial-hub-spoke-route-nat.md ...n/articles/nat-gateway/tutorial-hub-spoke-route-nat.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias, particularly in the testing and validation phases. While the infrastructure setup is cross-platform (Portal, PowerShell, CLI), the test virtual machines in both spokes are exclusively Windows Server 2022, and all test/validation steps (IIS installation, browser-based tests using Microsoft Edge, PowerShell scripts) are Windows-centric. There are no equivalent examples or instructions for deploying or testing with Linux-based VMs in the spokes, nor are Linux tools (e.g., curl, Apache/nginx, SSH) mentioned for validation. The use of PowerShell and Windows tools is prevalent, and Windows-based patterns are presented as the default for validation.
Recommendations
  • Provide parallel Linux-based test VM instructions for the spokes, including deployment, configuration, and validation steps (e.g., using Ubuntu or CentOS, installing Apache/nginx, and using curl or wget for testing).
  • Include Linux command-line examples for validation (e.g., curl http://<ip-address> to test web server connectivity, or using lynx/w3m as text browsers).
  • When demonstrating IIS installation and testing, also show how to install and test a web server on Linux (e.g., sudo apt install apache2, echo 'Hello World' > /var/www/html/index.html).
  • Instruct on using SSH and Linux shell commands for connectivity and troubleshooting, not just RDP/Edge/PowerShell.
  • Balance the use of Windows and Linux tools in all test and validation sections, and avoid assuming the user will always use Windows VMs or Microsoft browsers.
  • Explicitly mention that either Windows or Linux VMs can be used for testing, and provide guidance for both.
GitHub Create Pull Request
Nat Gateway Manage a Standard V2 NAT Gateway ...lob/main/articles/nat-gateway/manage-nat-gateway-v2.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation provides detailed instructions for managing a Standard V2 NAT Gateway using the Azure portal and Azure PowerShell, but does not include any examples or guidance for Linux/macOS users via Azure CLI or other cross-platform tools. All command-line examples are exclusively PowerShell-based, which may create friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all tasks (create, associate, remove, add/remove IPs/prefixes) alongside PowerShell instructions.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where PowerShell modules are referenced, provide Azure CLI command references and links.
  • Consider reordering or parallelizing example tabs so that Azure CLI is presented before or alongside PowerShell, not only after portal instructions.
GitHub Create Pull Request
Nat Gateway Quickstart: Create a Standard V2 Azure NAT Gateway - Deployment templates ...-gateway/quickstart-create-nat-gateway-v2-templates.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment instructions primarily using Azure PowerShell, with CLI examples only present for Bicep deployments. The ARM template deployment section exclusively uses PowerShell, which is more familiar to Windows users, and the PowerShell examples are presented before CLI alternatives. There is no explicit Linux shell (bash) example for ARM template deployment, and PowerShell is the default for resource cleanup as well.
Recommendations
  • Add Azure CLI (bash) examples for ARM template deployment alongside PowerShell, ensuring Linux/macOS users have clear instructions.
  • Present CLI and PowerShell examples side-by-side or in tabs for all deployment and cleanup steps, rather than defaulting to PowerShell.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, but provide bash syntax for CLI commands to improve accessibility for Linux/macOS users.
  • Ensure that instructions for copying/pasting commands do not assume Windows conventions (e.g., right-click to paste).
GitHub Create Pull Request
← Previous Page 2 of 4 Next →